Cardano Updates

Module 6 had a Governance page (SDK how-tos) and a separate "Governance via
cardano-cli" category covering the same operations plus deep ceremonies. Add
cardano-cli as a third tab alongside Evolution and Mesh for each operation
(register DRep, delegate, vote, propose, committee, query), and continue the
deeper cli-only ceremonies inline: script and Plutus DReps, authoring each
action type, committee cold/hot key management, and the governance queries.

Delete the six cardano-cli pages and the sidebar category, point the operator
governance page at the consolidated sections, and retarget the old cli
governance redirects to the page.

The section split the same detection loop (poll an address, compare the
received amount) across three method pages plus an overview. Consolidate
into a single page with the methods as tabs: Blockfrost (recommended,
hosted), cardano-cli (own node), and cardano-wallet (REST service). Each
tab keeps the essential query-and-compare code and links out for the deeper
walkthrough (the Blockfrost point-of-sale app links to its starter repo).

Delete the three method pages, collapse the sidebar category to a single
entry, repoint the inbound link, and redirect the old prod URLs to the page.

Wallet Authentication was split across a concept page, a separate Mesh guide,
and an autogenerated UTXOS subtree. Roll it into one page: the concept, an
"implement it yourself" section with Mesh and Evolution in tabs, a hosted
sign-in section pointing to UTXOS as a service, and a zero-knowledge login
earmark for zklogin-aiken. Delete the Mesh and UTXOS pages, repoint inbound
links, and redirect their prod URLs to the page.

Broaden the Integrations "AI Agents" category to "AI" and add a highlighted
AI-assisted development page for Cardano Dev Skills, the plugin that gives AI
coding assistants current Cardano context. The overview now frames the two
scopes: AI as a development aid versus autonomous on-chain agents.

Fix the Token Registry sidebar so the category opens its overview directly
(the category-link pattern used everywhere else) instead of listing overview
as a separate item.

The languages/ subsection was mostly thin: only Aiken had real content, the
Plutarch subtree duplicated the Design Patterns data structures, and the rest
were install steps plus external links that Choose a Language already
aggregates.

Choose a Language becomes the single hub: its comparison table links out to
each language's official docs, and a compact "Getting started with Aiken"
section carries the install and learning resources. The language-agnostic DeFi
patterns the Plutarch dApps demonstrated (vesting, P2P/atomic swaps, reward
accrual, routing, bridges) fold into a new section on the DeFi page, each
composing the existing Design Patterns primitives and pointing to open-source
reference implementations.

Delete the languages/ tree, drop the Languages sidebar category, repoint
inbound links to the hub or upstream docs, and redirect the established prod
URLs (data structures to Design Patterns, the dApp patterns to the DeFi page).

Dev Blog appeared in both the Developers and Ecosystem menus; keep it in
Ecosystem only. Add a data-column-count="1" width rule so the simplified
Operators menu renders as a single narrow column instead of reserving three
columns of empty width.

Group Module 7's infrastructure pages under an Infrastructure category that
lands on the infrastructure overview. Reorder Community to Developer
Community, Talent Pool, Funding.

Reshape Module 5 (Build a dApp): Scaffolding, Connect a wallet, Wallet
Authentication, DeFi on Cardano, DeFi Kernel, Oracles. Add a Scaffolding page
(starter templates today plus the cardano-init tool in development), a DeFi
Kernel page (the open order-book standard), and a Cardano DeFi map link.

Stop naming specific third-party apps in conceptual prose. Generalize DeFi
protocols, wallets, and example tokens to categories, pointing to
cardano.org/apps for the live list. Developer tooling (SDKs, infra providers,
oracles) and hands-on tutorials keep their specifics.

Wrap the operator sidebar's eight setup steps under a Handbook category,
mirroring the developer Curriculum grouping, with Overview on top and
Operator Tools alongside.

Rename the navbar's Validators dropdown to Operators (matching the reorg)
and collapse it from seven enumerated steps to three high-level entries:
Overview, Handbook, and Operator Tools. The sidebar carries the depth.

Community had three overlapping docs. Careers re-listed the same channels,
pointed at Catalyst again, and duplicated the Contributing section and the
curriculum. Funding led with Project Catalyst and a Builder DAO that no
longer operates, then a prescriptive "which door do I use" tab flow that
broke once Catalyst paused.

Fold the useful parts of Careers (ecosystem entities, founding-entity job
boards) into a Jobs section on the Developer Community page and drop the
rest. Rewrite Funding as a neutral map of the current avenues: Catalyst,
on-chain treasury withdrawals, Intersect grants, the Maintainer Retainer
Program, and other paths to watch, each linking out for live status rather
than baking in transient state. Talent Pool stays its own landing.

Repoint the footer Careers link and the careers redirects to the Community
page.

The folder structure never caught up with the curriculum. Readers saw a
clean module path in the sidebar while the files still sat in legacy
buckets (learn/, value/, foundations/, get-started/) next to build/ and
native-tokens/. Contributors had to hold two mental models.

Collapse everything into the structure readers actually navigate:

- docs/developers/ holds the developer sidebar: a curriculum/ tree with
  numbered module folders (01-fundamentals through 07-production) plus an
  integrations/ section. Numeric prefixes order the tree; Docusaurus
  strips them so URLs stay clean.
- docs/operators/ holds the stake pool content (was operate-a-stake-pool/)
  plus a security/ folder for the air-gap and secure-workflow guides.
- community/ and contribute/ stay top-level as cross-cutting meta.

No get-started/, infrastructure/, learn/, build/, value/, foundations/,
or first-steps/ buckets survive. Shared node pages live once under
Module 7 and the operators sidebar cross-links them.

Mechanics: ~260 file moves, every internal /docs/ link rewritten by
prefix, sidebars.js re-keyed (networkSidebar is now operatorsSidebar),
redirect targets repointed so old prod URLs resolve straight to the
final location, and the llms path-fix script and includeOrder globs
updated. Old prod URLs keep working through redirects; curriculum-spine
URLs were never published so they need none.

The developer sidebar groups the seven modules under a Curriculum
category so the navigation mirrors the developers/curriculum/ tree, with
Start Here on top and Integrations/Community/Contributing alongside.

Also drops the two orphaned cardano-wallet REST-server pages. They sat in
no sidebar, taught the legacy run-your-own-wallet-backend approach the
curriculum already covers through SDKs and API providers, and only the
payments-listening guide referenced them (now pointed at the upstream repo).

The Governance section duplicated cardano.org/governance, which is the
participant hub for delegating votes, becoming a DRep, and reading the
constitution. None of that is dev-facing, so the section earned its
keep only through the cardano-cli guides buried inside it.

Fold the build-relevant material into Module 6 (Staking & Governance):
pull the cardano-cli guides under build/staking-governance/cardano-cli/,
move the Conway thresholds and ratification lifecycle into the Module 6
governance page, and point every participation reference out to
cardano.org/governance. Drop the section sidebar, the homepage bento
card link, and the navbar dropdown; repoint redirects so old governance
URLs land on Module 6.

The Token Registry lived in a build/native-tokens/ subfolder of fourteen wiki-imported pages: URL-encoded filenames, two near-identical "prepare an entry" guides, one-paragraph FAQ stubs, and an orphan parent page that duplicated the whole thing. Rewrite it as three pages under native-tokens/token-registry/: an overview (what the registry is, CIP-26 vs CIP-68), a single register-an-entry guide (prepare, submit, update, remove, with the FAQ folded into a troubleshooting tail), and the metadata server API reference. No technical content dropped, just de-duplicated and brought up to the curriculum's bar. The sidebar is explicit, the canonical old URLs redirect, and the two inbound links are repointed.

Three module overviews (smart contracts, staking & governance, scaling) closed twice: a curated Next steps list followed by a redundant trailing DocCardList that just re-listed the sidebar. Drop the trailing DocCardList so the build modules all match Native Tokens, a curated Next steps and nothing after it. Also fix a stale "Learn -> Core Concepts" reference in the IoT intro that pointed at a bucket the curriculum no longer has.

The Developers mega menu duplicated every topic the curriculum now sequences, three crowded columns of links. Cut it to two: Learn & Build (Start Here, Builder Tools) and Get Involved (Community, Grants & Funding, Talent Pool, Dev Blog). On the homepage, give the hero the Start Here button it never had and reframe the Get Started bento card as the curriculum entry.

Add CardanoKit, a Swift library for Cardano wallet and transaction
support in iOS/macOS apps, under the SDKs & Libraries category.

Also add `swift` to the language property taxonomy (its first use).

- Replace the templated "Concept | Web2 equivalent" grids across the
  conceptual pages with prose that keeps the single strongest analogy.
  The grids read as low-signal filler and several cells were loose.
- Fix the misleading cells while converting: Ethereum "contract storage
  = datum", invalid_hereafter as a JWT exp claim, and native tokens'
  "transfer can fail in logic? No".
- Rewrite the native-tokens ERC-20 comparison as prose that keeps the
  nuance (native transfers can't fail in contract logic, but tokens at a
  script address can).
- Add a "when to use a table" rule to the style guide.

* Fix Builder Tools filter to AND across facet groups

Combine category, language, and interface with AND across groups and OR within a group, so selecting a category plus a language returns the overlap instead of the union.

* Keep Builder Tools filter controls in view while filtering

The /tools page swaps from a tall "browse" layout to a short "filtered"
layout when a filter is applied; the document collapses and the browser
clamps the scroll position toward the top, which reads as a jump-to-top.
(Docusaurus itself does not scroll on query-only URL changes.)

- Make the search/filter/sort bar sticky so the controls stay in view
  through the reflow instead of disappearing.
- Switch the filter/sort/intent controls from history.push to
  history.replace so toggling filters no longer fills the back stack.

* Comment why the Builder Tools controls bar is sticky

Records the content-collapse rationale in the code so it isn't only in
the commit history.

Records the content-collapse rationale in the code so it isn't only in
the commit history.

The /tools page swaps from a tall "browse" layout to a short "filtered"
layout when a filter is applied; the document collapses and the browser
clamps the scroll position toward the top, which reads as a jump-to-top.
(Docusaurus itself does not scroll on query-only URL changes.)

- Make the search/filter/sort bar sticky so the controls stay in view
  through the reflow instead of disappearing.
- Switch the filter/sort/intent controls from history.push to
  history.replace so toggling filters no longer fills the back stack.

- Module 5 and 7 open on their own overview pages instead of a sub-page;
  the old pages stay reachable as children and Module 7's redundant
  Scaling subcategory is dissolved.
- Rename the seven modules to a consistent action voice (Learn the
  Fundamentals, Mint Tokens & NFTs, Write Smart Contracts, Add Staking
  & Governance, Ship to Production); page titles stay descriptive.
- Re-sync the Get Started curriculum table to the new names and links.
- Fold the standalone Exchange Integrations into the Integrations group.

Combine category, language, and interface with AND across groups and OR within a group, so selecting a category plus a language returns the overlap instead of the union.

Add an in-development stub for formal verification in the Smart Contracts module, featuring Blaster (Lean 4 proof automation), with the Lean-blaster repo to track progress.

Drop the Infrastructure and Providers wrapper and surface its children directly; add a developer run-your-own-node page that hands off to the operator curriculum; remove installing/running/topology from the developer sidebar; delete the duplicate infrastructure overview and redirect it; move Mithril out of Scaling into the operator Operator Tools.

Rewrite the 327-line overview into a high-level overview that links the submodules instead of duplicating them; move the collateral mechanics into lock-and-spend; keep the inbound anchors stable.