diff --git a/.bestpractices.json b/.bestpractices.json
index 0f8203d0c..d2a52957c 100644
--- a/.bestpractices.json
+++ b/.bestpractices.json
@@ -18,7 +18,7 @@
 	"osps_br_07_01_status": "Met",
 	"osps_br_07_01_justification": "GitHub secret scanning with push protection is enabled, TruffleHog scans every pull request (https://github.com/brazilian-utils/javascript/blob/main/.github/workflows/security.yml) and .env files are git-ignored.",
 	"osps_do_01_01_status": "Met",
-	"osps_do_01_01_justification": "https://brazilian-utils.com.br/getting-started and https://brazilian-utils.com.br/utilities document every utility, in English and Portuguese.",
+	"osps_do_01_01_justification": "https://brazilian-utils.com.br/libs/javascript/ and the utility pages it links to (https://brazilian-utils.com.br/utils/cpf/, ...) document every utility, in English and Portuguese; the sources are docs/utilities.md and docs/pt-br/utilities.md.",
 	"osps_do_02_01_status": "Met",
 	"osps_do_02_01_justification": "https://github.com/brazilian-utils/javascript/blob/main/SUPPORT.md and the bug report issue template: https://github.com/brazilian-utils/javascript/issues/new/choose",
 	"osps_gv_02_01_status": "Met",
@@ -44,7 +44,7 @@
 	"osps_qa_05_01_status": "Met",
 	"osps_qa_05_01_justification": "Build output (dist) is git-ignored; nothing generated and executable is committed.",
 	"osps_qa_05_02_status": "Met",
-	"osps_qa_05_02_justification": "The only binary files are two small PNG images of the docs site (docs/images), reviewable as images.",
+	"osps_qa_05_02_justification": "The repository has no binary files: everything committed is text, reviewable in a diff.",
 	"osps_vm_02_01_status": "Met",
 	"osps_vm_02_01_justification": "https://github.com/brazilian-utils/javascript/blob/main/SECURITY.md#reporting-a-vulnerability",
 	"osps_ac_04_01_status": "Met",
@@ -76,7 +76,7 @@
 	"osps_sa_01_01_status": "Met",
 	"osps_sa_01_01_justification": "https://github.com/brazilian-utils/javascript/blob/main/CONTRIBUTING.md#architecture",
 	"osps_sa_02_01_status": "Met",
-	"osps_sa_02_01_justification": "The public API is documented at https://brazilian-utils.com.br/utilities and checked on every pull request against the last npm release, which fails on a breaking change and lists every added, removed and changed declaration: https://github.com/brazilian-utils/javascript/blob/main/CONTRIBUTING.md#public-api-validation",
+	"osps_sa_02_01_justification": "The public API is documented at https://brazilian-utils.com.br/libs/javascript/ and checked on every pull request against the last npm release, which fails on a breaking change and lists every added, removed and changed declaration: https://github.com/brazilian-utils/javascript/blob/main/CONTRIBUTING.md#public-api-validation",
 	"osps_sa_03_01_status": "Met",
 	"osps_sa_03_01_justification": "https://github.com/brazilian-utils/javascript/blob/main/SECURITY.md#threat-model",
 	"osps_vm_01_01_status": "Met",
@@ -142,9 +142,9 @@
 	"license_location_status": "Met",
 	"license_location_justification": "https://github.com/brazilian-utils/javascript/blob/main/LICENSE",
 	"documentation_basics_status": "Met",
-	"documentation_basics_justification": "https://brazilian-utils.com.br/getting-started",
+	"documentation_basics_justification": "https://brazilian-utils.com.br/libs/javascript/",
 	"documentation_interface_status": "Met",
-	"documentation_interface_justification": "https://brazilian-utils.com.br/utilities documents every exported function; API Extractor fails CI on an undocumented export: https://github.com/brazilian-utils/javascript/blob/main/CONTRIBUTING.md#public-api-validation",
+	"documentation_interface_justification": "https://brazilian-utils.com.br/libs/javascript/ documents every exported function; API Extractor fails CI on an undocumented export: https://github.com/brazilian-utils/javascript/blob/main/CONTRIBUTING.md#public-api-validation",
 	"sites_https_status": "Met",
 	"sites_https_justification": "The site, the repository and the npm package are HTTPS only.",
 	"discussion_status": "Met",
@@ -280,9 +280,9 @@
 	"documentation_security_status": "Met",
 	"documentation_security_justification": "https://github.com/brazilian-utils/javascript/blob/main/SECURITY.md#whats-in-scope and https://github.com/brazilian-utils/javascript/blob/main/SECURITY.md#threat-model",
 	"documentation_quick_start_status": "Met",
-	"documentation_quick_start_justification": "https://brazilian-utils.com.br/getting-started",
+	"documentation_quick_start_justification": "https://brazilian-utils.com.br/libs/javascript/",
 	"documentation_current_status": "Met",
-	"documentation_current_justification": "The docs are checked in CI: the Check workflow runs the llms.txt generator over them on every run, so a missing docs file fails it, jsr.json fails it when stale, an undocumented export fails the public API check, and a pull request that changes a utility must update both language versions.",
+	"documentation_current_justification": "The docs are checked in CI: the Check workflow generates the examples of the guides from their templates on every run, so a broken template fails it, jsr.json fails it when stale, an undocumented export fails the public API check, and a pull request that changes a utility must update both language versions.",
 	"documentation_achievements_status": "Met",
 	"documentation_achievements_justification": "The README links the OpenSSF Best Practices and Scorecard badges: https://github.com/brazilian-utils/javascript#readme",
 	"accessibility_best_practices_status": "Unmet",
@@ -292,7 +292,7 @@
 	"sites_password_security_status": "N/A",
 	"sites_password_security_justification": "The project sites store no passwords; authentication is GitHub's and npm's.",
 	"maintenance_or_update_status": "Met",
-	"maintenance_or_update_justification": "1.x names are kept as deprecated aliases in 2.x and the upgrade is documented: https://brazilian-utils.com.br/migration-v1-to-v2",
+	"maintenance_or_update_justification": "1.x names are kept as deprecated aliases in 2.x and the upgrade is documented: https://brazilian-utils.com.br/guides/javascript/migration-v1-to-v2/",
 	"vulnerability_report_credit_status": "N/A",
 	"vulnerability_report_credit_justification": "No vulnerability was resolved in the last 12 months; SECURITY.md commits to crediting reporters.",
 	"vulnerability_response_process_status": "Met",
@@ -374,7 +374,7 @@
 	"test_branch_coverage80_status": "Met",
 	"test_branch_coverage80_justification": "100% branch coverage, enforced in CI.",
 	"hardened_site_status": "Unmet",
-	"hardened_site_justification": "The documentation site is served by GitHub Pages, which does not let a project set Content-Security-Policy, HSTS or X-Content-Type-Options headers.",
+	"hardened_site_justification": "The documentation site, https://brazilian-utils.com.br, is built from https://github.com/brazilian-utils/docs and served by Cloudflare Pages; it sends X-Content-Type-Options: nosniff, but no Content-Security-Policy or HSTS header yet.",
 	"security_review_status": "Met",
 	"security_review_justification": "The maintainers reviewed the security requirements and boundaries in September 2026 and recorded the result as the threat model and policies in https://github.com/brazilian-utils/javascript/blob/main/SECURITY.md",
 	"code_review_standards_status": "Met",
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index ca59c2741..d273d919e 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -10,7 +10,6 @@
   - [ ] `docs/utilities.md` (English)
   - [ ] `docs/pt-br/utilities.md` (Portuguese)
 - [ ] `npm run check` passes locally (format, lint, types).
-- [ ] I ran `npm run build:llms` if I touched `docs/utilities.md` (the Check workflow fails when `docs/llms.txt` is stale).
 - [ ] This change does not introduce a breaking change, **or** I flagged it clearly below and it was discussed with maintainers beforehand.
 - [ ] This change does not add any runtime dependency (this library is zero-runtime-dependency by design).
 
diff --git a/.github/workflows/check.yml b/.github/workflows/check.yml
index f0cea14de..a2455cc7a 100644
--- a/.github/workflows/check.yml
+++ b/.github/workflows/check.yml
@@ -53,16 +53,13 @@ jobs:
       - name: Validate the public API
         run: npm run check:api
 
-      - name: Check llms.txt/llms-full.txt build from the docs
-        run: npm run build:llms
-
       - name: Check the JSR exports are up to date
         run: npm run build:jsr && git diff --exit-code -- jsr.json
 
-      - name: Build the documentation site
-        # The site is generated at deploy time (the Docs workflow), so nothing here can be stale;
-        # this only has to fail when a generator does.
-        run: npm run build:docs
+      - name: Generate the examples of the guides
+        # The docs site (brazilian-utils/docs) runs this before it reads `docs/`; the generated files
+        # are not committed, so this only has to fail when the generator does.
+        run: npm run build:examples
 
       - name: Check the VEX statements against the suppressed advisories
         run: npm run check:vex
diff --git a/.github/workflows/docs.yml b/.github/workflows/docs.yml
deleted file mode 100644
index 6c05f68cb..000000000
--- a/.github/workflows/docs.yml
+++ /dev/null
@@ -1,63 +0,0 @@
-# Builds the documentation site and publishes it to GitHub Pages. Everything the site needs that a
-# script can write - the per-page shells, the sitemap, llms.txt, llms-full.txt and the examples of
-# the document field page - is written here rather than kept in the repository, so a page and what
-# it is generated from can never disagree.
-#
-# This needs Pages set to "GitHub Actions" (Settings -> Pages -> Build and deployment -> Source);
-# serving the branch directly would publish `docs/` without these files.
-name: Docs
-
-on:
-  push:
-    branches: [main]
-    paths:
-      - docs/**
-      - scripts/**
-      - package.json
-      - .github/workflows/docs.yml
-  workflow_dispatch:
-
-concurrency:
-  group: pages
-  cancel-in-progress: false
-
-permissions:
-  contents: read
-
-jobs:
-  deploy:
-    name: Build and deploy
-    runs-on: ubuntu-latest
-    timeout-minutes: 15
-
-    permissions:
-      pages: write
-      id-token: write
-
-    environment:
-      name: github-pages
-      url: ${{ steps.deploy.outputs.page_url }}
-
-    steps:
-      - name: Checkout code
-        uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
-        with:
-          persist-credentials: false
-
-      - name: Setup
-        uses: ./.github/actions/setup
-
-      - name: Build the site
-        run: npm run build:docs
-
-      - name: Configure Pages
-        uses: actions/configure-pages@45bfe0192ca1faeb007ade9deae92b16b8254a0d # v6.0.0
-
-      - name: Upload the site
-        uses: actions/upload-pages-artifact@fc324d3547104276b827a68afc52ff2a11cc49c9 # v5.0.0
-        with:
-          path: docs
-
-      - name: Deploy to Pages
-        id: deploy
-        uses: actions/deploy-pages@368f82528645a54fb793d4d04e342629a3f51346 # v5.0.1
diff --git a/.github/zizmor.yml b/.github/zizmor.yml
index 27697cb21..890da5459 100644
--- a/.github/zizmor.yml
+++ b/.github/zizmor.yml
@@ -7,7 +7,6 @@ rules:
     ignore:
       - build.yml
       - check.yml
-      - docs.yml
       - datasets.yml
       - live-tests.yml
       - mutation.yml
diff --git a/.gitignore b/.gitignore
index 760402ec3..f78a0b1b1 100644
--- a/.gitignore
+++ b/.gitignore
@@ -18,16 +18,8 @@ reports
 # the one that pins this project's dependencies.
 deno.lock
 
-# The documentation site is generated by `npm run build:docs` and published by the Docs workflow:
-# only what a person writes is kept here.
-docs/*.html
-!docs/index.html
-docs/pt-br/*.html
-docs/guides/*.html
-docs/pt-br/guides/*.html
-docs/sitemap.xml
-docs/llms.txt
-docs/llms-full.txt
+# The examples the guides show are generated from templates by `npm run build:examples` (the docs
+# site, brazilian-utils/docs, runs it before reading `docs/`): only what a person writes is kept here.
 docs/snippets/document-field/generated/
 docs/snippets/address-form/*/cep-field.*
 docs/snippets/address-form/*/field.*
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 39fcad1c3..2592bf496 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -42,11 +42,8 @@ and is invoked through the `npm` scripts below, so you don't need to install any
 | `npm run test:chrome-browser`, `npm run test:firefox-browser`, `npm run test:edge-browser`, `npm run test:safari-browser` | Runs the test suite in real browsers via `vp test --browser.enabled`.                                                                                                                                                                                                    |
 | `npm run build`                                                                                                           | Builds the library for publishing with `vp pack` (also runs attw and publint over the built output).                                                                                                                                                                     |
 | `npm run build:data`                                                                                                      | Regenerates the datasets under `src/_internals/constants` from the IBGE/CONCLA sources (`scripts/data.ts`); run by the scheduled `Update datasets` workflow.                                                                                                             |
-| `npm run build:llms`                                                                                                      | Regenerates `docs/llms.txt` and `docs/llms-full.txt` from the docs (`scripts/llms.ts`). Generated at deploy time, not kept in the repository.                                                                                                                            |
-| `npm run build:site`                                                                                                      | Regenerates the per-page copies of `docs/index.html`, `docs/404.html` and `docs/sitemap.xml` from the sidebars (`scripts/site.ts`). Generated at deploy time, not kept in the repository.                                                                                |
 | `npm run build:jsr`                                                                                                       | Regenerates the `exports` of `jsr.json`, one per utility folder (`scripts/jsr.ts`); CI fails if they're out of date.                                                                                                                                                     |
-| `npm run build:docs`                                                                                                      | Runs the three generators of the site above, which is what the Docs workflow deploys and what a Vercel preview builds.                                                                                                                                                   |
-| `npm run build:examples`                                                                                                  | Regenerates the examples of the document field page from their templates (`scripts/examples.ts`). Generated at deploy time, not kept in the repository.                                                                                                                  |
+| `npm run build:examples`                                                                                                  | Regenerates the examples of the guides from their templates (`scripts/examples.ts`); the docs site runs it before reading `docs/`. Generated, not kept in the repository.                                                                                                |
 | `npm run check:dependencies`                                                                                              | Fails if `package.json` declares any runtime `dependencies` (this package ships zero by design).                                                                                                                                                                         |
 | `npm run check:tree-shaking`                                                                                              | Builds nothing; measures the single-import size of every export against `dist` (`scripts/tree-shaking.ts`). Run it after `npm run build` when you change a dataset, and update the bundle-size table in `docs/getting-started.md` / `docs/pt-br/getting-started.md`.     |
 | `npm run check:duplication`                                                                                               | Runs [jscpd](https://jscpd.dev) over `src` and `scripts`; any copy-pasted block of 5+ lines / 50+ tokens fails.                                                                                                                                                          |
@@ -179,7 +176,8 @@ example `formatSomething`):
    - `docs/pt-br/utilities.md` (Portuguese translation)
 
    Follow the existing format: a `###` heading with the function name under the `##` family it
-   belongs to, one sentence saying what it does (`llms.txt` indexes that sentence), a few short
+   belongs to (the docs site maps that heading to the utility's page, see
+   [Documentation](#documentation)), one sentence saying what it does, a few short
    bullets for the options and the return rules, a `javascript` code block showing example
    input/output, and a one-line `Source:` (`Fonte:` in Portuguese) with the official reference when
    there is one. Do not repeat what the Conventions section at the top of the file already says
@@ -187,11 +185,6 @@ example `formatSomething`):
    for every edge case, the reference is the place for what a caller needs. Keep both files in the
    same order.
 
-   After editing `docs/getting-started.md` or `docs/utilities.md`, run `npm run build:llms` to
-   regenerate `docs/llms.txt` and `docs/llms-full.txt` (see [llms.txt](https://llmstxt.org/)) and
-   check the result. The two files are built at deploy time and never committed; CI runs the
-   generator, which fails only when a docs file it reads is missing.
-
 6. If the utility is based on an official Brazilian specification/document (e.g. a government
    validation algorithm), link to the authoritative source in the code comment (`@see`) or PR
    description so reviewers can verify the implementation.
@@ -417,54 +410,48 @@ Every utility must keep working across all the runtimes this library targets:
 Avoid Node-specific APIs unless they are polyfilled/guarded, and prefer standard, widely available
 JavaScript/TypeScript features.
 
-## Documentation site
-
-`docs/` is the source of [brazilian-utils.com.br](https://brazilian-utils.com.br), served by GitHub
-Pages with [docsify](https://docsify.js.org): `docs/index.html` renders the Markdown in the
-browser, with `_sidebar.md`, `_navbar.md` and `_coverpage.md` as its navigation.
-
-- Only what a person writes lives in `docs/`: the `Docs` workflow runs `npm run build:docs` and
-  publishes the result to GitHub Pages, so the page shells, `sitemap.xml`, `llms.txt`,
-  `llms-full.txt` and the generated examples are never committed (and never stale). Run
-  `npm run build:docs` to see the site as it is published; a pull request that touches `docs/` or
-  `scripts/` gets the same build as a Vercel preview.
-- docsify runs in history mode, so every page is a real URL (`/getting-started`,
-  `/pt-br/utilities`) that search engines index on its own. GitHub Pages serves each one from a
-  copy of `index.html` next to the page (`getting-started.html`) that carries the page's own
-  title, description, canonical URL and hreflang pair, and `npm run build:site`
-  (`scripts/site.ts`) writes those copies, `404.html` and `sitemap.xml` from the sidebars and the
-  pages' front matter. Links from the hash-router era (`/#/getting-started?id=usage`) are
-  rewritten on load, so nothing out there breaks.
-- Every page starts with a front matter block with a quoted `title` and `description` (and
-  `keywords`), and has no `#` heading of its own: the plugin in `docs/index.html` turns the title
-  into the page's heading and the block feeds the page's metadata (a small wrapper there hands
-  the search plugin the same view, so the block never shows up in search results). Scripts read
-  the block through `scripts/front-matter.ts`.
-- The site's own CSS is `docs/styles.css`, linked by every shell: styles go there, not in a
-  `<style>` block of `index.html`.
-- The pages under `docs/examples/` show the files of `docs/snippets/`, one tab per framework and
-  one variant per document. Each example is complete on its own, so it can be copied as is, and
-  the live demo of the pair on screen runs that same file: `docs/snippets/live/index.html` takes
-  the files to compile in its query string and `run.js` compiles them in the browser. The demos
-  take their look from `docs/snippets/styles.css`.
-- The examples of the document field page are generated: `npm run build:examples`
-  (`scripts/examples.ts`) fills the templates of `docs/snippets/document-field/templates` from a
-  table of documents, so the shared mask is written once. Edit a template or the table: the files
-  under `generated/` are written by the build and are not in the repository. A template ends in
-  `.tmpl` (`schema/zod.ts.tmpl`) because its `@@placeholder@@` markers do not parse as the language
-  its name says: the suffix keeps it out of everything that walks the repository for source files.
-- `scripts/llms.ts` reads the title back out of the front matter, so `docs/llms.txt` and
-  `docs/llms-full.txt` keep their headings.
+## Documentation
+
+`docs/` holds the library's documentation as Markdown: `getting-started.md`, the `utilities.md`
+reference, the `guides/` and their Portuguese translations under `pt-br/`. It is not a site of its
+own anymore: [brazilian-utils.com.br](https://brazilian-utils.com.br), the documentation of every
+Brazilian Utils library, is built from it by the
+[brazilian-utils/docs](https://github.com/brazilian-utils/docs) repository, which reads:
+
+- `docs/utilities.md` and `docs/pt-br/utilities.md`, the reference: each `###` heading is a symbol
+  of the package (`### isValidCpf`), shown on the page of the contract function it implements
+  ([/utils/cpf/](https://brazilian-utils.com.br/utils/cpf/)) and on
+  [/libs/javascript/](https://brazilian-utils.com.br/libs/javascript/). Keep the headings the
+  exported names, so the site can map them.
+- `docs/guides/` and `docs/pt-br/guides/`, one page per guide
+  ([/guides/javascript/document-field/](https://brazilian-utils.com.br/guides/javascript/document-field/)).
+  A guide starts with a front matter block with a quoted `title` and `description` (and an
+  optional `order`) and has no `#` heading of its own. Its examples are
+  `<div class="example" data-name="React">` blocks, one per framework, optionally split into
+  `<div class="variant">`, each file a `<div class="file" data-file="…">` that includes a file of
+  `docs/snippets/` (`[cpf-field.tsx](../snippets/… ':include :type=code tsx')`); the site shows
+  them as tabs. A relative link to another guide becomes that guide on the site, a link to a
+  reference heading (`utilities.md#isvalidcpf`) the matching utility page, and any other relative
+  link the file on GitHub, so `getting-started.md` is linked as a file.
+- `docs/snippets/`, copied as it is: the files the guides include, and the live demos.
+  `docs/snippets/live/index.html` takes the files to compile in its query string and `run.js`
+  compiles them in the browser, so a demo runs exactly the code its page shows.
+  `docs/snippets/styles.css` lays a demo out; the site gives it its look.
+- The examples of the document field and address form guides are generated:
+  `npm run build:examples` (`scripts/examples.ts`) fills the templates of
+  `docs/snippets/document-field/templates` from a table of documents, so the shared mask is
+  written once, and the site runs it before reading `docs/`. Edit a template or the table: the
+  generated files are listed in `.gitignore` and are not in the repository. A template ends in
+  `.tmpl` (`schema/zod.ts.tmpl`) because its `@@placeholder@@` markers do not parse as the
+  language its name says: the suffix keeps it out of everything that walks the repository for
+  source files. The Check workflow runs the generator, so a broken template fails CI here.
 - Context7 indexes `docs/` as `/brazilian-utils/javascript`; `context7.json` says what it reads,
   and `.github/workflows/context7.yml` asks for a refresh when the docs change on `main`.
 
-Every pull request that touches `docs/` or `scripts/` gets a preview deployment on Vercel
-(`vercel.json`), with the URL posted as a comment. The file builds the site the way the Docs
-workflow does (`npm run build:docs`), serves
-`/getting-started` from `getting-started.html` like GitHub Pages does (`cleanUrls`), marks every
-response `noindex` and turns deployments of `main` off: production stays on GitHub Pages. To
-preview the site locally, point a static file server that resolves `/page` to `page.html`, the way
-GitHub Pages does, at `docs/`.
+The site reads the `main` branch of this repository, so a change shows there once it is merged and
+the site is built again. To see it before that, run the brazilian-utils/docs site with
+`USAGE_SOURCE=local`, which reads the checkouts under its `.repos/` folder instead (see its
+`site/README.md`).
 
 ## Commit messages
 
@@ -566,7 +553,7 @@ formatting, lint and types (`vp check`), the tests on every runtime, 100% covera
 score, duplicated code (jscpd), unused files and exports (knip), the public API check, bundle size
 per export (the tree-shaking report), the lockfile, known vulnerabilities (`audit-ci`,
 OSV-Scanner), CodeQL, the workflow linters, stale committed generated files (`jsr.json`), the
-`llms.txt` generator running and the commit messages.
+generator of the guides' examples running and the commit messages.
 
 **What the reviewer checks**, in this order:
 
diff --git a/README.md b/README.md
index b01684285..7487a63fc 100644
--- a/README.md
+++ b/README.md
@@ -3,7 +3,7 @@
 
 <p>Utilities for Brazilian data: CPF, CNPJ, CEP, boleto, Pix, holidays and more.</p>
 
-[📖 Documentation](https://brazilian-utils.com.br/getting-started)
+[📖 Documentation](https://brazilian-utils.com.br/libs/javascript/) · [🇧🇷 Leia em português](https://github.com/brazilian-utils/javascript/blob/main/README.pt-br.md)
 
 [![npm version](https://img.shields.io/npm/v/@brazilian-utils/brazilian-utils.svg)](https://www.npmjs.com/package/@brazilian-utils/brazilian-utils) [![Downloads per month](https://img.shields.io/npm/dm/@brazilian-utils/brazilian-utils.svg)](https://www.npmjs.com/package/@brazilian-utils/brazilian-utils) [![License: MIT](https://img.shields.io/github/license/brazilian-utils/javascript.svg)](https://github.com/brazilian-utils/javascript/blob/main/LICENSE)
 [![Zero dependencies](https://img.shields.io/badge/dependencies-0-brightgreen)](https://github.com/brazilian-utils/javascript/blob/main/CONTRIBUTING.md#zero-runtime-dependencies) [![TypeScript](https://img.shields.io/npm/types/@brazilian-utils/brazilian-utils)](https://www.npmjs.com/package/@brazilian-utils/brazilian-utils)
@@ -11,22 +11,6 @@
 
 </div>
 
-<!-- START doctoc generated TOC please keep comment here to allow auto update -->
-<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
-
-**Table of Contents**
-
-- [Getting Started](#getting-started)
-  - [Why Brazilian Utils](#why-brazilian-utils)
-  - [Installation](#installation)
-    - [Runtime support](#runtime-support)
-  - [Usage](#usage)
-  - [Development](#development)
-  - [Contributors](#contributors)
-  - [License](#license)
-
-<!-- END doctoc generated TOC please keep comment here to allow auto update -->
-
 # Getting Started
 
 Brazilian Utils is a zero-dependency library of small utilities for the day-to-day problems of building software for Brazil: validating, formatting, parsing and generating CPF, CNPJ, CEP, boleto, Pix, phone numbers, holidays and more.
@@ -73,10 +57,10 @@ import { isValidCpf } from "@brazilian-utils/brazilian-utils";
 isValidCpf("1232454233345"); // false
 ```
 
-The [utilities reference](https://brazilian-utils.com.br/utilities) lists every function, grouped by family, with its options and examples.
+The [utilities reference](https://brazilian-utils.com.br/libs/javascript/) lists every function, grouped by family, with its options and examples. The [guides](https://brazilian-utils.com.br/guides/) show a CPF field, an address form and more in React, Angular, Vue and plain JavaScript, and the [migration guide](https://brazilian-utils.com.br/guides/javascript/migration-v1-to-v2/) covers the move from v1.
 
-- Using an AI coding assistant? The docs are indexed on Context7 as [`/brazilian-utils/javascript`](https://context7.com/brazilian-utils/javascript), and [llms.txt](https://brazilian-utils.com.br/llms.txt) lists every util for other tools. See [AI assistants](https://brazilian-utils.com.br/getting-started?id=ai-assistants).
-- The package is tree-shakeable. Every util is also available as its own subpath (e.g. `@brazilian-utils/brazilian-utils/get-cities`) so you can lazy-load the few heavy ones. See [Bundle size](https://brazilian-utils.com.br/getting-started?id=bundle-size).
+- Using an AI coding assistant? The docs are indexed on Context7 as [`/brazilian-utils/javascript`](https://context7.com/brazilian-utils/javascript), and [llms.txt](https://brazilian-utils.com.br/llms.txt) lists every util for other tools. See [AI assistants](https://github.com/brazilian-utils/javascript/blob/main/docs/getting-started.md#ai-assistants).
+- The package is tree-shakeable. Every util is also available as its own subpath (e.g. `@brazilian-utils/brazilian-utils/get-cities`) so you can lazy-load the few heavy ones. See [Bundle size](https://github.com/brazilian-utils/javascript/blob/main/docs/getting-started.md#bundle-size).
 
 ## Development
 
diff --git a/README.pt-br.md b/README.pt-br.md
new file mode 100644
index 000000000..2d21e643f
--- /dev/null
+++ b/README.pt-br.md
@@ -0,0 +1,86 @@
+<div align="center">
+<img src="https://raw.githubusercontent.com/brazilian-utils/brand/main/github-hero/github-hero-js.png" width="100%" alt="Brazilian Utils" />
+
+<p>Utilitários para dados brasileiros: CPF, CNPJ, CEP, boleto, Pix, feriados e mais.</p>
+
+[📖 Documentação](https://brazilian-utils.com.br/pt-br/libs/javascript/) · [🇺🇸 Read in English](https://github.com/brazilian-utils/javascript/blob/main/README.md)
+
+[![npm version](https://img.shields.io/npm/v/@brazilian-utils/brazilian-utils.svg)](https://www.npmjs.com/package/@brazilian-utils/brazilian-utils) [![Downloads per month](https://img.shields.io/npm/dm/@brazilian-utils/brazilian-utils.svg)](https://www.npmjs.com/package/@brazilian-utils/brazilian-utils) [![License: MIT](https://img.shields.io/github/license/brazilian-utils/javascript.svg)](https://github.com/brazilian-utils/javascript/blob/main/LICENSE)
+[![Zero dependencies](https://img.shields.io/badge/dependencies-0-brightgreen)](https://github.com/brazilian-utils/javascript/blob/main/CONTRIBUTING.md#zero-runtime-dependencies) [![TypeScript](https://img.shields.io/npm/types/@brazilian-utils/brazilian-utils)](https://www.npmjs.com/package/@brazilian-utils/brazilian-utils)
+[![Build Status](https://github.com/brazilian-utils/javascript/actions/workflows/build.yml/badge.svg?branch=main)](https://github.com/brazilian-utils/javascript/actions/workflows/build.yml?query=branch%3Amain) [![Tests](https://github.com/brazilian-utils/javascript/actions/workflows/tests.yml/badge.svg?branch=main)](https://github.com/brazilian-utils/javascript/actions/workflows/tests.yml?query=branch%3Amain) [![codecov](https://codecov.io/gh/brazilian-utils/javascript/branch/main/graph/badge.svg)](https://codecov.io/gh/brazilian-utils/javascript) [![Mutation tests](https://github.com/brazilian-utils/javascript/actions/workflows/mutation.yml/badge.svg?branch=main)](https://github.com/brazilian-utils/javascript/actions/workflows/mutation.yml?query=branch%3Amain) [![OpenSSF Scorecard](https://api.scorecard.dev/projects/github.com/brazilian-utils/javascript/badge)](https://scorecard.dev/viewer/?uri=github.com/brazilian-utils/javascript) [![OpenSSF Best Practices](https://www.bestpractices.dev/projects/14695/badge)](https://www.bestpractices.dev/projects/14695)
+
+</div>
+
+# Introdução
+
+Brazilian Utils é uma biblioteca de utilitários, sem dependências, para os problemas do dia a dia de quem desenvolve software para o Brasil: validar, formatar, interpretar e gerar CPF, CNPJ, CEP, boleto, Pix, telefone, feriados e mais.
+
+## Por que Brazilian Utils
+
+- **Zero dependências de runtime.** Nada além da biblioteca entra no seu `node_modules` ou no seu bundle.
+- **Tree-shakeable até a função.** `import { isValidCpf }` custa cerca de 0,5 KB minificado (0,3 KB com gzip). Cada utilitário também é um subpath próprio, então os pesados podem ser carregados sob demanda.
+- **Roda em qualquer lugar.** Node.js `^20.19.0 || >=22.12.0`, Bun, Deno e navegadores modernos, todos testados no CI.
+- **Escrita em TypeScript.** Os tipos vêm no pacote, e todo pull request é comparado com a última versão publicada para que a API pública nunca mude em silêncio.
+- **Validada contra as regras oficiais.** Cada validador cita a especificação, lei ou base de dados que implementa, e a suíte de testes passa por mutation testing, não só por cobertura.
+- **Documentada em inglês e português**, com um `llms.txt` para assistentes de IA.
+
+## Instalação
+
+```bash
+npm install @brazilian-utils/brazilian-utils
+```
+
+O mesmo pacote funciona com `yarn add`, `pnpm add` e `bun add`. Em uma tag `<script>` ele expõe a global `BrazilianUtils`:
+
+```html
+<script src="https://unpkg.com/@brazilian-utils/brazilian-utils/dist/brazilian-utils.umd.cjs"></script>
+```
+
+### Runtimes suportados
+
+A faixa suportada é o campo `engines` do `package.json`. Cada linha abaixo roda no [workflow de testes](https://github.com/brazilian-utils/javascript/actions/workflows/tests.yml?query=branch%3Amain) em todo pull request.
+
+| Runtime     | Suportado                 | Testado no CI                 |
+| ----------- | ------------------------- | ----------------------------- |
+| Node.js     | `^20.19.0 \|\| >=22.12.0` | 20, 22, 24, 26                |
+| Bun         | mais recente              | mais recente                  |
+| Deno        | 2.x                       | 2.x                           |
+| Navegadores | modernos                  | Chrome, Firefox, Edge, Safari |
+
+## Como usar
+
+Importe a função que precisar:
+
+```javascript
+import { isValidCpf } from "@brazilian-utils/brazilian-utils";
+
+isValidCpf("1232454233345"); // false
+```
+
+A [referência de utilitários](https://brazilian-utils.com.br/pt-br/libs/javascript/) lista todas as funções, agrupadas por família, com opções e exemplos. Os [guias](https://brazilian-utils.com.br/pt-br/guides/) mostram um campo de CPF, um formulário de endereço e mais em React, Angular, Vue e JavaScript puro, e o [guia de migração](https://brazilian-utils.com.br/pt-br/guides/javascript/migration-v1-to-v2/) explica como sair da v1.
+
+- Usa um assistente de código com IA? A documentação está indexada no Context7 como [`/brazilian-utils/javascript`](https://context7.com/brazilian-utils/javascript), e o [llms.txt](https://brazilian-utils.com.br/llms.txt) lista todos os utilitários para outras ferramentas. Veja [Assistentes de IA](https://github.com/brazilian-utils/javascript/blob/main/docs/pt-br/getting-started.md#assistentes-de-ia).
+- O pacote é tree-shakeable. Cada utilitário também está disponível como um subpath próprio (por exemplo, `@brazilian-utils/brazilian-utils/get-cities`), então dá para carregar sob demanda os poucos que são pesados. Veja [Tamanho do bundle](https://github.com/brazilian-utils/javascript/blob/main/docs/pt-br/getting-started.md#tamanho-do-bundle).
+
+## Desenvolvimento
+
+Este repositório usa o Vite+ como ferramenta local. Ele é instalado como dependência, então não é preciso instalar nada globalmente além do Node.js 24 (a versão do `.nvmrc`, que a ferramenta exige; a biblioteca em si suporta Node.js `^20.19.0 || >=22.12.0`).
+
+```bash
+npm install
+npm run check
+npm test
+npm run build
+```
+
+O [CONTRIBUTING.md](https://github.com/brazilian-utils/javascript/blob/main/CONTRIBUTING.md) lista todos os scripts e as verificações pelas quais um pull request passa.
+
+As notas de cada versão são publicadas nas [GitHub Releases](https://github.com/brazilian-utils/javascript/releases).
+
+## Contribuidores
+
+Nosso "obrigado" vai para [todas as pessoas que contribuíram](https://github.com/brazilian-utils/javascript/blob/main/README.md#contributors). Este projeto segue a especificação [all-contributors](https://github.com/kentcdodds/all-contributors), e contribuições de qualquer tipo são bem-vindas!
+
+## Licença
+
+[MIT](https://github.com/brazilian-utils/javascript/blob/main/LICENSE)
diff --git a/SUPPORT.md b/SUPPORT.md
index 0e89a8dca..5dde09b0c 100644
--- a/SUPPORT.md
+++ b/SUPPORT.md
@@ -3,7 +3,7 @@
 Thanks for using Brazilian Utils! Here's where to get help, depending on what you need:
 
 - **Documentation**: the full list of utilities, usage examples and migration guides live at
-  [brazilian-utils.com.br](https://brazilian-utils.com.br/getting-started).
+  [brazilian-utils.com.br](https://brazilian-utils.com.br/libs/javascript/).
 - **Questions & usage help**: open a [GitHub Discussion](https://github.com/brazilian-utils/javascript/discussions).
   This is the best place for "how do I...?" questions or to propose an idea before it becomes an issue.
 - **Bugs & feature requests**: use our [issue templates](https://github.com/brazilian-utils/javascript/issues/new/choose)
diff --git a/context7.json b/context7.json
index 2695103c8..31acaa8aa 100644
--- a/context7.json
+++ b/context7.json
@@ -13,14 +13,7 @@
 		"SECURITY.md",
 		"SUPPORT.md",
 		"MAINTAINERS.md",
-		"index.html",
-		"CNAME",
-		"_sidebar.md",
-		"_navbar.md",
-		"_coverpage.md",
-		"llms.txt",
-		"llms-full.txt",
-		"robots.txt"
+		"index.html"
 	],
 	"previousVersions": [
 		{
diff --git a/docs/.nojekyll b/docs/.nojekyll
deleted file mode 100644
index e69de29bb..000000000
diff --git a/docs/CNAME b/docs/CNAME
deleted file mode 100644
index 9edc0cdca..000000000
--- a/docs/CNAME
+++ /dev/null
@@ -1 +0,0 @@
-brazilian-utils.com.br
\ No newline at end of file
diff --git a/docs/_coverpage.md b/docs/_coverpage.md
deleted file mode 100644
index 1aa2343f8..000000000
--- a/docs/_coverpage.md
+++ /dev/null
@@ -1,12 +0,0 @@
-<img src="https://raw.githubusercontent.com/brazilian-utils/brand/main/logos/logo-js.svg" alt="Brazilian Utils" width="360"/>
-
-> Utilities for Brazilian data: CPF, CNPJ, CEP, boleto, Pix, holidays and more.
-
-- Zero runtime dependencies
-- Tree-shakeable, one import per util
-- Node.js, Bun, Deno and browsers
-- Typed, documented in English and Portuguese
-
-[Get Started](getting-started.md)
-[Utilities](utilities.md)
-[GitHub](https://github.com/brazilian-utils/javascript)
diff --git a/docs/_navbar.md b/docs/_navbar.md
deleted file mode 100644
index 2cf7864df..000000000
--- a/docs/_navbar.md
+++ /dev/null
@@ -1,2 +0,0 @@
-* [English](/)
-* [Português](/pt-br/)
diff --git a/docs/_sidebar.md b/docs/_sidebar.md
deleted file mode 100644
index 0b8026ed2..000000000
--- a/docs/_sidebar.md
+++ /dev/null
@@ -1,8 +0,0 @@
-* [Getting Started](getting-started.md)
-* [Utilities](utilities.md)
-* Guides
-  * [Document field](guides/document-field.md)
-  * [Address from a CEP](guides/address-form.md)
-  * [State and city](guides/state-city.md)
-  * [Schema libraries](guides/schema.md)
-* [Migration v1 to v2](guides/migration-v1-to-v2.md)
diff --git a/docs/getting-started.md b/docs/getting-started.md
index 2ebc24f01..5f2e6eb0f 100644
--- a/docs/getting-started.md
+++ b/docs/getting-started.md
@@ -58,7 +58,7 @@ Validate a CNPJ with Brazilian Utils. use library /brazilian-utils/javascript
 
 To stop repeating it, add a rule to the agent's instructions file (`CLAUDE.md`, Cursor rules or the equivalent): "For Brazilian document utils, use the Context7 library /brazilian-utils/javascript".
 
-Without Context7, point the assistant at [llms.txt](https://brazilian-utils.com.br/llms.txt), which lists every util with a one-line description, or at [llms-full.txt](https://brazilian-utils.com.br/llms-full.txt), the whole English documentation in one Markdown file.
+Without Context7, point the assistant at [llms.txt](https://brazilian-utils.com.br/llms.txt), which lists every utility page of the documentation site, or at [utilities.md](https://raw.githubusercontent.com/brazilian-utils/javascript/main/docs/utilities.md), the whole English reference in one Markdown file.
 
 ## Bundle size
 
diff --git a/docs/guides/address-form.md b/docs/guides/address-form.md
index 9f52bc288..60d42d36d 100644
--- a/docs/guides/address-form.md
+++ b/docs/guides/address-form.md
@@ -6,12 +6,12 @@ keywords: ["CEP lookup", "address by CEP", "autofill address", "getAddressInfoBy
 
 Type a CEP and the rest of the address fills itself. Pick the framework: each example runs the code below it, which you can copy as is.
 
-`getAddressInfoByCep` asks the CEP providers and returns the street, neighborhood, city and state, or throws when no one has that CEP. It is asked only once `isValidCep` says the CEP is complete, so a request is not made on every keystroke, and what comes back stays editable: a lookup fills a form, it does not own it. The [document field guide](guides/document-field.md) has the mask that keeps the caret where it belongs.
+`getAddressInfoByCep` asks the CEP providers and returns the street, neighborhood, city and state, or throws when no one has that CEP. It is asked only once `isValidCep` says the CEP is complete, so a request is not made on every keystroke, and what comes back stays editable: a lookup fills a form, it does not own it. The [document field guide](document-field.md) has the mask that keeps the caret where it belongs.
 
 
 <div class="example" data-name="React" data-demo="/snippets/live/?dir=address-form/react&example=address-form.tsx">
 
-A hook takes the CEP and gives back what is known about it; the form draws that. The CEP field is the one the [document field guide](guides/document-field.md) builds:
+A hook takes the CEP and gives back what is known about it; the form draws that. The CEP field is the one the [document field guide](document-field.md) builds:
 
 <div class="file" data-file="address-form.tsx">
 
@@ -29,7 +29,7 @@ A hook takes the CEP and gives back what is known about it; the form draws that.
 
 <div class="example" data-name="Angular" data-demo="/snippets/live/?dir=address-form/angular&example=address-form.ts">
 
-A `resource` takes the CEP and gives back what is known about it, reloading when it changes. The CEP field is the one the [document field guide](guides/document-field.md) builds:
+A `resource` takes the CEP and gives back what is known about it, reloading when it changes. The CEP field is the one the [document field guide](document-field.md) builds:
 
 <div class="file" data-file="address-form.ts">
 
@@ -47,7 +47,7 @@ A `resource` takes the CEP and gives back what is known about it, reloading when
 
 <div class="example" data-name="Vue" data-demo="/snippets/live/?dir=address-form/vue&example=address-form.vue">
 
-A composable takes the CEP and gives back what is known about it; the form draws that. The CEP field is the one the [document field guide](guides/document-field.md) builds:
+A composable takes the CEP and gives back what is known about it; the form draws that. The CEP field is the one the [document field guide](document-field.md) builds:
 
 <div class="file" data-file="address-form.vue">
 
diff --git a/docs/images/favicon.png b/docs/images/favicon.png
deleted file mode 100644
index bc7a2083c..000000000
Binary files a/docs/images/favicon.png and /dev/null differ
diff --git a/docs/images/logo.png b/docs/images/logo.png
deleted file mode 100644
index 9fd965d06..000000000
Binary files a/docs/images/logo.png and /dev/null differ
diff --git a/docs/index.html b/docs/index.html
deleted file mode 100644
index 696687f19..000000000
--- a/docs/index.html
+++ /dev/null
@@ -1,530 +0,0 @@
-<!doctype html>
-<html lang="en">
-
-<head>
-  <meta charset="utf-8" />
-  <title>Brazilian Utils</title>
-  <meta name="description" content="Zero-dependency, tree-shakeable utilities for Brazilian data: validate, format, parse and generate CPF, CNPJ, CEP, boleto, Pix, holidays and more." />
-  <meta name="viewport" content="width=device-width, initial-scale=1, viewport-fit=cover" />
-  <meta name="color-scheme" content="dark" />
-  <meta name="theme-color" content="#009739" />
-  <!-- Ownership proof for Google Search Console; removing it drops the verification. -->
-  <meta name="google-site-verification" content="8xH7xzJdpi19V6yr-QGvrZtAG84ihpVn_-yWd6DhpXg" />
-
-  <!-- Every page is a real URL (docsify runs in history mode, see the router note below), and the
-       hook further down rewrites the title, description, canonical, hreflang and Open Graph tags for
-       the page being shown; the values here are the home page's, what a crawler without JavaScript
-       and a link preview see. -->
-  <link rel="canonical" href="https://brazilian-utils.com.br/" />
-  <link rel="alternate" hreflang="en" href="https://brazilian-utils.com.br/" />
-  <link rel="alternate" hreflang="x-default" href="https://brazilian-utils.com.br/" />
-  <link rel="sitemap" type="application/xml" href="/sitemap.xml" />
-  <!-- The Markdown behind the site, for agents that look for it: the per-util index, the whole
-       English documentation in one file, and (rewritten per page by the hook) the page's own source -->
-  <link rel="alternate" type="text/plain" href="/llms.txt" title="llms.txt" />
-  <link rel="alternate" type="text/plain" href="/llms-full.txt" title="llms-full.txt" />
-  <link rel="alternate" type="text/markdown" href="https://raw.githubusercontent.com/brazilian-utils/javascript/main/README.md" title="Markdown source" />
-  <!-- docsify's scripts and styles load without CORS, so that preconnect must not be `crossorigin`;
-       the README is fetched with XHR, so that one must -->
-  <link rel="preconnect" href="https://cdn.jsdelivr.net" />
-  <link rel="preconnect" href="https://raw.githubusercontent.com" crossorigin />
-  <meta property="og:type" content="website" />
-  <meta property="og:site_name" content="Brazilian Utils" />
-  <meta property="og:title" content="Brazilian Utils" />
-  <meta property="og:description" content="Zero-dependency, tree-shakeable utilities for Brazilian data: validate, format, parse and generate CPF, CNPJ, CEP, boleto, Pix, holidays and more." />
-  <meta property="og:url" content="https://brazilian-utils.com.br/" />
-  <meta property="og:locale" content="en_US" />
-  <meta property="og:locale:alternate" content="pt_BR" />
-  <meta property="og:image" content="https://brazilian-utils.com.br/images/logo.png" />
-  <meta property="og:image:width" content="569" />
-  <meta property="og:image:height" content="291" />
-  <meta property="og:image:alt" content="Brazilian Utils" />
-  <meta name="twitter:card" content="summary_large_image" />
-  <script type="application/ld+json">
-    {
-      "@context": "https://schema.org",
-      "@graph": [
-        {
-          "@type": "WebSite",
-          "@id": "https://brazilian-utils.com.br/#website",
-          "url": "https://brazilian-utils.com.br/",
-          "name": "Brazilian Utils",
-          "description": "Zero-dependency, tree-shakeable utilities for Brazilian data: validate, format, parse and generate CPF, CNPJ, CEP, boleto, Pix, holidays and more.",
-          "inLanguage": ["en", "pt-BR"]
-        },
-        {
-          "@type": "SoftwareSourceCode",
-          "@id": "https://brazilian-utils.com.br/#library",
-          "name": "Brazilian Utils",
-          "description": "Zero-dependency, tree-shakeable utilities for Brazilian data: validate, format, parse and generate CPF, CNPJ, CEP, boleto, Pix, holidays and more.",
-          "url": "https://brazilian-utils.com.br/",
-          "codeRepository": "https://github.com/brazilian-utils/javascript",
-          "programmingLanguage": "TypeScript",
-          "runtimePlatform": ["Node.js", "Bun", "Deno", "Browser"],
-          "license": "https://github.com/brazilian-utils/javascript/blob/main/LICENSE",
-          "isPartOf": { "@id": "https://brazilian-utils.com.br/#website" }
-        }
-      ]
-    }
-  </script>
-
-  <!-- Router: docsify runs in history mode, so each page is a real URL (/getting-started,
-       /pt-br/utilities) that crawlers index on its own, instead of one URL with hash routes.
-       GitHub Pages serves /getting-started from getting-started.html, a copy of this shell that
-       `npm run build:site` (scripts/site.ts) keeps in sync, one per page listed in _sidebar.md.
-       Links from the hash-router era (/#/getting-started?id=usage) and .html URLs are rewritten
-       to their history-mode form before docsify reads the location. -->
-  <script>
-    (function () {
-      if (location.hash.indexOf('#/') === 0) {
-        history.replaceState(null, '', location.hash.slice(1));
-      } else if (/\.html$/.test(location.pathname)) {
-        history.replaceState(null, '', location.pathname.replace(/(index)?\.html$/, '') + location.search + location.hash);
-      }
-    })();
-  </script>
-
-  <link rel="icon" type="image/png" sizes="32x32" href="/images/favicon.png" />
-  <link rel="icon" type="image/png" sizes="16x16" href="https://raw.githubusercontent.com/brazilian-utils/brand/main/favicons/favicon-16x16.png" />
-  <link rel="apple-touch-icon" href="https://raw.githubusercontent.com/brazilian-utils/brand/main/favicons/apple-touch-icon.png" />
-
-  <!-- The docsify theme and the site's own styles, in one file shared with the live demos -->
-  <link rel="stylesheet" href="/styles.css" />
-</head>
-
-<body class="loading sidebar-chevron-right">
-  <div id="app"></div>
-  <noscript>
-    <p>
-      This site renders its Markdown in the browser and needs JavaScript. The same pages are available as
-      plain Markdown: <a href="/getting-started.md">getting started</a>, <a href="/utilities.md">utilities</a>,
-      <a href="/guides/migration-v1-to-v2.md">migration from v1 to v2</a> and the
-      <a href="/pt-br/getting-started.md">Portuguese version</a>, or in one file at <a href="/llms-full.txt">llms-full.txt</a>.
-    </p>
-  </noscript>
-
-  <!-- Configuration -->
-  <script>
-    window.$docsify = {
-      name: 'Brazilian Utils',
-      logo: 'https://raw.githubusercontent.com/brazilian-utils/brand/main/icons/icon-js.svg',
-      routerMode: 'history',
-      nameLink: {
-        '/pt-br/': '/pt-br/',
-        '/': '/'
-      },
-      alias: {
-        '/': 'https://raw.githubusercontent.com/brazilian-utils/javascript/main/README.md',
-        '/pt-br/': '/pt-br/getting-started.md',
-        // The guides live in a folder; they share their language's sidebar and navbar
-        '/guides/_sidebar.md': '/_sidebar.md',
-        '/guides/_navbar.md': '/_navbar.md',
-        '/pt-br/guides/_sidebar.md': '/pt-br/_sidebar.md',
-        '/pt-br/guides/_navbar.md': '/pt-br/_navbar.md'
-      },
-      repo: 'brazilian-utils/javascript',
-      loadNavbar: true,
-      loadSidebar: true,
-      auto2top: true,
-      subMaxLevel: 3,
-      // Resolved relative to the route's folder, so the Portuguese cover is `_coverpage.md`
-      // inside `pt-br/`, not `pt-br/_coverpage.md` (which docsify would fetch as
-      // `/pt-br/pt-br/_coverpage.md` and leave the cover blank).
-      coverpage: {
-        '/': '_coverpage.md',
-        '/pt-br/': '_coverpage.md'
-      },
-      search: {
-        paths: 'auto',
-        placeholder: {
-          '/pt-br/': 'Buscar',
-          '/': 'Search'
-        },
-        noData: {
-          '/pt-br/': 'Nenhum resultado',
-          '/': 'No results'
-        },
-        depth: 3
-      },
-      plugins: [
-        // Every page carries a front matter block (title, description, keywords) and no heading
-        // of its own; the front-matter plugin below strips the block, and this hook turns its
-        // title into the page's H1.
-        function (hook, vm) {
-          hook.beforeEach(function (content) {
-            var title = vm.frontmatter && vm.frontmatter.title;
-            return title ? '# ' + title + '\n\n' + content : content;
-          });
-        },
-        // The framework tabs of an example page, and the select that picks which document the
-        // examples are about: every <div class="example" data-name> is a tab, and every
-        // <div class="variant" data-variant data-demo> inside it is one document. The live demo of
-        // the pair on screen, an iframe of docs/snippets, loads the first time it is shown and is
-        // as tall as its content. Both choices are remembered.
-        function (hook) {
-          hook.doneEach(function () {
-            var panels = [].slice.call(document.querySelectorAll('.example[data-name]'));
-            if (panels.length === 0) return;
-
-            var remember = function (key, value) {
-              try { localStorage.setItem(key, value); } catch (error) {}
-            };
-            var remembered = function (key) {
-              try { return localStorage.getItem(key); } catch (error) { return null; }
-            };
-
-            var variantsOf = function (panel) {
-              return [].slice.call(panel.querySelectorAll('.variant[data-variant]'));
-            };
-
-            var frames = [];
-
-            // Each demo measures itself and posts its height (docs/snippets/live/run.js), so the
-            // frame is exactly as tall as what it runs, message by message.
-            addEventListener('message', function (event) {
-              if (event.origin !== location.origin || !event.data || event.data.type !== 'example-height') return;
-              frames.forEach(function (frame) {
-                if (event.source !== frame.contentWindow) return;
-                frame.style.height = event.data.height + (frame.offsetHeight - frame.clientHeight) + 'px';
-              });
-            });
-
-            // The files of one example, as an editor's tabs: one strip per variant, the file name
-            // on each tab, one file on screen.
-            var addFiles = function (holder) {
-              var files = [].slice.call(holder.querySelectorAll('.file[data-file]'));
-              if (files.length < 2 || holder.querySelector('.file-tabs')) return;
-
-              var strip = document.createElement('div');
-              strip.className = 'file-tabs';
-              strip.setAttribute('role', 'tablist');
-
-              var open = function (name) {
-                files.forEach(function (file, index) {
-                  var selected = file.dataset.file === name;
-                  file.hidden = !selected;
-                  strip.children[index].setAttribute('aria-selected', String(selected));
-                });
-              };
-
-              files.forEach(function (file) {
-                file.setAttribute('role', 'tabpanel');
-                var button = document.createElement('button');
-                button.type = 'button';
-                button.setAttribute('role', 'tab');
-                button.textContent = file.dataset.file;
-                button.addEventListener('click', function () { open(file.dataset.file); });
-                strip.appendChild(button);
-              });
-
-              files[0].parentNode.insertBefore(strip, files[0]);
-              open(files[0].dataset.file);
-            };
-
-            var addDemo = function (holder) {
-              if (!holder.dataset.demo || holder.querySelector('iframe')) return;
-              var frame = document.createElement('iframe');
-              frame.title = 'Live demo';
-              frame.src = holder.dataset.demo;
-              frames.push(frame);
-              // Whatever the page says before the code says what the demo is: the demo comes after
-              // it and before the code, wherever the page happens to keep the two.
-              holder.insertBefore(frame, holder.querySelector('.file, .variant'));
-            };
-
-            var current = { tab: null, variant: null };
-
-            var show = function () {
-              panels.forEach(function (panel, index) {
-                var selected = panel.dataset.name === current.tab;
-                list.children[index].setAttribute('aria-selected', String(selected));
-                panel.hidden = !selected;
-                var variants = variantsOf(panel);
-                if (variants.length === 0) {
-                  if (selected) { addDemo(panel); addFiles(panel); }
-                  return;
-                }
-                variants.forEach(function (variant) {
-                  variant.hidden = variant.dataset.variant !== current.variant;
-                  if (!selected || variant.hidden) return;
-                  addDemo(variant);
-                  addFiles(variant);
-                });
-              });
-              remember('example-tab', current.tab);
-              if (current.variant) remember('example-variant', current.variant);
-            };
-
-            var names = variantsOf(panels[0]).map(function (variant) {
-              return variant.dataset.variant;
-            });
-            var picker = null;
-
-            if (names.length > 0) {
-              picker = document.createElement('label');
-              picker.className = 'example-picker';
-              picker.textContent = document.documentElement.lang === 'pt-BR'
-                ? 'Escolha o documento que você quer ver:'
-                : 'Choose the document you want to see:';
-              var select = document.createElement('select');
-              names.forEach(function (name) {
-                var option = document.createElement('option');
-                option.value = name;
-                option.textContent = name;
-                select.appendChild(option);
-              });
-              select.addEventListener('change', function () {
-                current.variant = select.value;
-                show();
-              });
-              picker.appendChild(select);
-              current.variant = names.indexOf(remembered('example-variant')) === -1 ? names[0] : remembered('example-variant');
-              select.value = current.variant;
-            }
-
-            // The document is a question the guide asks before the tabs answer which framework,
-            // so it says so in words, on a line of its own above them.
-            if (picker) panels[0].parentNode.insertBefore(picker, panels[0]);
-
-            var tabs = document.createElement('div');
-            tabs.className = 'example-tabs';
-            panels[0].parentNode.insertBefore(tabs, panels[0]);
-
-            var list = document.createElement('div');
-            list.className = 'example-tab-list';
-            list.setAttribute('role', 'tablist');
-            tabs.appendChild(list);
-
-            panels.forEach(function (panel) {
-              panel.setAttribute('role', 'tabpanel');
-              var button = document.createElement('button');
-              button.type = 'button';
-              button.setAttribute('role', 'tab');
-              button.textContent = panel.dataset.name;
-              button.addEventListener('click', function () {
-                current.tab = panel.dataset.name;
-                show();
-              });
-              list.appendChild(button);
-            });
-
-            var saved = remembered('example-tab');
-            current.tab = panels.some(function (panel) { return panel.dataset.name === saved; })
-              ? saved
-              : panels[0].dataset.name;
-            show();
-          });
-        },
-        // The two language links of the navbar, pointed at the page on screen: switching the
-        // language keeps the route, its query string and its anchor (/utilities becomes
-        // /pt-br/utilities and back), instead of sending the reader to a home page. `_navbar.md`
-        // stays the source of the labels and of their order, and the link of the language being
-        // read is marked the way docsify marks an active navbar entry; only the `href` changes,
-        // so the navbar is still what the Markdown says.
-        // Every page exists in both languages (the `_sidebar.md` of each lists the same pages,
-        // and `scripts/site.ts` pairs them one by one in the hreflang links and in the sitemap),
-        // so the translated route is a page that answers. The two exceptions go to the other
-        // language's home: the home pages, which are not translations of each other (`/` is the
-        // README and `/pt-br/` shows pt-br/getting-started through `alias`), and a route no
-        // language has, where docsify shows its 404 view and there is nothing to translate.
-        function (hook, vm) {
-          var HOME = { 'en': '/', 'pt-br': '/pt-br/' };
-          // Where each link points for the page on screen, and which language that page is in.
-          var destination = { 'en': HOME['en'], 'pt-br': HOME['pt-br'] };
-          var reading = 'en';
-          var watched = [];
-          // The language a navbar link switches to, from the href `_navbar.md` gives it, kept on
-          // the element so the link is still recognised once its href points at a page.
-          function languageOf(link) {
-            var href = link.getAttribute('href');
-            return link.dataset.language || (href === HOME['pt-br'] ? 'pt-br' : href === HOME['en'] ? 'en' : '');
-          }
-          // The same route in a language, the home pages standing in for each other.
-          function translate(path, language) {
-            var english = path.replace(/^\/pt-br(?=\/|$)/, '') || '/';
-            return english === '/' ? HOME[language] : language === 'pt-br' ? '/pt-br' + english : english;
-          }
-          function rewrite() {
-            var links = document.querySelectorAll('.app-nav a[href], .app-nav-merged a[href]');
-            [].forEach.call(links, function (link) {
-              var language = languageOf(link);
-              if (!language) return;
-              link.dataset.language = language;
-              link.setAttribute('href', destination[language]);
-              if (language === reading) link.setAttribute('aria-current', 'page');
-              else link.removeAttribute('aria-current');
-              (link.closest('li') || link).classList.toggle('active', language === reading);
-            });
-          }
-          hook.doneEach(function () {
-            // docsify's history router leaves an anchor written as `#` in the path and reads one
-            // of its own from `?id=`; the page keeps both as the reader has them, and the route
-            // is translated without the fragment.
-            var path = ((vm.route && vm.route.path) || '/').replace(/#.*$/, '');
-            var missing = !!(vm.route && vm.route.response && vm.route.response.ok === false);
-            reading = /^\/pt-br(\/|$)/.test(path) ? 'pt-br' : 'en';
-            // A home page has no counterpart to carry the place in the page to.
-            var within = missing || translate(path, reading) === HOME[reading] ? '' : location.search + location.hash;
-            Object.keys(HOME).forEach(function (language) {
-              destination[language] = missing ? HOME[language] : translate(path, language) + within;
-            });
-            rewrite();
-            // docsify renders the navbar from its own request, which on some routes answers after
-            // this hook and puts the Markdown's links back; the navbar is written again whenever
-            // that happens, from the same destinations. Watching what the links say, rather than
-            // holding the navbar's markup, leaves `_navbar.md` in charge of it.
-            [].forEach.call(document.querySelectorAll('.app-nav, .app-nav-merged'), function (nav) {
-              if (watched.indexOf(nav) !== -1) return;
-              watched.push(nav);
-              new MutationObserver(rewrite).observe(nav, { childList: true, subtree: true });
-            });
-          });
-        },
-        // Per-page metadata for search engines and link previews: the title, description,
-        // canonical URL, language and hreflang pair of the page being shown, from its front
-        // matter and route. The generated copies of this shell carry the same values statically
-        // (scripts/site.ts), this hook keeps them right as the reader navigates.
-        function (hook, vm) {
-          var site = 'https://brazilian-utils.com.br';
-          var siteDescription = JSON.parse(
-            document.querySelector('script[type="application/ld+json"]').textContent
-          )['@graph'][0].description;
-          function set(selector, attribute, value) {
-            var element = document.querySelector(selector);
-            if (element) element.setAttribute(attribute, value);
-          }
-          function setAlternate(hreflang, href) {
-            var element = document.querySelector('link[rel="alternate"][hreflang="' + hreflang + '"]');
-            if (href === null) {
-              if (element) element.remove();
-              return;
-            }
-            if (!element) {
-              element = document.createElement('link');
-              element.rel = 'alternate';
-              element.hreflang = hreflang;
-              document.head.appendChild(element);
-            }
-            element.href = href;
-          }
-          function remove(selector) {
-            var element = document.querySelector(selector);
-            if (element) element.remove();
-          }
-          hook.doneEach(function () {
-            var path = (vm.route && vm.route.path) || '/';
-            var file = (vm.route && vm.route.file) || '';
-            var frontmatter = vm.frontmatter || {};
-            // A page docsify could not fetch (its 404 view): no canonical, alternates or
-            // Open Graph URL for a URL that does not exist, only noindex, like 404.html.
-            if (vm.route && vm.route.response && vm.route.response.ok === false) {
-              document.title = 'Not found · Brazilian Utils';
-              remove('link[rel="canonical"]');
-              remove('meta[property="og:url"]');
-              remove('link[type="text/markdown"]');
-              setAlternate('en', null);
-              setAlternate('pt-BR', null);
-              setAlternate('x-default', null);
-              if (!document.querySelector('meta[name="robots"]')) {
-                var robots = document.createElement('meta');
-                robots.name = 'robots';
-                robots.content = 'noindex';
-                document.head.appendChild(robots);
-              }
-              return;
-            }
-            var isPtBr = path.indexOf('/pt-br') === 0;
-            var title = frontmatter.title ? frontmatter.title + ' · Brazilian Utils' : 'Brazilian Utils';
-            var description = frontmatter.description || siteDescription;
-            // An aliased route (see `alias`: /pt-br/ shows pt-br/getting-started) canonicalizes to
-            // the page it shows; the English home is the README, which has no Portuguese twin.
-            var aliased = vm.config.alias && vm.config.alias[path];
-            var canonicalPath = aliased && aliased.indexOf('/') === 0 ? aliased.replace(/\.md$/, '') : path;
-            var enPath = isPtBr ? canonicalPath.replace(/^\/pt-br\//, '/') : canonicalPath;
-            var ptBrPath = isPtBr ? canonicalPath : canonicalPath === '/' ? null : '/pt-br' + canonicalPath;
-            document.title = title;
-            document.documentElement.lang = isPtBr ? 'pt-BR' : 'en';
-            set('meta[name="description"]', 'content', description);
-            set('link[rel="canonical"]', 'href', site + canonicalPath);
-            setAlternate('en', site + enPath);
-            setAlternate('pt-BR', ptBrPath === null ? null : site + ptBrPath);
-            setAlternate('x-default', site + enPath);
-            set('meta[property="og:title"]', 'content', title);
-            set('meta[property="og:description"]', 'content', description);
-            set('meta[property="og:url"]', 'content', site + canonicalPath);
-            set('meta[property="og:locale"]', 'content', isPtBr ? 'pt_BR' : 'en_US');
-            set('meta[property="og:locale:alternate"]', 'content', isPtBr ? 'en_US' : 'pt_BR');
-            set('link[type="text/markdown"]', 'href', /^https?:/.test(file) ? file : site + '/' + file.replace(/^\//, ''));
-          });
-        },
-      ],
-      copyCode: {
-        buttonText: {
-          '/pt-br/': 'Clique para copiar',
-          '/': 'Copy to clipboard'
-        },
-        errorText: {
-          '/pt-br/': 'Erro',
-          '/': 'Error'
-        },
-        successText: {
-          '/pt-br/': 'Copiado',
-          '/': 'Copied'
-        }
-      },
-    };
-  </script>
-
-  <!-- Docsify 5: the major version pin picks up non-breaking releases automatically -->
-  <script src="//cdn.jsdelivr.net/npm/docsify@5/dist/docsify.min.js"></script>
-  <!-- The search plugin indexes the raw Markdown through Docsify.get, without the front-matter
-       plugin, so it would index the front matter as a heading and lose the page's title; this
-       hands it every page the way it renders: the block gone, the title as the H1. -->
-  <script>
-    (function () {
-      var get = Docsify.get;
-      var FRONT_MATTER = /^---\n([\s\S]*?)\n---\n+/;
-      Docsify.get = function (url, hasBar, headers) {
-        var request = get(url, hasBar, headers);
-        if (!/\.md(\?|$)/.test(url)) return request;
-        return {
-          then: function (success, error) {
-            return request.then(function (text, opt) {
-              var match = FRONT_MATTER.exec(text || '');
-              if (match) {
-                var title = /^title: "(.*)"$/m.exec(match[1]);
-                text = (title ? '# ' + title[1].replace(/\\"/g, '"') + '\n\n' : '') + text.slice(match[0].length);
-              }
-              success(text, opt);
-            }, error);
-          },
-          abort: request.abort
-        };
-      };
-    })();
-  </script>
-
-  <!-- Plugins (emoji is built into docsify since 4.13, so its plugin is gone) -->
-  <script src="//cdn.jsdelivr.net/npm/docsify@5/dist/plugins/search.min.js"></script>
-  <script src="//cdn.jsdelivr.net/npm/docsify@5/dist/plugins/front-matter.min.js"></script>
-  <script src="//cdn.jsdelivr.net/npm/docsify-copy-code@3/dist/docsify-copy-code.min.js"></script>
-  <!-- Grammars docsify's bundled Prism lacks, for the TypeScript, TSX and Vue examples -->
-  <script src="//cdn.jsdelivr.net/npm/prismjs@1.30.0/components/prism-typescript.min.js"></script>
-  <script src="//cdn.jsdelivr.net/npm/prismjs@1.30.0/components/prism-jsx.min.js"></script>
-  <script src="//cdn.jsdelivr.net/npm/prismjs@1.30.0/components/prism-tsx.min.js"></script>
-  <script>Prism.languages.vue = Prism.languages.markup;</script>
-
-  <!-- Context7 chat widget: a floating assistant that answers from this library's documentation
-       indexed at context7.com/brazilian-utils/javascript. Loads asynchronously; the chat only
-       answers once the library is claimed on Context7 and brazilian-utils.com.br is in the
-       widget's allowed domains (library admin page, Chat tab). -->
-  <script
-    src="https://context7.com/widget.js"
-    data-library="/brazilian-utils/javascript"
-    data-color="#009739"
-    data-placeholder="Ask about Brazilian Utils..."
-    async
-  ></script>
-</body>
-
-</html>
diff --git a/docs/pt-br/_coverpage.md b/docs/pt-br/_coverpage.md
deleted file mode 100644
index c7291e5f3..000000000
--- a/docs/pt-br/_coverpage.md
+++ /dev/null
@@ -1,12 +0,0 @@
-<img src="https://raw.githubusercontent.com/brazilian-utils/brand/main/logos/logo-js.svg" alt="Brazilian Utils" width="360"/>
-
-> Utilitários para dados brasileiros: CPF, CNPJ, CEP, boleto, Pix, feriados e mais.
-
-- Zero dependências de runtime
-- Tree-shakeable, um import por utilitário
-- Node.js, Bun, Deno e navegadores
-- Tipada, documentada em inglês e português
-
-[Introdução](pt-br/getting-started.md)
-[Utilitários](pt-br/utilities.md)
-[GitHub](https://github.com/brazilian-utils/javascript)
diff --git a/docs/pt-br/_sidebar.md b/docs/pt-br/_sidebar.md
deleted file mode 100644
index 190a96614..000000000
--- a/docs/pt-br/_sidebar.md
+++ /dev/null
@@ -1,8 +0,0 @@
-* [Introdução](pt-br/getting-started.md)
-* [Utilitários](pt-br/utilities.md)
-* Guias
-  * [Campo de documento](pt-br/guides/document-field.md)
-  * [Endereço pelo CEP](pt-br/guides/address-form.md)
-  * [Estado e cidade](pt-br/guides/state-city.md)
-  * [Bibliotecas de schema](pt-br/guides/schema.md)
-* [Migração v1 para v2](pt-br/guides/migration-v1-to-v2.md)
diff --git a/docs/pt-br/getting-started.md b/docs/pt-br/getting-started.md
index d58f9899a..fd275ab96 100644
--- a/docs/pt-br/getting-started.md
+++ b/docs/pt-br/getting-started.md
@@ -46,7 +46,7 @@ import { isValidCpf } from '@brazilian-utils/brazilian-utils';
 isValidCpf('1232454233345'); // false
 ```
 
-A [referência de utilitários](pt-br/utilities.md) lista todas as funções, agrupadas por família, com opções e exemplos. Os [guias](pt-br/guides/document-field.md) mostram um campo de CPF em React, Angular, Vue e JavaScript puro.
+A [referência de utilitários](utilities.md) lista todas as funções, agrupadas por família, com opções e exemplos. Os [guias](guides/document-field.md) mostram um campo de CPF em React, Angular, Vue e JavaScript puro.
 
 ## Assistentes de IA
 
@@ -58,7 +58,7 @@ Valide um CNPJ com o Brazilian Utils. use library /brazilian-utils/javascript
 
 Para não repetir isso a cada prompt, coloque uma regra no arquivo de instruções do agente (`CLAUDE.md`, regras do Cursor ou equivalente): "Para utilitários de documentos brasileiros, use a biblioteca /brazilian-utils/javascript do Context7".
 
-Sem o Context7, aponte o assistente para o [llms.txt](https://brazilian-utils.com.br/llms.txt), que lista todos os utilitários com uma descrição de uma linha, ou para o [llms-full.txt](https://brazilian-utils.com.br/llms-full.txt), a documentação completa em inglês em um único arquivo Markdown.
+Sem o Context7, aponte o assistente para o [llms.txt](https://brazilian-utils.com.br/llms.txt), que lista todas as páginas de utilitários do site de documentação, ou para o [utilities.md](https://raw.githubusercontent.com/brazilian-utils/javascript/main/docs/pt-br/utilities.md), a referência completa em português em um único arquivo Markdown.
 
 ## Tamanho do bundle
 
diff --git a/docs/pt-br/guides/address-form.md b/docs/pt-br/guides/address-form.md
index 8c07048cd..8c5b7cbed 100644
--- a/docs/pt-br/guides/address-form.md
+++ b/docs/pt-br/guides/address-form.md
@@ -6,12 +6,12 @@ keywords: ["consulta de CEP", "endereço pelo CEP", "preencher endereço", "getA
 
 Digite um CEP e o resto do endereço se preenche. Escolha o framework: cada exemplo roda o código logo abaixo dele, que pode ser copiado do jeito que está.
 
-O `getAddressInfoByCep` pergunta aos provedores de CEP e devolve rua, bairro, cidade e estado, ou lança quando ninguém tem aquele CEP. Ele só é chamado quando o `isValidCep` diz que o CEP está completo, então não sai uma requisição a cada tecla, e o que volta continua editável: a consulta preenche o formulário, não toma conta dele. O [guia do campo de documento](pt-br/guides/document-field.md) tem a máscara que mantém o cursor no lugar.
+O `getAddressInfoByCep` pergunta aos provedores de CEP e devolve rua, bairro, cidade e estado, ou lança quando ninguém tem aquele CEP. Ele só é chamado quando o `isValidCep` diz que o CEP está completo, então não sai uma requisição a cada tecla, e o que volta continua editável: a consulta preenche o formulário, não toma conta dele. O [guia do campo de documento](document-field.md) tem a máscara que mantém o cursor no lugar.
 
 
 <div class="example" data-name="React" data-demo="/snippets/live/?dir=address-form/react&example=address-form.tsx">
 
-Um hook recebe o CEP e devolve o que se sabe sobre ele; o formulário desenha isso. O campo de CEP é o que o [guia do campo de documento](pt-br/guides/document-field.md) constrói:
+Um hook recebe o CEP e devolve o que se sabe sobre ele; o formulário desenha isso. O campo de CEP é o que o [guia do campo de documento](document-field.md) constrói:
 
 <div class="file" data-file="address-form.tsx">
 
@@ -29,7 +29,7 @@ Um hook recebe o CEP e devolve o que se sabe sobre ele; o formulário desenha is
 
 <div class="example" data-name="Angular" data-demo="/snippets/live/?dir=address-form/angular&example=address-form.ts">
 
-Um `resource` recebe o CEP e devolve o que se sabe sobre ele, recarregando quando ele muda. O campo de CEP é o que o [guia do campo de documento](pt-br/guides/document-field.md) constrói:
+Um `resource` recebe o CEP e devolve o que se sabe sobre ele, recarregando quando ele muda. O campo de CEP é o que o [guia do campo de documento](document-field.md) constrói:
 
 <div class="file" data-file="address-form.ts">
 
@@ -47,7 +47,7 @@ Um `resource` recebe o CEP e devolve o que se sabe sobre ele, recarregando quand
 
 <div class="example" data-name="Vue" data-demo="/snippets/live/?dir=address-form/vue&example=address-form.vue">
 
-Um composable recebe o CEP e devolve o que se sabe sobre ele; o formulário desenha isso. O campo de CEP é o que o [guia do campo de documento](pt-br/guides/document-field.md) constrói:
+Um composable recebe o CEP e devolve o que se sabe sobre ele; o formulário desenha isso. O campo de CEP é o que o [guia do campo de documento](document-field.md) constrói:
 
 <div class="file" data-file="address-form.vue">
 
@@ -75,4 +75,4 @@ Sem build: salve como um arquivo `.html` e abra. Ele importa o pacote de um CDN
 
 </div>
 
-A [referência de utilitários](pt-br/utilities.md) documenta o `getAddressInfoByCep`, os provedores e o que ele lança.
+A [referência de utilitários](../utilities.md) documenta o `getAddressInfoByCep`, os provedores e o que ele lança.
diff --git a/docs/pt-br/guides/document-field.md b/docs/pt-br/guides/document-field.md
index e20282c21..e30b47597 100644
--- a/docs/pt-br/guides/document-field.md
+++ b/docs/pt-br/guides/document-field.md
@@ -408,4 +408,4 @@ Sem build: salve como um arquivo `.html` e abra. Ele importa o pacote de um CDN,
 
 </div>
 
-A [referência de utilitários](pt-br/utilities.md) lista todas as funções.
+A [referência de utilitários](../utilities.md) lista todas as funções.
diff --git a/docs/pt-br/guides/migration-v1-to-v2.md b/docs/pt-br/guides/migration-v1-to-v2.md
index 15822f5b7..22f5769b3 100644
--- a/docs/pt-br/guides/migration-v1-to-v2.md
+++ b/docs/pt-br/guides/migration-v1-to-v2.md
@@ -23,12 +23,12 @@ Quatro helpers da v1 eram internos e não têm alias. Substitua-os antes de atua
 ## O que mudou
 
 - **Os nomes são camelCase.** Veja [Funções renomeadas](#funções-renomeadas).
-- **O tree-shaking funciona até a função**, e cada utilitário também é um subpath próprio (`@brazilian-utils/brazilian-utils/is-valid-cpf`), então os pesados podem ser carregados sob demanda. Veja [Tamanho do bundle](pt-br/getting-started.md#tamanho-do-bundle).
+- **O tree-shaking funciona até a função**, e cada utilitário também é um subpath próprio (`@brazilian-utils/brazilian-utils/is-valid-cpf`), então os pesados podem ser carregados sob demanda. Veja [Tamanho do bundle](../getting-started.md#tamanho-do-bundle).
 - **CNPJ alfanumérico.** `isValidCnpj` e `generateCnpj` aceitam o novo formato alfanumérico com `{ version: 2 }`. O numérico (versão 1) continua sendo o padrão. Veja [`generateCnpj` e a versão](#generatecnpj-e-a-versão).
 - **`getAddressInfoByCep`** aceita a opção `providers`, completa com zeros um CEP numérico e lança erros tipados: `GetAddressInfoByCepValidationError`, `GetAddressInfoByCepNotFoundError` e `GetAddressInfoByCepServiceError`. Chamadas sem opções funcionam como na v1.
 - **`getCities`** retorna a lista em ordem alfabética. Desde a 2.4.0 está descontinuada: `getMunicipalities('SP')` retorna os mesmos municípios com seus códigos IBGE, e `getMunicipalityByCode('3550308')` busca um deles offline.
 - **`isValidIe`** recebe um único objeto desde a 2.4.0, `isValidIe({ value, stateCode })`. A forma posicional está descontinuada.
-- **Muitos utilitários novos** desde a v2: feriados e dias úteis, Pix, chave de NF-e, leitura de boleto, formatação de telefone, contas bancárias e consulta de bancos, códigos de classificação (CBO, CNAE, NCM, CFOP), municípios offline, números por extenso e mais. Todos estão na [referência de utilitários](pt-br/utilities.md).
+- **Muitos utilitários novos** desde a v2: feriados e dias úteis, Pix, chave de NF-e, leitura de boleto, formatação de telefone, contas bancárias e consulta de bancos, códigos de classificação (CBO, CNAE, NCM, CFOP), municípios offline, números por extenso e mais. Todos estão na [referência de utilitários](../utilities.md).
 - **As ferramentas** mudaram para Vite+ e Vitest, com testes em navegador no CI. Isso só importa para quem contribui; veja o [CONTRIBUTING.md](https://github.com/brazilian-utils/javascript/blob/main/CONTRIBUTING.md).
 
 ## Funções renomeadas
diff --git a/docs/pt-br/guides/schema.md b/docs/pt-br/guides/schema.md
index 2d61efeef..7addce9eb 100644
--- a/docs/pt-br/guides/schema.md
+++ b/docs/pt-br/guides/schema.md
@@ -193,4 +193,4 @@ Sem biblioteca de schema nenhuma: o `toStandardSchema` dá ao validador a interf
 
 </div>
 
-A [referência de utilitários](pt-br/utilities.md#tostandardschema) documenta o `toStandardSchema` e os tipos da especificação.
+A [referência de utilitários](../utilities.md#tostandardschema) documenta o `toStandardSchema` e os tipos da especificação.
diff --git a/docs/pt-br/guides/state-city.md b/docs/pt-br/guides/state-city.md
index 44187d434..0c050eb5b 100644
--- a/docs/pt-br/guides/state-city.md
+++ b/docs/pt-br/guides/state-city.md
@@ -93,4 +93,4 @@ Sem build: salve como um arquivo `.html` e abra. Cada subpath é um módulo pró
 
 </div>
 
-A [introdução](pt-br/getting-started.md#tamanho-do-bundle) lista todos os utilitários que embutem uma tabela e valem um subpath próprio.
+A [introdução](../getting-started.md#tamanho-do-bundle) lista todos os utilitários que embutem uma tabela e valem um subpath próprio.
diff --git a/docs/pt-br/utilities.md b/docs/pt-br/utilities.md
index af5601f75..01a527f8f 100644
--- a/docs/pt-br/utilities.md
+++ b/docs/pt-br/utilities.md
@@ -1951,7 +1951,7 @@ Retorna os municípios brasileiros publicados pelo IBGE: todos os municípios, o
 - Cada município (`Municipality`) é `{ code, name, stateCode }`, onde `code` é o código IBGE de 7 dígitos. Ordenados por nome no locale "pt-BR".
 - Só um `stateCode` omitido (ou `undefined`) pede a lista completa: `null` e `''` retornam `[]`.
 - `stateCode` ignora maiúsculas/minúsculas e espaços nas pontas: `'sp'` retorna os municípios de São Paulo, como `'SP'` (até a 2.4.0 retornava `[]`).
-- Embute todos os 5571 municípios, os mesmos códigos da [Divisão Territorial Brasileira 2025](https://geoftp.ibge.gov.br/organizacao_do_territorio/estrutura_territorial/divisao_territorial/2025/DTB_2025.zip) do IBGE (data base 31/12/2025). Veja [Tamanho do bundle](pt-br/getting-started.md#tamanho-do-bundle) para carregá-lo sob demanda via `@brazilian-utils/brazilian-utils/get-municipalities`.
+- Embute todos os 5571 municípios, os mesmos códigos da [Divisão Territorial Brasileira 2025](https://geoftp.ibge.gov.br/organizacao_do_territorio/estrutura_territorial/divisao_territorial/2025/DTB_2025.zip) do IBGE (data base 31/12/2025). Veja [Tamanho do bundle](getting-started.md#tamanho-do-bundle) para carregá-lo sob demanda via `@brazilian-utils/brazilian-utils/get-municipalities`.
 
 ```javascript
 import { getMunicipalities } from '@brazilian-utils/brazilian-utils';
@@ -2012,7 +2012,7 @@ Busca o código IBGE de 7 dígitos de um município brasileiro pelo nome e pela
 - O nome ignora acentos, cedilha e maiúsculas/minúsculas. Sequências de espaços viram um só e os espaços em volta são removidos, mas um nome escrito sem um espaço que o nome do IBGE tem não é encontrado (`'saopaulo'`).
 - Recebe um único objeto, `{ municipalityName, stateCode }` (`GetCodeByMunicipalityNameParams`), com os dois campos obrigatórios. A sigla do estado ignora maiúsculas/minúsculas e espaços em volta, como em todo util que recebe UF. Ela é obrigatória, porque o mesmo nome pode ser de municípios de estados diferentes (`'Bom Jesus'` existe no PI, no RS e em outros estados).
 - Retorna o código como string, ou `null` quando a sigla não é de um estado ou nenhum município daquele estado tem esse nome.
-- Embute os 5571 municípios, a mesma tabela de `getMunicipalityByCode`. Veja [Tamanho do bundle](pt-br/getting-started.md#tamanho-do-bundle) para carregá-la sob demanda via `@brazilian-utils/brazilian-utils/get-code-by-municipality-name`.
+- Embute os 5571 municípios, a mesma tabela de `getMunicipalityByCode`. Veja [Tamanho do bundle](getting-started.md#tamanho-do-bundle) para carregá-la sob demanda via `@brazilian-utils/brazilian-utils/get-code-by-municipality-name`.
 
 ```javascript
 import { getCodeByMunicipalityName } from '@brazilian-utils/brazilian-utils';
@@ -2033,7 +2033,7 @@ Retorna os nomes das cidades brasileiras: todas as cidades, ou só as de um esta
 - Ordenadas no locale "pt-BR".
 - Qualquer `state` falsy pede a lista completa, enquanto `getMunicipalities` retorna `[]`.
 - `state` ignora maiúsculas/minúsculas e espaços nas pontas: `'sp'` retorna as cidades de São Paulo, como `'SP'` (até a 2.4.0 retornava `[]`).
-- Embute os 5571 nomes (~64,2 KB minificado, ~26,4 KB com gzip). Veja [Tamanho do bundle](pt-br/getting-started.md#tamanho-do-bundle) para carregá-la sob demanda via `@brazilian-utils/brazilian-utils/get-cities`.
+- Embute os 5571 nomes (~64,2 KB minificado, ~26,4 KB com gzip). Veja [Tamanho do bundle](getting-started.md#tamanho-do-bundle) para carregá-la sob demanda via `@brazilian-utils/brazilian-utils/get-cities`.
 
 ```javascript
 import { getCities } from '@brazilian-utils/brazilian-utils';
@@ -3742,7 +3742,7 @@ Busca um código CID-10 e retorna a sua descrição oficial em português. O res
 
 - Mesmas regras de entrada de `isValidCid10`. O `code` vem em maiúsculas e sem o ponto. Retorna `null` quando o código é desconhecido ou o valor não está em uma forma documentada.
 - Mesma tabela de `isValidCid10`: a V2008 do DATASUS mais os códigos `U07` da tabela do SIM (`getCid10('U07.1')` é `{ code: 'U071', description: 'Infecção pelo novo Coronavírus (COVID-19)' }`); `U09.9` e `U10.9` não são encontrados.
-- Este é o utilitário mais pesado do pacote: ele embute as 2046 categorias e 12191 subcategorias com suas descrições, cerca de 722 KB minificado (113 KB com gzip). Carregue-o sob demanda pelo seu subpath, como mostrado em [Tamanho do bundle](pt-br/getting-started.md#tamanho-do-bundle), e use `isValidCid10` quando a descrição não for necessária.
+- Este é o utilitário mais pesado do pacote: ele embute as 2046 categorias e 12191 subcategorias com suas descrições, cerca de 722 KB minificado (113 KB com gzip). Carregue-o sob demanda pelo seu subpath, como mostrado em [Tamanho do bundle](getting-started.md#tamanho-do-bundle), e use `isValidCid10` quando a descrição não for necessária.
 
 ```javascript
 import { getCid10 } from '@brazilian-utils/brazilian-utils';
diff --git a/docs/robots.txt b/docs/robots.txt
deleted file mode 100644
index 4f83e52d2..000000000
--- a/docs/robots.txt
+++ /dev/null
@@ -1,5 +0,0 @@
-User-agent: *
-Allow: /
-Disallow: /snippets/
-
-Sitemap: https://brazilian-utils.com.br/sitemap.xml
diff --git a/docs/snippets/styles.css b/docs/snippets/styles.css
index ae06ac9b9..a7593d601 100644
--- a/docs/snippets/styles.css
+++ b/docs/snippets/styles.css
@@ -1,9 +1,8 @@
 /*
- * The live demos of the guides: the site's own stylesheet, so a demo looks like the page around it
- * (docsify already styles the controls), plus the layout of a form and the state of its fields.
- * The examples themselves carry no classes: everything here is addressed by element.
+ * The live demos of the guides: the layout of a form and the state of its fields. The docs site
+ * that embeds a demo gives it its palette, fonts and the look of the controls. The examples
+ * themselves carry no classes: everything here is addressed by element.
  */
-@import url("../styles.css");
 
 :root {
   --invalid-color: #e5534b;
diff --git a/docs/styles.css b/docs/styles.css
deleted file mode 100644
index ece52ea71..000000000
--- a/docs/styles.css
+++ /dev/null
@@ -1,61 +0,0 @@
-/*
- * The stylesheet of the docs site, linked by every page shell and imported by the live demos of
- * examples.md, so both look the same. docsify 5's core theme with the dark add-on always on, the
- * look the site had before v5 (add `screen and (prefers-color-scheme: dark)` to the add-on's
- * import to follow the system instead), then the site's own styles.
- */
-@import url("https://cdn.jsdelivr.net/npm/docsify@5/dist/themes/core.min.css");
-@import url("https://cdn.jsdelivr.net/npm/docsify@5/dist/themes/addons/core-dark.min.css");
-
-:root {
-  /* The green of the official palette (github.com/brazilian-utils/brand) */
-  --theme-color: #009739;
-  /* The cover page shares the page background instead of the default gradient */
-  --cover-bg: var(--color-bg);
-  --cover-bg-overlay: none;
-}
-
-/* The two questions a guide asks: which document, in words, and then which framework, as tabs */
-.example-picker {
-  display: flex; flex-wrap: wrap; align-items: center; gap: 0.6em; margin: 1.5em 0 0;
-}
-.example-picker select { padding: 0.3em 0.5em; font: inherit; }
-.example-picker + .example-tabs { margin-top: 0.8em; }
-.example-tabs {
-  display: flex; flex-wrap: wrap; gap: 4px; margin: 1.5em 0 0;
-  border-bottom: 1px solid var(--border-color);
-}
-.example-tab-list { display: flex; flex-wrap: wrap; gap: 4px; }
-.example-tabs button {
-  padding: 0.55em 1.1em; border: 0; border-bottom: 2px solid transparent; border-radius: 0;
-  margin-bottom: -1px; background: none; color: inherit; font: inherit; font-weight: 600;
-  opacity: 0.7; cursor: pointer;
-}
-.example-tabs button:hover { opacity: 1; }
-.example-tabs button[aria-selected="true"] {
-  opacity: 1; color: var(--theme-color); border-bottom-color: var(--theme-color);
-}
-.example-tabs button:focus { box-shadow: none; outline: none; }
-.example-tabs button:focus-visible {
-  box-shadow: none; outline: 2px solid var(--theme-color); outline-offset: -2px;
-}
-.variant[hidden] { display: none; }
-.example[hidden] { display: none; }
-.example iframe {
-  display: block; width: 100%; height: 74px; margin: 1em 0;
-  border: 1px solid var(--border-color); border-radius: var(--border-radius);
-}
-
-/* The files of an example, shown like an editor's tabs */
-.file-tabs { display: flex; flex-wrap: wrap; gap: 2px; margin: 1.5em 0 0; }
-.file-tabs button {
-  padding: 0.45em 0.9em; border: 0; border-radius: var(--border-radius) var(--border-radius) 0 0;
-  background: none; color: inherit; cursor: pointer; opacity: 0.65;
-  font: 0.85em var(--font-family-mono);
-}
-.file-tabs button:hover { opacity: 1; }
-.file-tabs button[aria-selected="true"] { opacity: 1; background: var(--code-bg); }
-.file-tabs button:focus { box-shadow: none; outline: none; }
-.file-tabs button:focus-visible { outline: 2px solid var(--theme-color); outline-offset: -2px; }
-.file[hidden] { display: none; }
-.file-tabs + .file pre { margin-top: 0; border-top-left-radius: 0; }
diff --git a/package.json b/package.json
index a540e2204..bfe399318 100644
--- a/package.json
+++ b/package.json
@@ -38,7 +38,7 @@
 		"validator",
 		"zero-dependencies"
 	],
-	"homepage": "https://brazilian-utils.com.br",
+	"homepage": "https://brazilian-utils.com.br/libs/javascript/",
 	"bugs": {
 		"url": "https://github.com/brazilian-utils/javascript/issues"
 	},
@@ -128,11 +128,8 @@
 		"check:commits": "commitlint --from origin/main --to HEAD --verbose",
 		"check:lockfile": "lockfile-lint --path package-lock.json --type npm --allowed-hosts npm --validate-https --validate-integrity",
 		"build:data": "node ./scripts/data.ts",
-		"build:llms": "node ./scripts/llms.ts",
-		"build:site": "node ./scripts/site.ts",
 		"build:jsr": "node ./scripts/jsr.ts",
 		"build:examples": "node ./scripts/examples.ts",
-		"build:docs": "npm run build:examples && npm run build:llms && npm run build:site",
 		"prepublishOnly": "vp run build",
 		"check:dependencies": "node -e \"const d=require('./package.json').dependencies||{};if(Object.keys(d).length){console.error('runtime dependencies are not allowed:',Object.keys(d).join(', '));process.exit(1)}\""
 	},
diff --git a/scripts/front-matter.ts b/scripts/front-matter.ts
deleted file mode 100644
index 2c31fd33c..000000000
--- a/scripts/front-matter.ts
+++ /dev/null
@@ -1,35 +0,0 @@
-/**
- * The front matter block the docs pages open with (`title`, `description` and `keywords`, read by
- * the docsify shell), parsed once for every script that generates files from the pages, so they
- * all read a page the same way.
- */
-
-const FRONT_MATTER_PATTERN = /^---\r?\n([\s\S]*?)\r?\n---\r?\n+/;
-const QUOTED_FIELD_PATTERN = /^(\w+): "(.*)"$/gm;
-
-/** The parsed front matter of a page. */
-export type FrontMatter = {
-	/** The quoted string fields of the block, unescaped; `keywords` is not one of them. */
-	fields: Record<string, string>;
-	/** The page without its front matter block. */
-	body: string;
-};
-
-/**
- * Splits a page into its front matter fields and its body.
- * @param {string} markdown - The page, with or without a front matter block.
- * @returns {FrontMatter} The quoted fields (empty when there is no block) and the body.
- */
-export function parseFrontMatter(markdown: string): FrontMatter {
-	const match = FRONT_MATTER_PATTERN.exec(markdown);
-
-	if (!match) return { fields: {}, body: markdown };
-
-	const fields: Record<string, string> = {};
-
-	for (const [, name, value] of (match[1] ?? "").matchAll(QUOTED_FIELD_PATTERN)) {
-		fields[name ?? ""] = (value ?? "").replaceAll(String.raw`\"`, '"');
-	}
-
-	return { fields, body: markdown.slice(match[0].length) };
-}
diff --git a/scripts/llms.ts b/scripts/llms.ts
deleted file mode 100644
index 69c5aba39..000000000
--- a/scripts/llms.ts
+++ /dev/null
@@ -1,339 +0,0 @@
-import { readFileSync, writeFileSync } from "node:fs";
-import { join } from "node:path";
-
-import { parseFrontMatter } from "./front-matter.ts";
-import { removeUntilStable } from "./remove-until-stable.ts";
-
-const ROOT = join(import.meta.dirname, "..");
-const DOCS_DIRECTORY = join(ROOT, "docs");
-const SITE = "https://brazilian-utils.com.br";
-const REPOSITORY = "https://github.com/brazilian-utils/javascript";
-
-type UtilitySection = {
-	name: string;
-	slug: string;
-	description: string;
-};
-
-const SLUG_STRIP_PATTERN = /[\u2000-\u206F\u2E00-\u2E7F\\'!"#$%&()*+,./:;<=>?@[\]^`{|}~]/g;
-const VARIATION_SELECTOR_PATTERN = /\uFE0F/g;
-const EMOJI_PATTERN = /[\p{Emoji_Presentation}\p{Extended_Pictographic}]/gu;
-
-/**
- * Reproduces docsify's heading-to-anchor slug algorithm (see
- * `src/core/render/slugify.js` in the docsify source) so links into
- * `utilities.md`/`getting-started.md` resolve to the same anchors docsify
- * renders at runtime.
- * @param {string} heading - The Markdown heading text to slugify.
- * @returns {string} The docsify-compatible anchor slug for `heading`.
- */
-function slugify(heading: string): string {
-	return removeUntilStable(heading.trim().normalize("NFC"), /<[^>]+>/g)
-		.replaceAll(/\[([^\]]+)\]\([^)]+\)/g, "$1")
-		.replace(VARIATION_SELECTOR_PATTERN, "")
-		.replace(EMOJI_PATTERN, "")
-		.replaceAll(/[A-Z]+/g, (match) => match.toLowerCase())
-		.replace(SLUG_STRIP_PATTERN, "")
-		.replaceAll(/\s/g, "-")
-		.replace(/^(\d)/, "_$1");
-}
-
-const ABBREVIATION_PLACEHOLDER = String.fromCharCode(1);
-
-/**
- * Extracts the first sentence of a paragraph, treating `e.g.`, `i.e.` and `art.` (the way a
- * Brazilian law article is cited, as in "LGPD, art. 6º III") as abbreviations rather than
- * sentence boundaries.
- * @param {string} paragraph - The paragraph to extract the first sentence from.
- * @returns {string} The first sentence of `paragraph`.
- */
-function firstSentence(paragraph: string): string {
-	const withoutLinks = paragraph.replaceAll(/\[([^\]]+)\]\([^)]+\)/g, "$1");
-	const protectedText = withoutLinks.replaceAll(
-		/\b(e\.g|i\.e|art)\./gi,
-		(_match, abbr: string) => `${abbr}${ABBREVIATION_PLACEHOLDER}`,
-	);
-	const match = /[\s\S]*?[.!?](?=\s|$)/.exec(protectedText);
-	const sentence = match ? match[0] : protectedText;
-
-	return sentence.split(ABBREVIATION_PLACEHOLDER).join(".").trim();
-}
-
-const DEPRECATION_MARKER = "**Deprecated:**";
-
-/**
- * Extracts the `**Deprecated:** ...` sentence of a paragraph, without its markdown bold. The
- * description of an entry is its first sentence, and a deprecation notice never is the first
- * sentence, so without this it would be dropped from the generated index.
- * @param {string} paragraph - The paragraph to read the deprecation notice of.
- * @returns {string} The deprecation sentence, or an empty string when the paragraph carries none.
- */
-function deprecationSentence(paragraph: string): string {
-	const markerIndex = paragraph.indexOf(DEPRECATION_MARKER);
-
-	if (markerIndex === -1) return "";
-
-	return firstSentence(paragraph.slice(markerIndex).replaceAll("**", ""));
-}
-
-const UTILITY_HEADING_PATTERN = /^#{2,3} ([a-z][A-Za-z0-9]*)\n/;
-
-/**
- * Parses every function section of `utilities.md` into name/slug/description. A function section
- * starts with a `## <name>` or `### <name>` heading whose text is a bare identifier; the `##` family
- * headings that group most of them ("CPF", "Pix", ...) are skipped.
- * @param {string} utilitiesMarkdown - The full contents of `utilities.md`.
- * @returns {UtilitySection[]} One entry per function section, in document order.
- */
-function parseUtilities(utilitiesMarkdown: string): UtilitySection[] {
-	const sections = utilitiesMarkdown
-		.split(/^(?=#{2,3} )/m)
-		.filter((section) => UTILITY_HEADING_PATTERN.test(section));
-
-	return sections.map((section) => {
-		const newlineIndex = section.indexOf("\n");
-		const name = section.slice(0, newlineIndex).replace(/^#+ /, "").trim();
-		const body = section.slice(newlineIndex + 1);
-		const [firstParagraphRaw = ""] = body.split(/\n\s*\n/);
-		const firstParagraph = firstParagraphRaw.trim();
-		const description = firstSentence(firstParagraph);
-		const deprecation = description.includes(DEPRECATION_MARKER)
-			? ""
-			: deprecationSentence(firstParagraph);
-
-		return {
-			name,
-			slug: slugify(name),
-			description: deprecation === "" ? description : `${description} ${deprecation}`,
-		};
-	});
-}
-
-const FENCE_MARKER = "```";
-const SUB_HEADING_PATTERN = /^#{2,3} (.+)$/;
-const BACKTICKED_PATTERN = /`([^`]+)`/g;
-
-/**
- * Collects the `##` and `###` headings of a page, in document order and outside code fences, so a
- * generated table of contents cannot drift from the page it indexes.
- * @param {string} markdown - The Markdown page to read the headings of.
- * @returns {string[]} The heading texts, in document order.
- */
-function subHeadings(markdown: string): string[] {
-	let insideFence = false;
-
-	return markdown.split("\n").flatMap((line) => {
-		if (line.startsWith(FENCE_MARKER)) {
-			insideFence = !insideFence;
-			return [];
-		}
-
-		if (insideFence) return [];
-
-		const heading = SUB_HEADING_PATTERN.exec(line)?.[1];
-
-		return heading === undefined ? [] : [heading.trim()];
-	});
-}
-
-/**
- * Reads the util names listed in the "Bundle size" table of `getting-started.md`, so the summary
- * of the dataset-backed utils cannot drift from the table it summarizes.
- * @param {string} gettingStartedMarkdown - The full contents of `getting-started.md`.
- * @returns {string[]} The util names of the table, in document order.
- */
-function parseDatasetUtilities(gettingStartedMarkdown: string): string[] {
-	const section = /\n## Bundle size\n([\s\S]*?)(?=\n## |$)/.exec(gettingStartedMarkdown)?.[1] ?? "";
-
-	return section
-		.split("\n")
-		.filter((row) => row.startsWith("| `"))
-		.flatMap((row) =>
-			[...(row.split("|")[1] ?? "").matchAll(BACKTICKED_PATTERN)].map(([, name]) => name),
-		);
-}
-
-/**
- * Joins names into an English list, e.g. "`a`, `b` and `c`".
- * @param {string[]} names - The names to join, in order.
- * @returns {string} The names, backticked and comma-separated, with "and" before the last one.
- */
-function joinNames(names: string[]): string {
-	const quoted = names.map((name) => `\`${name}\``);
-	const last = quoted.at(-1) ?? "";
-
-	return quoted.length < 2 ? last : `${quoted.slice(0, -1).join(", ")} and ${last}`;
-}
-
-const PREFIX_GROUPS: { title: string; test: (name: string) => boolean }[] = [
-	{ title: "Validators (isValid*)", test: (name) => name.startsWith("isValid") },
-	{ title: "Formatters (format*)", test: (name) => name.startsWith("format") },
-	{ title: "Parsers (parse*)", test: (name) => name.startsWith("parse") },
-	{ title: "Generators (generate*)", test: (name) => name.startsWith("generate") },
-	{ title: "Getters (get*)", test: (name) => name.startsWith("get") },
-];
-
-function groupUtilities(
-	utilities: UtilitySection[],
-): { title: string; utilities: UtilitySection[] }[] {
-	const groups: { title: string; utilities: UtilitySection[] }[] = PREFIX_GROUPS.map((group) => ({
-		title: group.title,
-		utilities: [],
-	}));
-	const other: UtilitySection[] = [];
-
-	for (const utility of utilities) {
-		const groupIndex = PREFIX_GROUPS.findIndex((group) => group.test(utility.name));
-		const matchedGroup = groupIndex === -1 ? undefined : groups[groupIndex];
-
-		if (matchedGroup === undefined) {
-			other.push(utility);
-		} else {
-			matchedGroup.utilities.push(utility);
-		}
-	}
-
-	if (other.length > 0) {
-		groups.push({ title: "Other utilities", utilities: other });
-	}
-
-	return groups.filter((group) => group.utilities.length > 0);
-}
-
-function utilityLink(utility: UtilitySection): string {
-	return `- [${utility.name}](${SITE}/utilities.md#${utility.slug}): ${utility.description}`;
-}
-
-function buildLlmsTxt(utilities: UtilitySection[], datasetUtilities: string[]): string {
-	const groups = groupUtilities(utilities);
-	const groupSections = groups
-		.map((group) => `## ${group.title}\n\n${group.utilities.map(utilityLink).join("\n")}`)
-		.join("\n\n");
-
-	return `# Brazilian Utils
-
-> Brazilian Utils is a zero-dependency JavaScript/TypeScript library of small, focused utilities for the day-to-day problems of building software for Brazil: validating, formatting, parsing and generating CPF, CNPJ, CEP, Pix, boleto, NF-e, phone numbers, license plates and more.
-
-The package has **zero runtime dependencies**, is fully tree-shakeable and runs on Node.js \`^20.19.0 || >=22.12.0\`, Bun, Deno and modern browsers (including a UMD \`<script>\` build).
-
-Install with \`npm install --save @brazilian-utils/brazilian-utils\` (also available via yarn, pnpm and bun). Import a util from the package root:
-
-\`\`\`javascript
-import { isValidCpf } from '@brazilian-utils/brazilian-utils';
-\`\`\`
-
-Every util is also available as its own subpath for lazy-loading/code-splitting, \`@brazilian-utils/brazilian-utils/<kebab-name>\` (kebab-case of the function name, e.g. \`isValidCpf\` maps to \`is-valid-cpf\`) - most useful for the utils that embed an official dataset (${joinNames(datasetUtilities)}):
-
-\`\`\`javascript
-const { getCities } = await import('@brazilian-utils/brazilian-utils/get-cities');
-\`\`\`
-
-## Docs
-
-- [Getting started](${SITE}/getting-started.md): installation, runtime support, usage and bundle size/subpath imports
-- [Utilities](${SITE}/utilities.md): full English reference, one section per function, with signatures and examples
-- [Bundle size](${SITE}/getting-started.md#bundle-size): tree-shaking behavior and the dataset-backed utils that are worth a subpath import
-- [Examples](${SITE}/examples.md): a CPF field that formats as you type and validates, in React, Vue, Angular and plain JavaScript
-
-${groupSections}
-
-## Optional
-
-- [Getting started (pt-BR)](${SITE}/pt-br/getting-started.md): Portuguese translation of the getting started guide
-- [Utilities (pt-BR)](${SITE}/pt-br/utilities.md): Portuguese translation of the utilities reference
-- [README on GitHub](${REPOSITORY}#readme): project overview and contributor list
-- [CHANGELOG](${REPOSITORY}/blob/main/CHANGELOG.md): release history
-- [npm package](https://www.npmjs.com/package/@brazilian-utils/brazilian-utils): published versions and download stats
-`;
-}
-
-/**
- * Strips docsify-only markdown syntax (`?id=` anchors, HTML comments) so the content reads as
- * plain Markdown.
- * @param {string} markdown - The docsify-flavored Markdown to strip.
- * @returns {string} `markdown` with docsify-only syntax removed.
- */
-function stripDocsifySyntax(markdown: string): string {
-	return removeUntilStable(markdown, /<!--[\s\S]*?-->/g)
-		.replaceAll(
-			/\]\(([^)]+)\?id=([^)]+)\)/g,
-			(_match, path: string, id: string) => `](${path}#${id})`,
-		)
-		.trimEnd();
-}
-
-/**
- * Demotes every markdown heading in `markdown` by one level (adds one `#`), so it nests under a
- * higher-level heading.
- * @param {string} markdown - The Markdown whose headings should be demoted.
- * @returns {string} `markdown` with every heading demoted by one level.
- */
-function demoteHeadings(markdown: string): string {
-	return markdown.replaceAll(/^(#{1,5}\s)/gm, "#$1");
-}
-
-function buildLlmsFullTxt(
-	gettingStartedMarkdown: string,
-	utilitiesMarkdown: string,
-	utilities: UtilitySection[],
-): string {
-	const toc = [
-		"- [Getting Started](#getting-started)",
-		...subHeadings(gettingStartedMarkdown).map(
-			(heading) => `  - [${heading}](#${slugify(heading)})`,
-		),
-		"- [Utilities](#utilities)",
-		...utilities.map((utility) => `  - [${utility.name}](#${utility.slug})`),
-	].join("\n");
-
-	const gettingStarted = demoteHeadings(stripDocsifySyntax(gettingStartedMarkdown));
-	const utilitiesReference = demoteHeadings(stripDocsifySyntax(utilitiesMarkdown));
-
-	return `# Brazilian Utils
-
-> Brazilian Utils is a zero-dependency JavaScript/TypeScript library of small, focused utilities for the day-to-day problems of building software for Brazil. This file concatenates the full English documentation (getting started + utilities reference) in one Markdown document for LLM context loading.
-
-## Table of contents
-
-${toc}
-
-${gettingStarted}
-
-${utilitiesReference}
-`;
-}
-
-/**
- * Replaces the front matter block of a page (its `title` and `description`, which the docsify
- * shell reads) with a level-one heading of its title, the heading the page shows on the site, so
- * the generated files keep reading as they did when the heading was in the Markdown.
- * @param {string} markdown - A docs page, with or without a front matter block.
- * @returns {string} The page body, headed by its front matter title when it has one.
- */
-function frontMatterToHeading(markdown: string): string {
-	const { fields, body } = parseFrontMatter(markdown);
-	const title = fields["title"];
-
-	return title === undefined ? body : `# ${title}\n\n${body}`;
-}
-
-function main(): void {
-	const gettingStartedMarkdown = frontMatterToHeading(
-		readFileSync(join(DOCS_DIRECTORY, "getting-started.md"), "utf8"),
-	);
-	const utilitiesMarkdown = frontMatterToHeading(
-		readFileSync(join(DOCS_DIRECTORY, "utilities.md"), "utf8"),
-	);
-	const utilities = parseUtilities(utilitiesMarkdown);
-
-	writeFileSync(
-		join(DOCS_DIRECTORY, "llms.txt"),
-		buildLlmsTxt(utilities, parseDatasetUtilities(gettingStartedMarkdown)),
-	);
-	writeFileSync(
-		join(DOCS_DIRECTORY, "llms-full.txt"),
-		buildLlmsFullTxt(gettingStartedMarkdown, utilitiesMarkdown, utilities),
-	);
-}
-
-main();
diff --git a/scripts/site.ts b/scripts/site.ts
deleted file mode 100644
index b3396ca48..000000000
--- a/scripts/site.ts
+++ /dev/null
@@ -1,281 +0,0 @@
-import { mkdirSync, readFileSync, writeFileSync } from "node:fs";
-import { dirname, join } from "node:path";
-
-import { parseFrontMatter } from "./front-matter.ts";
-
-/**
- * Keeps brazilian-utils.com.br crawlable as a set of real URLs. docsify runs in history mode there
- * (`routerMode: 'history'` in `docs/index.html`), so `/getting-started` has to answer with the
- * docsify shell: GitHub Pages serves `getting-started.html` for it, and this script writes that
- * file, and one per page of each `_sidebar.md`, from `docs/index.html`, with the page's own
- * title, description, canonical URL, language and hreflang links in place of the home page's, so
- * a crawler that does not run JavaScript still reads the right metadata for each URL (the hook
- * in the shell keeps them right as the reader navigates). It also writes `404.html` and the
- * `sitemap.xml` that lists every page with its English/Portuguese counterpart. The Check
- * workflow fails when any of them is stale.
- */
-
-const ROOT = join(import.meta.dirname, "..");
-const DOCS_DIRECTORY = join(ROOT, "docs");
-const SITE = "https://brazilian-utils.com.br";
-const SITE_NAME = "Brazilian Utils";
-
-/** The Markdown docsify shows at `/`: the README, fetched from GitHub (the `alias` in the shell). */
-const HOME_MARKDOWN = "https://raw.githubusercontent.com/brazilian-utils/javascript/main/README.md";
-
-/** The folder of each language, keyed by its hreflang, `""` being the English root. */
-const LANGUAGES: { hreflang: string; folder: string; locale: string }[] = [
-	{ hreflang: "en", folder: "", locale: "en_US" },
-	{ hreflang: "pt-BR", folder: "pt-br", locale: "pt_BR" },
-];
-
-/**
- * The page `/pt-br/` shows (the `alias` in `docs/index.html`): the Portuguese site has no README,
- * so its home is the getting-started page, and `/pt-br/` canonicalizes there.
- */
-const PT_BR_HOME_PAGE = "/pt-br/getting-started";
-
-const SIDEBAR_LINK_PATTERN = /\]\(([^)]+)\.md\)/g;
-const HREFLANG_LINK_PATTERN = /^ *<link rel="alternate" hreflang="[^"]*" href="[^"]*" \/>\n/gm;
-const CANONICAL_LINK_PATTERN = /^( *)<link rel="canonical" href="[^"]*" \/>\n/m;
-
-type Page = {
-	/** The site path, `/getting-started`. */
-	path: string;
-	/** The path a crawler should index for it, the path itself except for the aliased `/pt-br/`. */
-	canonicalPath: string;
-	/** The language folder, `""` for the root. */
-	folder: string;
-	title: string;
-	description: string;
-	/** The Markdown docsify loads for the path: a file relative to `docs/`, or a full URL. */
-	markdown: string;
-};
-
-type Alternate = { hreflang: string; href: string };
-
-/**
- * Reads the pages a `_sidebar.md` links to, as site paths (`/getting-started`).
- * @param {string} folder - The language folder the sidebar sits in, `""` for the root.
- * @returns {string[]} The page paths, in sidebar order.
- */
-function sidebarPaths(folder: string): string[] {
-	const sidebar = readFileSync(join(DOCS_DIRECTORY, folder, "_sidebar.md"), "utf8");
-
-	return [...sidebar.matchAll(SIDEBAR_LINK_PATTERN)].map(([, target]) => `/${target ?? ""}`);
-}
-
-/**
- * Reads the `title` and `description` of a page's front matter.
- * @param {string} markdown - The Markdown file, relative to `docs/`.
- * @returns {{ title: string; description: string }} The two fields, empty when absent.
- */
-function frontMatter(markdown: string): { title: string; description: string } {
-	const { fields } = parseFrontMatter(readFileSync(join(DOCS_DIRECTORY, markdown), "utf8"));
-
-	return { title: fields["title"] ?? "", description: fields["description"] ?? "" };
-}
-
-/**
- * The pages of the site: each sidebar entry of each language, plus `/pt-br/`.
- * @returns {Page[]} The pages, English first.
- */
-function pages(): Page[] {
-	const sidebarPages = LANGUAGES.flatMap(({ folder }) =>
-		sidebarPaths(folder).map((path): Page => {
-			const markdown = `${path.slice(1)}.md`;
-			const { title, description } = frontMatter(markdown);
-			return { path, canonicalPath: path, folder, markdown, title, description };
-		}),
-	);
-	const ptBrHome = sidebarPages.find((page) => page.path === PT_BR_HOME_PAGE);
-
-	if (ptBrHome === undefined) throw new Error(`${PT_BR_HOME_PAGE} is not in pt-br/_sidebar.md`);
-
-	return [...sidebarPages, { ...ptBrHome, path: "/pt-br/" }];
-}
-
-/**
- * The file GitHub Pages serves for a path: `index.html` for a folder, `<page>.html` otherwise.
- * @param {string} path - A site path.
- * @returns {string} The file path, relative to `docs/`.
- */
-function shellFile(path: string): string {
-	return path.endsWith("/") ? `${path.slice(1)}index.html` : `${path.slice(1)}.html`;
-}
-
-/**
- * The same page in another language: `/pt-br/utilities` for `/utilities` and back. The English
- * home (`/`, the README) has no Portuguese twin.
- * @param {string} canonicalPath - A canonical site path.
- * @param {string} folder - The target language folder, `""` for the root.
- * @returns {string | null} The canonical path of the page in that language, `null` when it has none.
- */
-function translate(canonicalPath: string, folder: string): string | null {
-	if (canonicalPath === "/") return folder === "" ? "/" : null;
-
-	const bare = canonicalPath.replace(/^\/pt-br\//, "/");
-
-	return folder === "" ? bare : `/${folder}${bare}`;
-}
-
-/**
- * The `hreflang` links of a page: one per language that has it, plus `x-default` on the English one.
- * @param {string} canonicalPath - A canonical site path.
- * @returns {Alternate[]} The links, in `LANGUAGES` order.
- */
-function alternates(canonicalPath: string): Alternate[] {
-	const links = LANGUAGES.flatMap(({ hreflang, folder }): Alternate[] => {
-		const path = translate(canonicalPath, folder);
-		return path === null ? [] : [{ hreflang, href: `${SITE}${path}` }];
-	});
-
-	return [
-		...links,
-		{ hreflang: "x-default", href: `${SITE}${translate(canonicalPath, "") ?? "/"}` },
-	];
-}
-
-/**
- * Replaces the home page's value of a tag in the shell with the page's own, failing when the tag
- * is not in `index.html` any more, so an edit there cannot silently leave the copies stale.
- * @param {string} shell - The shell being rewritten.
- * @param {RegExp} tag - The tag to rewrite, its value as the first capture group.
- * @param {string} value - The page's value.
- * @returns {string} The rewritten shell.
- */
-function replaceTag(shell: string, tag: RegExp, value: string): string {
-	const match = tag.exec(shell);
-
-	if (match?.[1] === undefined) throw new Error(`docs/index.html has no ${tag.source}`);
-
-	const escaped = value.replaceAll("&", "&amp;").replaceAll('"', "&quot;").replaceAll("<", "&lt;");
-	const rewritten = match[0].replace(match[1], () => escaped);
-
-	return shell.replace(match[0], () => rewritten);
-}
-
-/**
- * Replaces the home page's `hreflang` links with the page's own, right after its canonical link.
- * @param {string} shell - The shell being rewritten.
- * @param {Alternate[]} links - The page's links, none to drop them all.
- * @returns {string} The rewritten shell.
- */
-function replaceAlternates(shell: string, links: Alternate[]): string {
-	const stripped = shell.replace(HREFLANG_LINK_PATTERN, "");
-	const canonical = CANONICAL_LINK_PATTERN.exec(stripped);
-
-	if (canonical === null) throw new Error("docs/index.html has no canonical link");
-
-	const indent = canonical[1] ?? "";
-	const lines = links.map(
-		({ hreflang, href }) =>
-			`${indent}<link rel="alternate" hreflang="${hreflang}" href="${href}" />\n`,
-	);
-
-	return stripped.replace(canonical[0], () => canonical[0] + lines.join(""));
-}
-
-/**
- * The shell with the page's metadata in place of the home page's.
- * @param {string} shell - `docs/index.html`.
- * @param {Page} page - The page the copy serves.
- * @returns {string} The copy.
- */
-function pageShell(shell: string, page: Page): string {
-	const language = LANGUAGES.find(({ folder }) => folder === page.folder);
-	const canonical = `${SITE}${page.canonicalPath}`;
-	const title = `${page.title} · ${SITE_NAME}`;
-	const markdown = /^https?:/.test(page.markdown) ? page.markdown : `${SITE}/${page.markdown}`;
-	let copy = shell;
-
-	copy = replaceTag(copy, /<html lang="([^"]*)">/, language?.hreflang ?? "en");
-	copy = replaceTag(copy, /<title>([^<]*)<\/title>/, title);
-	copy = replaceTag(copy, /<meta name="description" content="([^"]*)" \/>/, page.description);
-	copy = replaceTag(copy, /<link rel="canonical" href="([^"]*)" \/>/, canonical);
-	copy = replaceAlternates(copy, alternates(page.canonicalPath));
-	copy = replaceTag(copy, /<link rel="alternate" type="text\/markdown" href="([^"]*)"/, markdown);
-	copy = replaceTag(copy, /<meta property="og:title" content="([^"]*)" \/>/, title);
-	copy = replaceTag(
-		copy,
-		/<meta property="og:description" content="([^"]*)" \/>/,
-		page.description,
-	);
-	copy = replaceTag(copy, /<meta property="og:url" content="([^"]*)" \/>/, canonical);
-	copy = replaceTag(
-		copy,
-		/<meta property="og:locale" content="([^"]*)" \/>/,
-		language?.locale ?? "en_US",
-	);
-	copy = replaceTag(
-		copy,
-		/<meta property="og:locale:alternate" content="([^"]*)" \/>/,
-		language?.hreflang === "pt-BR" ? "en_US" : "pt_BR",
-	);
-
-	return copy;
-}
-
-/**
- * The shell for unknown URLs: titled as not found, kept out of the index and without the home
- * page's canonical, hreflang, `og:url` and Markdown links, so an unknown URL sends no signal but
- * `noindex` (GitHub Pages serves it with a 404 status, a crawler may still read the tags).
- * @param {string} shell - `docs/index.html`.
- * @returns {string} The copy.
- */
-function notFoundShell(shell: string): string {
-	const titled = replaceTag(shell, /<title>([^<]*)<\/title>/, `Not found · ${SITE_NAME}`);
-	const bare = replaceAlternates(titled, [])
-		.replace(CANONICAL_LINK_PATTERN, "")
-		.replace(/^ *<meta property="og:url" content="[^"]*" \/>\n/m, "")
-		.replace(/^ *<link rel="alternate" type="text\/markdown" [^\n]*\n/m, "");
-
-	return bare.replace("<title>", () => '<meta name="robots" content="noindex" />\n  <title>');
-}
-
-function buildSitemap(sitePages: Page[]): string {
-	const entries = sitePages.map((page) => {
-		const links = alternates(page.canonicalPath).map(
-			({ hreflang, href }) =>
-				`    <xhtml:link rel="alternate" hreflang="${hreflang}" href="${href}" />`,
-		);
-
-		return ["  <url>", `    <loc>${SITE}${page.canonicalPath}</loc>`, ...links, "  </url>"].join(
-			"\n",
-		);
-	});
-
-	return `<?xml version="1.0" encoding="UTF-8"?>
-<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" xmlns:xhtml="http://www.w3.org/1999/xhtml">
-${entries.join("\n")}
-</urlset>
-`;
-}
-
-function main(): void {
-	const shell = readFileSync(join(DOCS_DIRECTORY, "index.html"), "utf8");
-	const sitePages = pages();
-
-	for (const page of sitePages) {
-		const file = join(DOCS_DIRECTORY, shellFile(page.path));
-		mkdirSync(dirname(file), { recursive: true });
-		writeFileSync(file, pageShell(shell, page));
-	}
-
-	writeFileSync(join(DOCS_DIRECTORY, "404.html"), notFoundShell(shell));
-
-	// The home page is `index.html` itself; `/pt-br/` canonicalizes to its entry page, so the sitemap
-	// lists the canonical paths once.
-	const home: Page = {
-		path: "/",
-		canonicalPath: "/",
-		folder: "",
-		title: SITE_NAME,
-		description: "",
-		markdown: HOME_MARKDOWN,
-	};
-	const canonicalPages = sitePages.filter((page) => page.path === page.canonicalPath);
-	writeFileSync(join(DOCS_DIRECTORY, "sitemap.xml"), buildSitemap([home, ...canonicalPages]));
-}
-
-main();
diff --git a/tsconfig.json b/tsconfig.json
index 01499eb0a..a58c2fcd4 100644
--- a/tsconfig.json
+++ b/tsconfig.json
@@ -18,10 +18,9 @@
 		"noPropertyAccessFromIndexSignature": true,
 		"noImplicitOverride": true
 	},
-	// The documentation site is not part of the library: its examples are written for React,
-	// Angular and Vue. `npm run build:docs` and the type-check of each example live in the docs
-	// workflow. `base` is the second checkout the Tree-shaking job of the build workflow writes
-	// there, a whole copy of the repository at the base revision of the pull request: the build
-	// running here compiles the head, never it.
+	// The documentation is not part of the library: the examples of its guides are written for
+	// React, Angular and Vue. `base` is the second checkout the Tree-shaking job of the build
+	// workflow writes there, a whole copy of the repository at the base revision of the pull
+	// request: the build running here compiles the head, never it.
 	"exclude": ["base", "docs", "dist", "coverage", "reports", ".stryker-tmp"]
 }
diff --git a/vercel.json b/vercel.json
deleted file mode 100644
index bbd51911a..000000000
--- a/vercel.json
+++ /dev/null
@@ -1,24 +0,0 @@
-{
-	"$schema": "https://openapi.vercel.sh/vercel.json",
-	"framework": null,
-	"installCommand": "npm ci",
-	"buildCommand": "npm run build:docs",
-	"outputDirectory": "docs",
-	"cleanUrls": true,
-	"ignoreCommand": "test -n \"$VERCEL_GIT_PREVIOUS_SHA\" && git diff --quiet \"$VERCEL_GIT_PREVIOUS_SHA\" HEAD -- docs scripts package.json vercel.json 2>/dev/null || exit 1",
-	"git": {
-		"deploymentEnabled": {
-			"main": false
-		}
-	},
-	"headers": [
-		{
-			"source": "/(.*)",
-			"headers": [
-				{ "key": "X-Robots-Tag", "value": "noindex, nofollow" },
-				{ "key": "X-Content-Type-Options", "value": "nosniff" },
-				{ "key": "Referrer-Policy", "value": "strict-origin-when-cross-origin" }
-			]
-		}
-	]
-}