docs: establish Dusk SEO source truth - #145
Merged
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
This PR establishes a single, crawlable “Privacy on Dusk” documentation source-of-truth and reconciles product/protocol status language across Learn/Developer docs (especially around Phoenix being a live capability with new-transaction admission temporarily paused).
Changes:
- Add a new canonical “Privacy on Dusk” page and link it from Learn navigation and Overview.
- Align Phoenix wording across docs to “temporary admission pause” (not retirement) and clarify Boreas vs Aegis scope.
- Standardize “current availability” messaging for key components/products (DuskEVM, Hedger, Citadel 2, Forge, W3sper, Hyperstaking, Dusk Trade, etc.).
Reviewed changes
Copilot reviewed 13 out of 13 changed files in this pull request and generated 3 comments.
Show a summary per file
| File | Description |
|---|---|
| src/sidebars/siteSidebar.js | Adds “Privacy on Dusk” to the Learn → Architecture sidebar. |
| src/content/docs/updates/network/boreas.md | Updates Boreas narrative and Phoenix status language to reflect a temporary admission pause. |
| src/content/docs/learn/privacy-on-dusk.md | Introduces the new canonical Privacy on Dusk page with capability/status table and FAQ. |
| src/content/docs/learn/overview.mdx | Updates positioning language and links to the new Privacy page. |
| src/content/docs/learn/hyperstaking.md | Adds explicit “current availability” language and refines the Sozu example text. |
| src/content/docs/learn/glossary.md | Refreshes glossary entries for updated status/availability across the stack. |
| src/content/docs/learn/dusk-trade.md | Clarifies Dusk Trade is in development (not presented as live). |
| src/content/docs/learn/dusk-evm.md | Adds explicit current availability note for DuskEVM testnet. |
| src/content/docs/learn/deep-dive/duskds-tx-models.md | Adds/updates availability note and Phoenix pause wording. |
| src/content/docs/learn/core-components.md | Expands component table with availability + adds capability/product status map and related sections. |
| src/content/docs/developer/integrations/w3sper.md | Adds current availability note for W3sper. |
| src/content/docs/developer/duskvm/overview.md | Adds current availability note for DuskVM/Forge. |
| src/content/docs/developer/digital-identity/protocol.mdx | Adds current availability note for Citadel 2. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
HDauven
force-pushed
the
agent/seo-phase1-source-truth
branch
from
August 31, 2026 16:02
842214a to
cf200fc
Compare
HDauven
approved these changes
Aug 31, 2026
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.
Summary
Why / root cause
Dusk's public documentation described the same products and privacy capabilities inconsistently. Search engines and answer engines need one crawlable, internally linked source of truth that clearly distinguishes public flows, confidential flows, live mainnet capabilities, live public-testnet capabilities, paused admission, and products being built.
Impact and boundaries
This PR changes documentation only. It does not change protocol behavior, deploy contracts, alter network configuration, or claim automatic regulatory compliance. “Dusk Network” remains a former/alternate name; the current public brand is Dusk.
Validation
npm ci --ignore-scriptswith npm 11.18.0 — passednpm audit signatures— 362 packages verified; 85 packages with verified registry attestationsnpm run verifyon the rebased final commit — passed: 68 pages built, all internal links valid, 3/3 tests passed/learn/privacy-on-dusk/— passed; page, metadata, table, and FAQ structure rendered without page errorsDeployment, configuration, and rollback
No secrets, environment variables, migrations, or configuration changes. Normal docs deployment after an approved merge. Rollback by reverting this commit.
Dependencies and remaining risk
The companion website PR will link to the new
/learn/privacy-on-dusk/URL, so merge and deploy this docs PR first. Product-status wording reflects the approved August 31, 2026 source-of-truth decisions and should receive the requested domain-owner review.Post-deployment checks
https://docs.dusk.network/learn/privacy-on-dusk/returns 200 and is present in the sitemapDeliberately not included