Skip to content

Conversation

@Andy-Hay
Copy link
Contributor

@Andy-Hay Andy-Hay commented Jan 7, 2026

What changed?

Change references to iglucentral from http to https.

Why?

We will be turning off the http access in February 2026

Reviewer guidance

Changed references and any code snippets.

AI reviews

Claude will automatically review this PR against the docs style guide.

If you have questions or want it to look again at something specific, tag @claude in a comment.

@github-actions
Copy link
Contributor

github-actions bot commented Jan 7, 2026

Missing SEO metadata

The following markdown files are missing required metadata fields:

  • docs/api-reference/iglu/common-architecture/self-describing-json-schemas/index.md: missing fields: description, keywords, sidebar_label
  • docs/api-reference/iglu/iglu-central-setup/index.md: missing fields: description, keywords, sidebar_label
  • docs/api-reference/iglu/iglu-clients/objc-client/index.md: missing fields: description, keywords, sidebar_label
  • docs/api-reference/iglu/iglu-clients/ruby-client/index.md: missing fields: description, keywords, sidebar_label
  • docs/api-reference/iglu/iglu-repositories/iglu-central/index.md: missing fields: description, keywords, sidebar_label
  • docs/api-reference/iglu/iglu-repositories/iglu-server/index.md: missing fields: description, keywords, sidebar_label
  • docs/api-reference/iglu/iglu-repositories/index.md: missing fields: description, keywords, sidebar_label
  • docs/api-reference/iglu/iglu-repositories/static-repo/index.md: missing fields: description, keywords, sidebar_label
  • docs/api-reference/iglu/iglu-resolver/index.md: missing fields: description, keywords, sidebar_label
  • docs/api-reference/iglu/igluctl-2/index.md: missing fields: description, keywords, sidebar_label
  • docs/api-reference/iglu/index.md: missing fields: description, keywords, sidebar_label
  • docs/api-reference/json-schema-reference/index.md: missing fields: keywords, sidebar_label
  • docs/api-reference/snowplow-micro/api/index.md: missing fields: keywords, sidebar_label
  • docs/data-product-studio/data-structures/manage/api/index.md: missing fields: description, keywords
  • docs/data-product-studio/data-structures/manage/iglu/index.md: missing fields: description, keywords
  • docs/data-product-studio/data-structures/version-amend/amending/index.md: missing fields: keywords, sidebar_label
  • docs/data-product-studio/snowtype/snowtype-config/index.md: missing fields: description, keywords
  • docs/data-product-studio/snowtype/using-the-cli/index.md: missing fields: description, keywords
  • docs/destinations/forwarding-events/google-tag-manager-server-side/snowplow-tag-for-gtm-ss/snowplow-tag-configuration/advanced-event-settings/index.md: missing fields: description, keywords, sidebar_label
  • docs/events/ootb-data/app-error-events/index.md: missing fields: description, keywords, sidebar_label
  • docs/events/ootb-data/app-information/index.md: missing fields: description, keywords, sidebar_label
  • docs/events/ootb-data/app-performance/index.md: missing fields: description, keywords, sidebar_label
  • docs/events/ootb-data/consent-events/index.md: missing fields: description, keywords, sidebar_label
  • docs/events/ootb-data/device-and-browser/index.md: missing fields: description, keywords, sidebar_label
  • docs/events/ootb-data/ecommerce-events/index.md: missing fields: description, keywords, sidebar_label
  • docs/events/ootb-data/geolocation/index.md: missing fields: description, keywords, sidebar_label
  • docs/events/ootb-data/links-and-referrers/index.md: missing fields: description, keywords, sidebar_label
  • docs/events/ootb-data/media-events/index.md: missing fields: description, keywords, sidebar_label
  • docs/events/ootb-data/mobile-lifecycle-events/index.md: missing fields: description, keywords, sidebar_label
  • docs/events/ootb-data/page-activity-tracking/index.md: missing fields: description, keywords, sidebar_label
  • docs/events/ootb-data/page-and-screen-view-events/index.md: missing fields: description, keywords, sidebar_label
  • docs/events/ootb-data/user-and-session-identification/index.md: missing fields: description, keywords, sidebar_label
  • docs/events/ootb-data/visionos-swiftui/index.md: missing fields: description, keywords, sidebar_label
  • docs/fundamentals/failed-events/index.md: missing fields: keywords
  • docs/fundamentals/schemas/index.md: missing fields: keywords
  • docs/monitoring/recovering-failed-events/manual/running/index.md: missing fields: description, keywords
  • docs/sources/c-tracker/client-sessions/index.md: missing fields: description, keywords, sidebar_label
  • docs/sources/c-tracker/tracking-specific-events/index.md: missing fields: description, keywords
  • docs/sources/flutter-tracker/anonymous-tracking/index.md: missing fields: description, keywords
  • docs/sources/flutter-tracker/initialization-and-configuration/index.md: missing fields: description, keywords
  • docs/sources/mobile-trackers/custom-tracking-using-schemas/index.md: missing fields: description, keywords
  • docs/sources/mobile-trackers/previous-versions/mobile-trackers-v2-x/remote-configuration/index.md: missing fields: description, keywords, sidebar_label
  • docs/sources/mobile-trackers/previous-versions/mobile-trackers-v3-x/remote-configuration/index.md: missing fields: description, keywords, sidebar_label
  • docs/sources/mobile-trackers/remote-configuration/index.md: missing fields: description, keywords
  • docs/sources/react-native-tracker/previous-version/react-native-tracker-v2-reference/tracking-events/screen-tracking/index.md: missing fields: description, keywords, sidebar_label
  • docs/sources/react-native-tracker/tracking-events/screen-tracking/index.md: missing fields: description, keywords
  • docs/sources/ruby-tracker/tracking-events/index.md: missing fields: description, keywords
  • docs/sources/web-trackers/custom-tracking-using-schemas/index.md: missing fields: description, keywords
  • docs/sources/web-trackers/migration-guides/v3-to-v4-migration-guide/index.md: missing fields: description, keywords
  • docs/sources/web-trackers/previous-versions/browser-tracker-v3-reference/tracker-setup/initialization-options/index.md: missing fields: description, keywords, sidebar_label
  • docs/sources/web-trackers/previous-versions/web-trackers-v3/custom-tracking-using-schemas/index.md: missing fields: description, keywords, sidebar_label
  • docs/sources/web-trackers/previous-versions/web-trackers-v3/tracking-events/session/index.md: missing fields: description, keywords, sidebar_label
  • docs/sources/web-trackers/tracking-events/screen-views/index.md: missing fields: description, keywords
  • docs/sources/web-trackers/tracking-events/session/index.md: missing fields: description, keywords
  • docs/sources/webhooks/adjust-webhook/index.md: missing fields: description, keywords
  • docs/testing/data-structures-ci-tool/index.md: missing fields: description, keywords
  • docs/testing/snowplow-micro/adding-schemas/index.md: missing fields: keywords
  • tutorials/data-products-base-tracking/setup-custom-ds.md: missing fields: description, keywords
  • tutorials/data-structures-in-git/local-setup.md: missing fields: description, keywords
  • tutorials/data-structures-in-git/validation-and-publishing.md: missing fields: description, keywords

Required fields

The file metadata is important for SEO and marketing. All markdown files, except for those with filenames starting with _, should include:

  • title: Full, descriptive page title
  • sidebar_label: Short title for navigation sidebar (can be the same as the main title)
  • description: One to two sentences summarizing the page contents
  • keywords: Array of marketing/SEO keywords

Please add the missing metadata.

@netlify
Copy link

netlify bot commented Jan 7, 2026

Deploy Preview for snowplow-docs ready!

Name Link
🔨 Latest commit 0a12647
🔍 Latest deploy log https://app.netlify.com/projects/snowplow-docs/deploys/696131bb99b2550008e3e972
😎 Deploy Preview https://deploy-preview-1567--snowplow-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 19 (🟢 up 1 from production)
Accessibility: 91 (no change from production)
Best Practices: 92 (no change from production)
SEO: 95 (no change from production)
PWA: -
View the detailed breakdown and full score reports

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

@claude
Copy link

claude bot commented Jan 7, 2026

Style Guide Review

Thank you for updating the Iglu Central URLs to HTTPS! The technical changes look correct. I found a few writing quality issues to address according to our style guide:

Issues to fix

1. Use "Snowplow" not "Snowplow Analytics"

  • Location: docs/api-reference/iglu/iglu-repositories/iglu-central/index.md:7
  • Current: "hosted by Snowplow Analytics"
  • Should be: "hosted by Snowplow"
  • Reference: Style guide line 88

2. Avoid marketing language: "easily"

  • Location: Multiple instances, but not changed in this PR
  • This is pre-existing, but worth noting for future improvements

3. Typo: "publically" should be "publicly"

  • Location: docs/api-reference/iglu/iglu-repositories/iglu-central/index.md:11
  • Current: "storing publically-available JSON Schemas"
  • Should be: "storing publicly available JSON Schemas"
  • Note: Also remove the hyphen ("publicly available" not "publicly-available")

4. Inconsistent connection type in Ruby example

  • Location: docs/api-reference/iglu/iglu-clients/ruby-client/index.md:56
  • Current: :connection => {:https => {:uri => "https://iglucentral.com"}}
  • Note: Changed from :http to :https in the key name. Please verify this is the correct Ruby client syntax and not just the URI that should change.

Summary

The HTTPS migration is well-executed across all files. The main actionable items are:

  1. Change "Snowplow Analytics" to "Snowplow" on line 7
  2. Fix "publically" to "publicly" and remove hyphen on line 11
  3. Verify the Ruby client connection type change (http vs https key)

All other URL changes follow the correct pattern. Nice work on the comprehensive update!

@antonis-snowplow
Copy link
Contributor

@Andy-Hay can you please resolve the conflicts for this one? I can then approve this

@Andy-Hay
Copy link
Contributor Author

Andy-Hay commented Jan 9, 2026

@claude can you review please

@Andy-Hay Andy-Hay marked this pull request as ready for review January 9, 2026 17:12
Copy link
Contributor

@antonis-snowplow antonis-snowplow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Andy-Hay
Copy link
Contributor Author

Andy-Hay commented Jan 9, 2026

@stanch would you be able to review this and hit merge if all good please ?


```json
{
"$schema": "http://iglucentral.com/schemas/com.snowplowanalytics.self-desc/schema/jsonschema/1-0-0#",
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@istreeter Will this work? I am under the impression that this is hardcoded and can’t be changed in customer schemas?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay i may have gone too far and change more than the resolvers. Probably easier to create a new PR if thats the case 😢

incorporating the aforementioned `self` property.

Notice that we also changed the `$schema` property to [our own JSON Schema](http://iglucentral.com/schemas/com.snowplowanalytics.self-desc/schema/jsonschema/1-0-0#) which enforces the `self` property.
Notice that we also changed the `$schema` property to [our own JSON Schema](https://iglucentral.com/schemas/com.snowplowanalytics.self-desc/schema/jsonschema/1-0-0#) which enforces the `self` property.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same comment

:data => {
:cacheSize => 500,
:repositories => [{:name => "Iglu Central", :priority => 0, :vendorPrefixes => ["com.snowplowanalytics"], :connection => {:http => {:uri => "http://iglucentral.com"}}}]
:repositories => [{:name => "Iglu Central", :priority => 0, :vendorPrefixes => ["com.snowplowanalytics"], :connection => {:https => {:uri => "https://iglucentral.com"}}}]
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
:repositories => [{:name => "Iglu Central", :priority => 0, :vendorPrefixes => ["com.snowplowanalytics"], :connection => {:https => {:uri => "https://iglucentral.com"}}}]
:repositories => [{:name => "Iglu Central", :priority => 0, :vendorPrefixes => ["com.snowplowanalytics"], :connection => {:http => {:uri => "https://iglucentral.com"}}}]

Not an expert on Ruby, but sounds like http is a fixed name of the setting?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not done Ruby for a long time, so i asked Claude and queried what it should be. It said it should be https. But it could be wrong.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see the Ruby client is archived and not touched in 9 years. I suggest just deleting the whole thing from the docs. But it’s definitely http: https://github.com/snowplow-archive/iglu-ruby-client/blob/master/lib/iglu-client/resolver.rb#L94

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm going to move back to draft and redo in two weeks - it's wrong, sorry for wasting your time.


```json
{
"$schema": "http://iglucentral.com/schemas/com.snowplowanalytics.self-desc/schema/jsonschema/1-0-0#",
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same comment about hardcoded schema (throughout this file)


- JSON Schema has inconsistent self-describing information and path on filesystem
- JSON Schema has invalid `$schema` keyword. It should be always set to [iglu-specific](http://iglucentral.com/schemas/com.snowplowanalytics.self-desc/schema/jsonschema/1-0-0#), while users tend to set it to Draft v4 or even to self-referencing Iglu URI
- JSON Schema has invalid `$schema` keyword. It should be always set to [iglu-specific](https://iglucentral.com/schemas/com.snowplowanalytics.self-desc/schema/jsonschema/1-0-0#), while users tend to set it to Draft v4 or even to self-referencing Iglu URI
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same


```json
{
"$schema": "http://iglucentral.com/schemas/com.snowplowanalytics.self-desc/schema/jsonschema/1-0-0#",
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same


```json
{
"$schema":"http://iglucentral.com/schemas/com.snowplowanalytics.self-desc/schema/jsonschema/1-0-0#",
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same

"required": [
"example_field_1"
],
"$schema": "http://iglucentral.com/schemas/com.snowplowanalytics.self-desc/schema/jsonschema/1-0-0#",
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok I will stop commenting on this :)

@Andy-Hay Andy-Hay marked this pull request as draft January 9, 2026 18:55
@Andy-Hay
Copy link
Contributor Author

Closing in favour of targeted #1574

@Andy-Hay Andy-Hay closed this Jan 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants