docs: add dedicated Services section for infrastructure services#126
docs: add dedicated Services section for infrastructure services#126s-adamantine wants to merge 1 commit into
Conversation
Move Hyperindex, Certified Services, and Certified PDSs into a new "Services" nav section, separating hosted infrastructure from developer tools. Update all internal cross-references to the new paths. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
📝 WalkthroughWalkthroughThe PR reorganizes the documentation site's navigation structure by creating a new top-level Services section, moving Hyperindex from Tools and Certified PDSs/Services from Reference into the new section. All internal documentation links across multiple pages are updated to reflect the new paths accordingly. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
⚔️ Resolve merge conflicts
Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@pages/architecture/epds.md`:
- Line 10: Update the link label in pages/architecture/epds.md so the anchor
text matches the target page title: change the phrase "Certified services" to
"Certified PDSs" for the link that points to /services/certified-pdss in the
sentence starting "Certified operates production, staging, and test ePDS
instances." This keeps the label consistent with the destination used later on
the page.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 9951c6b7-52e0-4464-8255-6d8884e5b77a
📒 Files selected for processing (14)
lib/navigation.jspages/architecture/account-and-identity.mdpages/architecture/certified-group-service.mdpages/architecture/epds.mdpages/architecture/overview.mdpages/core-concepts/why-at-protocol.mdpages/getting-started/testing-and-deployment.mdpages/reference/faq.mdpages/reference/glossary.mdpages/roadmap.mdpages/services/certified-pdss.mdpages/services/certified-services.mdpages/services/hyperindex.mdpages/tools/scaffold.md
| The ePDS adds email-based, passwordless sign-in on top of a standard AT Protocol PDS. Users enter their email, receive a one-time code, and end up with a normal AT Protocol session tied to a DID. | ||
|
|
||
| Certified operates production, staging, and test ePDS instances. See [Certified services](/reference/certified-pdss) for the current hostnames and guidance on which to use in which scenario. | ||
| Certified operates production, staging, and test ePDS instances. See [Certified services](/services/certified-pdss) for the current hostnames and guidance on which to use in which scenario. |
There was a problem hiding this comment.
Use consistent link label for the PDS page.
Line 10 links to /services/certified-pdss, but the label says “Certified services.” Consider matching the destination title (“Certified PDSs”) for consistency with Line 194.
✏️ Suggested copy tweak
-Certified operates production, staging, and test ePDS instances. See [Certified services](/services/certified-pdss) for the current hostnames and guidance on which to use in which scenario.
+Certified operates production, staging, and test ePDS instances. See [Certified PDSs](/services/certified-pdss) for the current hostnames and guidance on which to use in which scenario.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| Certified operates production, staging, and test ePDS instances. See [Certified services](/services/certified-pdss) for the current hostnames and guidance on which to use in which scenario. | |
| Certified operates production, staging, and test ePDS instances. See [Certified PDSs](/services/certified-pdss) for the current hostnames and guidance on which to use in which scenario. |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@pages/architecture/epds.md` at line 10, Update the link label in
pages/architecture/epds.md so the anchor text matches the target page title:
change the phrase "Certified services" to "Certified PDSs" for the link that
points to /services/certified-pdss in the sentence starting "Certified operates
production, staging, and test ePDS instances." This keeps the label consistent
with the destination used later on the page.
Summary
pages/tools/hyperindex.md,pages/reference/certified-services.md, andpages/reference/certified-pdss.mdintopages/services/lib/navigation.jsto reflect the new section and removes the moved entries from Tools and Reference/services/pathsWhy
Service-related content was scattered across Tools, Reference, and Architecture sections. A dedicated Services section makes it easier to find infrastructure you interact with, and clarifies the distinction: Tools = things you install and run locally (CLI, Scaffold, Hyperboards), Services = hosted infrastructure (indexer, PDSs, service endpoints).
Test plan
npm run buildpasses with no errors🤖 Generated with Claude Code
Summary by CodeRabbit