Skip to content

infra: Learn Hub migration prep#208

Draft
marc0olo wants to merge 5 commits intomainfrom
infra/learn-hub-migration-prep
Draft

infra: Learn Hub migration prep#208
marc0olo wants to merge 5 commits intomainfrom
infra/learn-hub-migration-prep

Conversation

@marc0olo
Copy link
Copy Markdown
Member

@marc0olo marc0olo commented May 6, 2026

Summary

Prepares the repo to migrate all developer-relevant content from learn.internetcomputer.org into the docs site before Learn Hub is taken down. No new docs pages are created in this PR — it lays the infrastructure for 9 follow-on content PRs.

This PR is a draft. All 9 batch content PRs target this branch (infra/learn-hub-migration-prep) rather than main. The full migrated site can be previewed here before anything merges to main. Once all batches and the final cleanup PR are merged into this branch, a maintainer rebases on main and marks this PR ready.

  • 86 Learn Hub articles fetched via Zendesk API and committed to .migration/learn-hub/ as Markdown with learn_hub_* frontmatter (migrated: false). 57 in-scope (under how-does-icp-work/) and 29 out-of-scope (under out-of-scope/).
  • Navigation map (.docs-plan/learn-hub-navigation.md): every in-scope article mapped to a target file, action type (new / expand / reference / skip), batch number, and per-batch cross-link replacement table. Three articles are explicitly marked skip with reasons and kept for human review in the final cleanup PR.
  • Agent instructions (.docs-plan/learn-hub-migration.md): 9-step workflow an agent follows for each batch PR — skill loading (technical-documentation + icp-brand-voice only, no icskills needed for concept pages), staging file reading, per-action page templates, sidebar notes (no sidebar.mjs changes needed), technical verification step for protocol-layer content, intra-batch linking rules, skip article policy, and a final cleanup checklist with a human review gate before the staging directory is deleted. Brand voice is called out as critical — Learn Hub articles routinely use banned jargon that must be cleaned up during migration.
  • AGENTS.md rule updates: removed "Learn Hub" from the "never duplicate external docs" list; updated the "link to old docs" rule to direct agents to docs/concepts/ and .docs-plan/learn-hub-migration.md instead of Learn Hub.
  • docs/index.mdx: removed the Learn Hub <LinkCard> from the External Resources section.
  • Structural decisions recorded in .docs-plan/decisions.md (2026-05-06 entry).
  • 9 batch entries added to .docs-plan/migration-plan.md.

What comes next (not in this PR)

9 content PRs, one per batch, each targeting infra/learn-hub-migration-prep. Batches 1–4 have no dependencies and can run in parallel. GitHub Issues for the 9 batches will be created after this PR is reviewed.

Sync recommendation

hand-written

…t instructions

- Fetch all 86 Learn Hub articles via Zendesk API into .migration/learn-hub/
  (57 in-scope under how-does-icp-work/, 29 out-of-scope; each with
  learn_hub_* frontmatter and migrated: false)
- Add .docs-plan/learn-hub-navigation.md: article-to-target mapping for
  all 9 content batches with action types (new/expand/reference/skip)
  and per-batch cross-link replacement tables
- Add .docs-plan/learn-hub-migration.md: 9-step agent workflow covering
  skill loading, staging file reading, per-action templates, sidebar
  config (no changes needed), verification step for protocol content,
  intra-batch linking rules, skip article policy, and final cleanup PR
  checklist with human review gate
- Update .docs-plan/decisions.md with migration structural decisions
- Update .docs-plan/migration-plan.md with 9 batch entries
- Remove Learn Hub from AGENTS.md duplicate-content rule and link rule
- Remove Learn Hub LinkCard from docs/index.mdx
@marc0olo marc0olo requested a review from a team as a code owner May 6, 2026 13:40
@marc0olo marc0olo marked this pull request as draft May 6, 2026 14:30
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.

1 participant