Repository navigation
docs: title the migration page with its H1, and move the posthog.com SDK page into the reference - #361
Closed
gewenyu99 wants to merge 2 commits into
Closed
docs: title the migration page with its H1, and move the posthog.com SDK page into the reference#361gewenyu99 wants to merge 2 commits into
gewenyu99 wants to merge 2 commits into
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The posthog.com Rust SDK page redirects to this reference once 1.0.0 ships, so its setup, how-to, and feature flag sections now live in docs/getting-started.md. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
gewenyu99
marked this pull request as draft
November 12, 2026 17:36
gewenyu99
changed the title
3 of 13 tasks
Contributor
Author
|
Combined into #362. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
💡 Motivation and Context
The migration page on posthog.com shows two titles: the front matter title "PostHog Rust SDK migration guides", then the guide's own H1. With one guide, the generator now uses the guide's H1 as the page title and drops the H1 from the body. With more than one guide, nothing changes.
The guide rewrites that use this are in separate PRs. The Python SDK has the same change in PostHog/posthog-python#1244.
Content from the posthog.com Rust SDK page
posthog.com retires its hand-written Rust SDK page and redirects it to the Rust reference. So nothing is lost, this PR moves everything on that page that the reference didn't already say into
docs/getting-started.md, which the reference shows as its "Getting started" section. Examples are setup variants, how-to sections, feature flag usage, and configuration guidance.💚 How did you test it?
Ran migration_page on a one-guide and a two-guide input. The script has no test suite.
📝 Checklist
🤖 Agent context
Human-driven (agent-assisted)
🤖 Generated with Claude Code