Adding Signals Real-time personalisation accelerator

[jborlase-snowplow]

No description provided.

[netlify]

✅ Deploy Preview for snowplow-docs ready!

Name	Link
🔨 Latest commit	dbb37c8
🔍 Latest deploy log	https://app.netlify.com/projects/snowplow-docs/deploys/685bcef1d21fba0008058848
😎 Deploy Preview	https://deploy-preview-1284--snowplow-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[Copilot]

Pull Request Overview

This PR introduces a new tutorial accelerator for building a real-time personalization system with Snowplow Signals on a newspaper website example.

• Adds step-by-step guides for Snowplow event tracking, defining Signals attributes/views, and integrating real-time recommendations.
• Provides metadata, architectural overview, and sample JSON/Python/Node code snippets.

Reviewed Changes

Copilot reviewed 8 out of 8 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
tutorials/signals-real-time-media-personalisation/meta.json	Defines tutorial metadata (title, label, description)
tutorials/signals-real-time-media-personalisation/intro.md	Overview and architecture diagram for the tutorial
tutorials/signals-real-time-media-personalisation/snowplow-tracking.md	Guide to setting up Snowplow tracking and JSON schema
tutorials/signals-real-time-media-personalisation/define-attributes-and-views.md	Instructions to install SDK and define Signals attributes, views, and services
tutorials/signals-real-time-media-personalisation/creating-real-time-recommendations.md	NextJS example for retrieving Signals attributes and generating recommendations

Comments suppressed due to low confidence (4)

tutorials/signals-real-time-media-personalisation/snowplow-tracking.md:17

• [nitpick] Grammar: add the missing article and use lowercase for consistency: "create a data structure with the following JSON schema:"

If you would like to follow along, you can create Data Structure with the following JSON schema:

tutorials/signals-real-time-media-personalisation/meta.json:4

• [nitpick] Wording: the word "using" is repeated. Consider rephrasing to remove duplication, for example: "How to build a real-time recommendation system with Snowplow Signals on a newspaper website."

"description": "How to build a real-time recommendation system using Snowplow Signals using a Newspaper website as an example."

tutorials/signals-real-time-media-personalisation/snowplow-tracking.md:21

• The $schema field is using markdown link syntax instead of a plain URL. It should be a raw string, e.g., "http://iglucentral.com/schemas/com.snowplowanalytics.self-desc/schema/jsonschema/1-0-0#" to produce valid JSON.

"$schema": "[http://iglucentral.com/schemas/com.snowplowanalytics.self-desc/schema/jsonschema/1-0-0#](http://iglucentral.com/schemas/com.snowplowanalytics.self-desc/schema/jsonschema/1-0-0#)",

tutorials/signals-real-time-media-personalisation/creating-real-time-recommendations.md:108

• The variable articles_read is not defined in this snippet. You should ensure it is declared or replace it with the correct identifier (e.g., a list of previously read slugs).

let recommendedArticles = articles.filter((article) => interests.includes(article.category) && !articles_read.includes(article.slug))

[Copilot]

Typo in the explanatory text: it says "Lets breakdown" above the list. It should read "Let's break down" for correct grammar.

Suggested change

	Lets breakdown what that code does:
	Let's break down what that code does:

[Copilot]

Variable name typo: "technlogy_articles_read" should be spelled "technology_articles_read" to match the attribute key.

Suggested change

	const technlogy_articles_read = (attributes['article_category_technology_read_count']?.[0] ?? 0);
	const technology_articles_read = (attributes['article_category_technology_read_count']?.[0] ?? 0);

[johnmicahreid]

@mscwilson can we add this to the 1197 PR?