This playbook walks contributors through adding a new National Competent Authority (NCA) section under national-adaptations/. It mirrors the conventions established by the existing NCA sections (BaFIN, CBI, CSSF, DNB, AFM, AMF, DFSA) so that the new section drops cleanly into the site’s navigation and search.

• Create the folder at national-adaptations/<CC>/<nca-slug>/, where <CC> is the uppercase ISO 3166-1 alpha-2 country code (e.g. DE, FR, NL) and <nca-slug> is the lowercase acronym of the authority (e.g. bafin, cbi, cssf, dnb, afm, amf, dfsa).
• Document filenames are kebab-case, descriptive, and free of dates (e.g. casp-application-form-article-62.md, circular-cssf-25-875.md). They become the URL slug, so keep them concise and stable.

After creating the folder, register it in _nav.json:

• Append the slug to nca_order in the position you want it to appear.
• Add an nca_labels entry with the acronym or display label, e.g. "bafin": "BaFin".

Explicit registration in _nav.json is mandatory — unregistered NCA folders are silently excluded from the generated navigation.

Every NCA folder has a README.md that serves as the section index. Required pieces:

Frontmatter

---
title: "Full Authority Name (ACRONYM)"
shortTitle: "ACRONYM — Country"
type: index
---

shortTitle is what shows in the left-nav. type: index marks this as the folder’s landing page.

Body

1. # <Full Authority Name> H1 heading.
2. One short paragraph identifying the authority, the Member State, its role under MiCAR (CASP supervisor, ART/EMT supervisor, conduct vs. prudential), and the national designation instrument if relevant (e.g. “designated under S.I. No. 607/2024 (Article 93(1) MiCAR)”).
3. An Official MiCAR pages block linking the authority’s main MiCA hub(s) — use a single bold line if there is one URL, or a bullet list for multiple.
4. A ## Publications section (or topic-split sections like ## MiCAR guidance + ## Circulars) listing every document page in the folder. Each entry is a Markdown link with a human-readable label that matches the document’s title.

Keep the labels in the README in sync with the documents’ title frontmatter — readers and the SUMMARY generator both depend on this.

Each document page covers one piece of NCA output (a guidance note, a circular, an application form, a key-facts template, an FAQ, etc.).

Required frontmatter

---
title: "Full document title as published by the NCA"
shortTitle: "ACRONYM: Short label for nav"
type: nca-guidance        # or nca-circular for numbered circulars
status: Published
source_page: "https://<NCA URL of the document>"
---

Optional fields seen in existing pages:

• id: — official reference number for circulars, e.g. "CSSF 25/875".
• published: — date string ("2025-02-05" or "2025") when the NCA published the document.

shortTitle is what appears in the SUMMARY left-nav; keep it under ~50 characters and prefix it with the NCA acronym so it is recognisable in the flat nav list.

Body structure

1. # <Document title> H1 — match the title frontmatter exactly.

2. A blockquote header line with either > **[Link to NCA page →](URL)** or, for dated/numbered items, > **Reference:** XX/YY · **Published:** YYYY-MM-DD · **[Link →](URL)**.

3. ## What this document covers — one paragraph (3–6 sentences) summarising what the NCA actually published. Stay factual; do not paraphrase MiCAR itself.

4. ## Key provisions — bullet list of the substantive points the NCA makes. Aim for 5–8 bullets. Reference MiCA article numbers inline where helpful.

5. ## Relevant MiCA articles — a list of the MiCA articles the document touches. Each entry is a Markdown link into ../../mica/... with a one-line description. Example:

   [Article 62](../../mica/title-v-authorisation-and-operating-conditions-for-crypto-asset-service-providers-art.-59-85/chapter-1/article-62.md) - Application for CASP authorisation.

   The relative path is ../../mica/<title-folder>/<chapter-folder?>/article-N.md. Check the existing pages for the exact title-folder slugs — they are long and unforgiving of typos.

6. ## Source — bullet list with the canonical NCA URL(s) for the document.

Look at bafin/services-and-activities-in-connection-with-crypto-assets-in-accordance-with-micar.md for a clean reference of the nca-guidance shape and cssf/circular-cssf-25-875.md for an nca-circular example.

NCAs publish MiCA material in inconsistent places. Useful starting points:

• Direct URL hunt: try <nca-domain>/<en|fr|de>/mica, /micar, /crypto-assets, /markets-in-crypto-assets. Most NCAs have a dedicated MiCAR hub page that links everything they publish.
• Search the NCA site for MiCAR, MiCA, crypto-asset, Article 62, CASP, ART, EMT, white paper. Add the year (MiCAR 2025) to surface newer circulars.
• Browse the legal/regulation index. Most NCAs publish circulars and decisions under a “Laws and regulations”, “Circulars”, or “Publications” tree — look for crypto-tagged entries.
• Check the NCA’s English pages. Translations sometimes lag the national language; cross-check both if you read the local language.
• Cross-reference with ESMA’s register of NCAs (https://www.esma.europa.eu/) and the EBA’s competent-authority list to confirm the authority’s MiCAR scope (CASP, ART, EMT, or a split).
• Watch for twin-peaks splits. In countries like the Netherlands (AFM + DNB) and others where conduct and prudential supervision are separated, each authority has its own MiCAR pages — make sure you are reading the right one for the topic.

For each document you add, capture the deep URL of the document itself (not just the hub) in source_page so the page is verifiable even if the hub layout changes.

The site’s left-nav (SUMMARY.md) is generated. After adding or editing any NCA file:

node scripts/build-summary.js

This rewrites SUMMARY.md from the configured MiCA sections, definitions/, and blog/, picking up registered NCA files from national-competent-authorities/.

Inspect the diff:

git status
git diff SUMMARY.md _nav.json

Commit and push:

git add national-adaptations/<CC>/<nca-slug>/ _nav.json SUMMARY.md
git commit -m "docs: add <ACRONYM> NCA section"
git push origin main

Use a meaningful commit subject — recent commit history follows the feat: add <NCA> sections / docs: ... style.

• Folder national-adaptations/<CC>/<nca-slug>/ created with uppercase country code and lowercase acronym slug.
• _nav.json updated: slug in nca_order, label in nca_labels.
• README.md has title, shortTitle, type: index frontmatter and links every document in the folder.
• Each document page has title, shortTitle, type: nca-guidance (or nca-circular), status: Published, and source_page frontmatter.
• Each document page has the five body sections: link header, What this document covers, Key provisions, Relevant MiCA articles, Source.
• MiCA article links resolve (relative paths into ../../mica/...).
• node scripts/build-summary.js ran clean and SUMMARY.md reflects the new entries.
• Commit staged, pushed to main.