diff --git a/AGENTS.md b/AGENTS.md
index 0fd7f6dc..5a81a288 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -15,12 +15,12 @@ person reads the page. Do not put "as an AI, …" prose back into `docs/`.
 
 | Path | Purpose |
 | --- | --- |
-| `docs/` | The pages. Sidebar and nav live in `docs/.vitepress/config.mjs`. Two pages are not chapters: `index.md` (`layout: home`, the front door) and `evaluate.md` (`layout: landing`, the page for the person who approves abap2UI5 - drawn like the front door, with no sidebar, outline or crumb trail, and its own address so a link to it does not say "manual"; its frontmatter says why) |
+| `docs/` | The pages. Sidebar and nav live in `docs/.vitepress/config.mjs`. One page is not a chapter: `index.md` (`layout: home`, the front door). **The manual is for developers.** The case for the person who approves abap2UI5 - what it can build, how it compares, what it costs, who runs it - is a site of its own, [abap2UI5/test-docs](https://github.com/abap2UI5/test-docs) at https://abap2ui5.github.io/test-docs/; link it, never argue it here a second time |
 | `docs/public/` | Static assets — **and** the generated `llms.txt`, `llms-full.txt` and per-page `.md`, which are gitignored |
 | `scripts/check-examples.mjs` | Extracts every fenced ABAP block that builds a view, compiles it against the real framework and lints the view it produces |
 | `scripts/link-samples.mjs` | Generates the *Working Samples* block on a page from its `samples:` frontmatter plus the catalogue of the repository each class belongs to — the prefix decides: `z2ui5_cl_smp_app_*` is `abap2UI5/samples` (read from its `SAMPLES.md` in a checkout), `z2ui5_cl_smpc_*` samples-controls and `z2ui5_cl_smps_*` samples-stack (read from their `catalogue.json`, a checkout or the published copy). Checks the link in both directions for the samples repository (the `" @docs` line), the class's existence for the other two, and resolves the source links a page writes by hand against whichever checkout is here |
 | `scripts/generate-llms.mjs` | Builds `llms.txt` / `llms-full.txt` / per-page markdown from the sidebar. Runs inside `docs:build`, so the deploy publishes them |
-| `scripts/lib/facts.mjs` | The counted figures the front door and the Evaluate page print under the hero and in `<p class="a2ui5-facts"></p>` - unit tests, specs, browser suites, gates, GitHub stars. Read at build time from the framework README's `facts:start` block (`A2UI5_HOME` via `git show`, else raw GitHub) and the GitHub API; this repository types no number of its own, and a read that fails costs the line, never the build, and says so in the build log |
+| `scripts/lib/facts.mjs` | The counted figures the front door prints under the hero and in `<p class="a2ui5-facts"></p>` - unit tests, specs, browser suites, gates, GitHub stars. Read at build time from the framework README's `facts:start` block (`A2UI5_HOME` via `git show`, else raw GitHub) and the GitHub API; this repository types no number of its own, and a read that fails costs the line, never the build, and says so in the build log |
 | `scripts/generate-api-reference.mjs` | Generates the client API reference — the block in `docs/resources/api.md` and `docs/public/api/client-api.json` — from `z2ui5_if_client` on the framework branch this site tracks (`main`); `--check` is the freshness gate |
 | `scripts/lib/client-interface.mjs` | Where `z2ui5_if_client` is fetched from (the ref comes from `lib/release.mjs`, shared with `check-api-names.mjs`; `A2UI5_HOME` reads the same ref out of a local clone of the framework instead, with `git show`, never its working tree) and the full parser `generate-api-reference.mjs` renders from; pinned by `test/client-interface.test.mjs` |
 | `scripts/check-version.mjs` | The release number in the bar's menu, the deprecations page and the changelog, against the newest release tag of the framework |
@@ -49,7 +49,6 @@ person reads the page. Do not put "as an AI, …" prose back into `docs/`.
 | `scripts/check-images.mjs` | Every image under `docs/public`: a screenshot is WebP, a deliverable is one of the PNGs the logo page hands out, none is over its budget, and the build can measure each of them - `scripts/lib/images.mjs` is the one reader both this gate and `build-site.mjs` use, so a format the build cannot size fails here rather than shifting the page there |
 | `scripts/lib/html.mjs` | `stripComments( )`: every finished page leaves the build without the HTML comments its sources are written with - 418 kB across the site, a tenth of every page's compressed weight, read by nobody - outside `<script>`, because a script's text is what its hash in the policy is taken from |
 | `scripts/lib/prose.mjs` | What on a page is PROSE - not fenced or inline code, not a link target, a tag, a comment, a URL, a generated block or a frontmatter setting - and the house spelling of it, which is American: the British forms as patterns, each with the American form it becomes. `test/spelling.test.mjs` is the gate; `scripts/fix-spelling.mjs` (`npm run fix:spelling`) rewrites exactly the words the gate names |
-| `docs/.vitepress/theme/cost-calculator.js` | The cost calculator (`resources/cost_calculator`): sliders whose readouts follow them, a choice of support, and a Calculate button that greys the inputs and hands out the sheet - which echoes the readouts, in the currency chosen - until the next round. Two things ride on the reveal rather than on the input rows: the links out (the issue tracker, Slack) sit on the sheet's Support line, and under the total is a short plain list of what the zeros get you. `theme/cost-model.js` is the half with no DOM in it - the reading of a position, and the total, which is zero for any input; `test/cost-calculator.test.mjs` pins the arithmetic and holds the page's written readouts to what the script would write |
 | `scripts/lib/csp.mjs` | The Content-Security-Policy every page is published under, as a `<meta>` because GitHub Pages sets no headers of ours: this origin, the playground beside it for the Run panel, and the two inline scripts by hash - the theme line and the borrowed menu script, hashed from the very string the build writes. `build-site.mjs` reads every finished page back for an inline script that is neither, and refuses to publish it |
 | `scripts/check-cross-site.mjs` | Every link out of this deployment and into a neighbouring one on the same origin carries a `target`, or VitePress's router swallows it and shows this site's 404 at the other site's URL. Reads the BUILT html, so it runs after `docs:build`; the rule and the reasoning are in `scripts/lib/cross-site.mjs` |
 
@@ -617,7 +616,7 @@ hand-written HTML file behind at its old address — a canonical link, a
 browser does not follow it. `docs/public/configuration/troubleshooting.html`
 is the worked example.
 
-There are thirty-two of them. Eight are `/technical/*`: that whole section became
+There are thirty-six of them. Eight are `/technical/*`: that whole section became
 the Know-How series under `/advanced/insights/` in one commit, and eight
 addresses that had been public for years stopped existing with it — one of
 them, `/technical/concept`, is linked from the framework's README, which is
@@ -634,10 +633,13 @@ The last thirteen are the Tutorial's, moved on 2026-10-08 when its single
 `step-1` to `step-12` each point at the same page one level up, under
 `/tutorials/`. Those carry a one-line script on top of the `meta refresh`
 that keeps the `#fragment`, because links into a step's sections exist.
-The thirty-second is `get_started/evaluate`, the Evaluate page's address for
-its first day (2026-10-23) before it got the landing layout and moved to
-`/evaluate`; the framework's README and two of its docs pages link sections of
-it, so the stub keeps the fragment the same way.
+The last five point out of this site, at the page for decision makers
+(https://abap2ui5.github.io/test-docs/), which took over what the manual
+carried for them on 2026-10-24: `evaluate` and `get_started/evaluate` (its
+address for its first day) keep the `#fragment`, because the framework's README
+links sections of it and the new page keeps every section id;
+`resources/cost_calculator`, `resources/who_uses` and `resources/references`
+point at the section that carries each now.
 
 Two things make this safe rather than a second set of pages to maintain:
 
diff --git a/docs/.vitepress/config.mjs b/docs/.vitepress/config.mjs
index c5053c99..8160ae6c 100644
--- a/docs/.vitepress/config.mjs
+++ b/docs/.vitepress/config.mjs
@@ -230,7 +230,6 @@ export default defineConfig({
         collapsed: true,
         items: [
           { text: "In a Nutshell", link: "/get_started/about" }, // sidebar
-          { text: "Evaluate abap2UI5", link: "/evaluate" },
           { text: "Quickstart", link: "/get_started/quickstart" },
           { text: "Hello World", link: "/get_started/hello_world" },
           { text: "Developing with AI", link: "/get_started/ai" },
@@ -516,8 +515,8 @@ export default defineConfig({
           // page in this section teaches something you do to your own app -
           // downport it, run it off-stack, extend it, wire it to something.
           // Add-ons teaches nothing: it is a list of what other people
-          // published, which is the same kind of page as References and Who
-          // Uses abap2UI5?. The pages that need it still link it by name.
+          // published, so it reads as a resource. The pages that need it still
+          // link it by name.
           {
             text: "Extensibility",
             collapsed: true,
@@ -644,10 +643,9 @@ export default defineConfig({
       },
       {
         text: "Resources",
-        link: "/resources/references",
+        link: "/resources/api",
         collapsed: true,
         items: [
-          { text: "References", link: "/resources/references" },
           // Generated from z2ui5_if_client at the pinned release by
           // scripts/generate-api-reference.mjs — the entry lives here rather
           // than in the Cookbook because it is a lookup destination, not a
@@ -662,17 +660,15 @@ export default defineConfig({
           //
           // Moved here from Advanced Topics: the ecosystem around the
           // framework rather than a technique to apply to your own app, and
-          // it closes by asking the reader to add their project - the same
-          // invitation Who Uses abap2UI5? makes below it.
+          // it closes by asking the reader to add their project.
           { text: "Add-ons", link: "/resources/addons" },
-          { text: "Who Uses abap2UI5?", link: "/resources/who_uses" },
           { text: "Release Notes", link: "/resources/changelog" },
           { text: "Deprecations", link: "/resources/deprecations" },
           {
             // The series of essays, moved here from a top-level "Know-How"
-            // section of its own: a reader looks for them next to References
-            // and Who Uses abap2UI5?, as reading about the framework rather
-            // than a step in using it. The URLs stay where they were published.
+            // section of its own: a reader looks for them among the resources,
+            // as reading about the framework rather than a step in using it.
+            // The URLs stay where they were published.
             text: "Blogs",
             link: "/advanced/insights/",
             collapsed: true,
@@ -731,10 +727,6 @@ export default defineConfig({
             collapsed: true,
             items: [
               { text: "License", link: "/resources/license" },
-              // What the license comes to for YOUR landscape: sliders for
-              // users, systems, apps and support tiers, and a sheet whose
-              // every line is zero. The front door's cost card opens it.
-              { text: "Cost Calculator", link: "/resources/cost_calculator" },
               { text: "Support", link: "/resources/support" },
               // SIDEBAR copy — the nav bar has the same two entries verbatim,
               // further up under the version number. Search for this marker,
diff --git a/docs/.vitepress/theme/cost-calculator.js b/docs/.vitepress/theme/cost-calculator.js
deleted file mode 100644
index 0d59bf45..00000000
--- a/docs/.vitepress/theme/cost-calculator.js
+++ /dev/null
@@ -1,114 +0,0 @@
-/*
- * The cost calculator, once it is in a browser.
- *
- * The page carries everything: sliders with their stops, a readout beside
- * each, choices made with checkboxes and radio buttons, a button, and - hidden
- * until the button is pressed - a sheet whose lines echo the readings, the
- * total, and the words under it.
- * All of it is written into the HTML with its answer already on it. What
- * this adds is the readout following its slider, the echoes following the
- * readout, every amount rewritten in the currency chosen, and the button.
- *
- * One delegated listener each for `input`, `change` and `click`, on the document,
- * like the Run button and the copy link: the manual's own build loads this
- * once per page and VitePress once per application, and neither has to know
- * whether the page in front of it is the calculator. `cost-model.js` is the
- * half with no DOM in it.
- */
-import { amount, line, listed, reading, stopsOf, total } from './cost-model.js';
-
-const CALCULATOR = '.cost[data-cost]';
-
-/** Every readout, echo and amount on the calculator brought in line with
- *  its sliders and its currency. Nothing to do on a page without one. */
-export function syncCostCalculator(root = document) {
-  const calc = root.querySelector(CALCULATOR);
-  if (!calc) return;
-  const settings = {};
-  for (const slider of calc.querySelectorAll('input[type="range"][data-stops]')) {
-    const said = reading(stopsOf(slider.dataset.stops), slider.value, slider.dataset.unit || '');
-    settings[slider.id] = said;
-    for (const out of calc.querySelectorAll(`output[for="${slider.id}"], [data-echo="${slider.id}"]`)) {
-      out.textContent = said;
-    }
-  }
-  /* A choice made with radio buttons or checkboxes: the group's name is the
-     setting, and what the sheet echoes is the ticked ones' words as a list -
-     or the group's own words for nothing ticked. */
-  const groups = new Map();
-  for (const box of calc.querySelectorAll('input[type="radio"][data-choice], input[type="checkbox"][data-choice]')) {
-    if (!groups.has(box.name)) groups.set(box.name, { none: box.closest('[data-none]')?.dataset.none, chosen: [] });
-    if (box.checked) groups.get(box.name).chosen.push(box.dataset.choice);
-  }
-  for (const [name, { none, chosen }] of groups) {
-    const said = listed(chosen, none);
-    settings[name] = said;
-    for (const out of calc.querySelectorAll(`[data-echo="${name}"]`)) out.textContent = said;
-  }
-  const currency = calc.querySelector('select[data-currency]')?.value || 'EUR';
-  for (const cell of calc.querySelectorAll('[data-amount]')) cell.textContent = amount(line(settings), currency);
-  for (const cell of calc.querySelectorAll('[data-total]')) cell.textContent = amount(total(settings), currency);
-}
-
-/* The button. The sheet is not on the page until it is asked for: pressing
- * Calculate greys the inputs, thinks for a moment, and hands out the sheet -
- * and then offers a new round, which puts the inputs back and takes the
- * sheet away until the next press. THE ANSWER IS THE SAME EVERY TIME, which
- * is the joke; the ceremony is what makes it land. */
-function calculate(button) {
-  const calc = button.closest(CALCULATOR);
-  const inputs = calc?.querySelector('.cost-inputs');
-  /* What the button hands out: the sheet inside the calculator, and the words
-     under it - the formula, and the one line that is not zero - which are
-     markdown outside it and carry the same mark. */
-  const results = calc ? [...calc.ownerDocument.querySelectorAll('[data-result]')] : [];
-  if (!inputs || !results.length) return;
-  const controls = inputs.querySelectorAll('input, select');
-  if (calc.dataset.state === 'calculated') {
-    for (const result of results) result.hidden = true;
-    delete inputs.dataset.locked;
-    for (const control of controls) control.disabled = false;
-    delete calc.dataset.state;
-    button.textContent = button.dataset.calculate;
-    return;
-  }
-  syncCostCalculator(calc.ownerDocument);
-  for (const control of controls) control.disabled = true;
-  inputs.dataset.locked = '';
-  button.disabled = true;
-  button.textContent = 'Calculating\u2026';
-  setTimeout(() => {
-    for (const result of results) result.hidden = false;
-    calc.dataset.state = 'calculated';
-    button.disabled = false;
-    button.textContent = button.dataset.again;
-    results[0].scrollIntoView?.({ block: 'nearest' });
-  }, 700);
-}
-
-export function setUpCostCalculator() {
-  const follow = (e) => { if (e.target.closest?.(CALCULATOR)) syncCostCalculator(); };
-  document.addEventListener('input', follow);
-  document.addEventListener('change', follow);
-  document.addEventListener('click', (e) => {
-    const button = e.target.closest?.('button[data-calculate]');
-    if (button && !button.disabled) calculate(button);
-  });
-  /* A browser puts a page's controls back where they were when it restores
-     the page - back, forward, reload - while the words beside them are the
-     page's own again. */
-  addEventListener('pageshow', () => {
-    /* ...including their DISABLED state, in Firefox: a reload after Calculate
-       brought the inputs back greyed with the sheet hidden, and one during the
-       "Calculating" moment left the button itself dead. A calculator that is
-       not showing its sheet has nothing to be locked for. */
-    for (const calc of document.querySelectorAll(CALCULATOR)) {
-      if (calc.dataset.state === 'calculated') continue;
-      for (const c of calc.querySelectorAll('.cost-inputs input, .cost-inputs select, button[data-calculate]')) c.disabled = false;
-      const inputs = calc.querySelector('.cost-inputs');
-      if (inputs) delete inputs.dataset.locked;
-    }
-    syncCostCalculator();
-  });
-  syncCostCalculator();
-}
diff --git a/docs/.vitepress/theme/cost-model.js b/docs/.vitepress/theme/cost-model.js
deleted file mode 100644
index 6c4a89ba..00000000
--- a/docs/.vitepress/theme/cost-model.js
+++ /dev/null
@@ -1,60 +0,0 @@
-/*
- * The cost calculator's arithmetic, with no DOM in it.
- *
- * The page (docs/resources/cost_calculator.md) carries the sliders and the
- * sheet as plain markup: every slider names its stops in `data-stops`, so
- * the page is the one place the numbers live and this module reads them
- * rather than knowing them. What is here is the reading of a position -
- * "10,000 users", "S/4HANA Private Cloud" - what a line of the sheet comes
- * to, the sum, and an amount written in a currency.
- *
- * The total is zero. Not rounded to zero, not zero for the default settings:
- * zero. abap2UI5 is MIT licensed and there is no edition, tier, seat or
- * per-system fee behind it, so every line on the sheet is the same number
- * whatever the sliders say, and the sum of them is that number too. The
- * functions exist so that a test can say so in code, and so the page can be
- * honest about being a calculator: it takes every input, and it returns the
- * answer. Pinned by test/cost-calculator.test.mjs.
- */
-
-/** The stops a slider steps through, as written on it: `1|5|10`, or
- *  `Community|Standard|Premium`. */
-export const stopsOf = (attr) => String(attr || '').split('|').map((s) => s.trim()).filter(Boolean);
-
-/** What a slider at `position` reads: a number with its unit ("250 users",
- *  "1 system" - `unit` is `one|many`), or the stop's own words. A position
- *  off either end reads as the end. */
-export function reading(stops, position, unit = '') {
-  if (!stops.length) return '';
-  const at = Math.min(Math.max(Math.trunc(Number(position)) || 0, 0), stops.length - 1);
-  const stop = stops[at];
-  const n = Number(stop.replace(/,/g, ''));
-  if (!Number.isFinite(n)) return stop;
-  const [one, many = one] = unit.split('|');
-  const word = n === 1 ? one : many;
-  return word ? `${n.toLocaleString('en-US')} ${word}` : n.toLocaleString('en-US');
-}
-
-/** Choices read out as a list - "A", "A and B", "A, B and C" - or `none`
- *  when nothing is ticked. */
-export function listed(choices, none = 'none') {
-  if (!choices.length) return none;
-  if (choices.length === 1) return choices[0];
-  return `${choices.slice(0, -1).join(', ')} and ${choices[choices.length - 1]}`;
-}
-
-/** What one line of the sheet comes to, for any setting of its slider. */
-export const line = () => 0;
-
-/** The sum of the sheet: every line, added up, for the settings given. */
-export const total = (settings = {}) => Object.values(settings).reduce((sum, value) => sum + line(value), 0);
-
-/** `value` in `currency`, the way English writes it: `amount(0, 'EUR')` is
- *  "€0". A runtime without the currency data gets the number and the code. */
-export function amount(value, currency) {
-  try {
-    return new Intl.NumberFormat('en', { style: 'currency', currency, maximumFractionDigits: 0 }).format(value);
-  } catch {
-    return `${value} ${currency}`;
-  }
-}
diff --git a/docs/.vitepress/theme/index.js b/docs/.vitepress/theme/index.js
index 2861ff5c..7c7af408 100644
--- a/docs/.vitepress/theme/index.js
+++ b/docs/.vitepress/theme/index.js
@@ -20,7 +20,6 @@ import './style.css'
 import { setUpPlayground } from './playground.js'
 import { setUpCodeLines, watchCodeLines } from './code-lines.js'
 import { markDirective, setUpLinkToSelection } from './link-to-selection.js'
-import { setUpCostCalculator } from './cost-calculator.js'
 import TheBar from './TheBar.vue'
 import SiteNav from './SiteNav.vue'
 import Crumbs from './Crumbs.vue'
@@ -61,10 +60,6 @@ export default {
     // (about -> brand -> Home) never started its example.
     const rearmPlayground = import.meta.env.SSR ? undefined : setUpPlayground()
 
-    // The cost calculator's sliders and the sheet under them
-    // (cost-calculator.js): two delegated listeners for the whole site, and
-    // nothing to do on any page but resources/cost_calculator.
-    if (!import.meta.env.SSR) setUpCostCalculator()
 
     // A number beside every line of every listing, and an address for it -
     // #B2L42 is line 42 of the second listing on the page, #B2L42-L58 a
diff --git a/docs/evaluate.md b/docs/evaluate.md
deleted file mode 100644
index 8d356fb5..00000000
--- a/docs/evaluate.md
+++ /dev/null
@@ -1,310 +0,0 @@
----
-# THE PAGE FOR THE PERSON WHO APPROVES IT, drawn like the front door and not
-# like a chapter: no sidebar, no outline, no crumb trail saying "Documentation
-# > Getting Started" over the first line. A developer sends this link to the
-# person who decides, and that person must not land in the manual. It is the
-# `landing` layout of build-site.mjs: the hero carries the name, the claim,
-# the intro and the two doors; the screenshot stands where the front door has
-# its mark, because the reader of this page will not open the playground to
-# see an app; the counted figures stand under the hero (lib/facts.mjs); the
-# H2 sections are bands across the width; the four tiles at the end are the
-# four ways to start, in order of effort, so the last section does not list
-# them a second time.
-#
-# The H1 stays in the body - the search index and the sidebar test read it
-# there - and the layout prints it in the hero instead, once.
-layout: landing
-title: Evaluate abap2UI5
-outline: [2, 4]
-description: abap2UI5 for the people who approve a tool rather than build with it - what problem it answers, when it is the right choice and when RAP is, what your organization keeps, where it runs, what it costs, the objections a review board raises, and how to test it on one real screen in a week.
-hero:
-  name: For the people who approve it
-  tagline: "For IT management, architecture boards, product owners, SAP Basis and internal audit: the questions a review asks, in the order it asks them, each with the page that carries the detail. A developer who wants to see it run is better served by the Quickstart; send them there and read on."
-  image:
-    src: /tutorials/walkthrough-preview.webp
-    alt: "An abap2UI5 app: a selection form above a table of invoices, with a dialog editing one row"
-  actions:
-    - theme: brand
-      text: Try it in the playground
-      link: https://abap2ui5.github.io/playground/
-      target: _self
-    - theme: alt
-      text: Read the technical picture
-      link: /get_started/about
-  note: "Nothing to install, no trial license, no sales call — the playground runs in your browser."
-features:
-  - title: Ten minutes, nothing installed
-    icon: <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" aria-hidden="true"><circle cx="12" cy="12" r="8.6" fill="none" stroke="currentColor" stroke-width="1.7"/><path d="M10.2 8.4v7.2a.5.5 0 0 0 .76.43l5.8-3.6a.5.5 0 0 0 0-.86l-5.8-3.6a.5.5 0 0 0-.76.43z" fill="currentColor"/></svg>
-    details: Open the playground and change a running app, or browse the sample catalog for the screen closest to yours.
-    link: https://abap2ui5.github.io/playground/samples/
-    target: _self
-  - title: One afternoon, one developer
-    icon: <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" aria-hidden="true"><path fill="none" stroke="currentColor" stroke-width="1.7" stroke-linejoin="round" stroke-linecap="round" d="M8 7.5 3.5 12 8 16.5M16 7.5l4.5 4.5-4.5 4.5M13.6 4.8 10.4 19.2"/></svg>
-    details: Send them the Quickstart — abapGit pull, ICF node, first app. The tutorial takes the same app to transport and unit tests.
-    link: /get_started/quickstart
-  - title: One question
-    icon: <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" aria-hidden="true"><path fill="none" stroke="currentColor" stroke-width="1.7" stroke-linejoin="round" stroke-linecap="round" d="M4 5.5h16v10H9l-4.5 3.5z"/></svg>
-    details: Ask it in the Slack channel or as a GitHub issue, where the people who run it in production answer.
-    link: https://abapgit.slack.com/join/shared_invite/zt-46tqufaht-QlrxTzlDqlx85CWbeUnOqg#/shared-invite/email
-  - title: A partner
-    icon: <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" aria-hidden="true"><path fill="none" stroke="currentColor" stroke-width="1.7" stroke-linejoin="round" stroke-linecap="round" d="M3.5 19.5V9l5.5 3.5V9l5.5 3.5V9l6 3.5v7zM3.5 19.5h17M6 4.5h3v7.5"/></svg>
-    details: The companies on Who Uses abap2UI5? offer implementation, workshops and support agreements.
-    link: /resources/who_uses
----
-# Evaluate abap2UI5
-
-## The problem it answers
-
-Every SAP system has screens nobody shipped: the cockpit for one team, the
-monitor for one process, the selection screen with a result list that used to
-be a report with an ALV. They are not standard floorplans, so Fiori Elements
-does not cover them; they are not worth a frontend project, an OData service
-and a deployment pipeline, so they stay in SAP GUI, in a spreadsheet, or on
-paper. And on a system older than S/4HANA, RAP is not there to build them
-with at all.
-
-abap2UI5 is the shorter path for exactly these screens. An app is one ABAP
-class, written in ADT or SE80, transported like any other class, and it
-renders as a UI5 app in the browser, in the Fiori launchpad, or on a mobile
-device. There is no service, no frontend project and nothing to deploy. The
-rest of this page is what that costs and what it does not.
-
-→ *[In a Nutshell](/get_started/about) is the technical picture of how the
-framework works, for the architect who wants to see the roundtrip*
-
-## When to use it, and when not
-
-abap2UI5 is one way to put a UI5 interface on ABAP. RAP with Fiori Elements
-is another, freestyle UI5 with OData a third, and all three run side by side
-in the same launchpad. Written so that a team can disagree with a specific
-line rather than with a feeling:
-
-**Use abap2UI5 when**
-
-- **The team is ABAP.** No JavaScript, no UI5 tooling, no Business
-  Application Studio to set up. An app is one class, written, debugged,
-  transported and unit-tested like every other class.
-- **The system is older than RAP.** NetWeaver 7.02 to 7.4x have no RAP and
-  a Fiori stack that is expensive to add. abap2UI5 runs there from the same
-  source it runs on ABAP Cloud, so an app written on 7.31 today moves to
-  S/4HANA unchanged.
-- **The screen is yours, not SAP's.** Tools, cockpits, monitors, admin
-  consoles, anything that used to be a report or a module pool. The moment
-  a screen is a dashboard with a chart and a custom form, a Fiori Elements
-  template becomes the thing you fight.
-- **You do not want a deployment pipeline.** No BSP upload, no approuter, no
-  MTA. The ABAP system serves the frontend; an abapGit pull is the
-  installation.
-- **You replace SAP GUI screens one at a time.** Selection screens, lists and
-  transactions become browser apps without rewriting the logic behind them.
-
-**Use RAP and Fiori Elements when**
-
-- **The service is the product.** Other consumers, a mobile app, an
-  integration, SAP's own apps, need the OData service anyway. RAP gives you
-  the service and the UI from one model; abap2UI5 gives you a UI and no
-  service.
-- **The screen is a standard floorplan and should stay one.** List report,
-  object page, worklist, with SAP's draft handling and flexible column layout
-  as SAP ships and maintains them. Fiori Elements tracks every UI5 release
-  for you; a hand-built screen is yours to keep current.
-- **The data is large and lives behind paging.** Fiori Elements pages, sorts
-  and filters through OData on the server. In abap2UI5 the table a view
-  binds travels with the model; thousands of rows are routine, millions are
-  the app's job to page.
-- **Offline, or a native mobile SDK, is a requirement.** abap2UI5 is a
-  roundtrip to the ABAP system on every interaction. It has a mobile shell
-  for camera, barcode and location; it has no offline store.
-- **A frontend team should own the frontend.** The app is one ABAP class;
-  that is the point, and it means there is no frontend project for a
-  separate team to own, and no place for heavy client-side behavior.
-- **The organization has standardized on it.** A clean-core guideline that
-  names RAP as the extensibility model is a decision already taken.
-  abap2UI5 passes the ABAP Cloud checks, but it is not SAP's programming
-  model, and a review board will say so.
-
-The common answer is not either. Standard transactional screens as Fiori
-Elements, the tools and cockpits around them as abap2UI5, both as tiles in
-the same launchpad with navigation between them. What it costs either way:
-
-| | abap2UI5 | RAP + Fiori Elements |
-|---|---|---|
-| Skills | ABAP, and a reading knowledge of the UI5 control API | ABAP, CDS, RAP, annotations, and someone who can debug the Fiori Elements template |
-| First screen | One class, minutes | Data model, behavior definition, service, Fiori project, deploy: a day when everything is set up |
-| Custom UI | Any UI5 control, 1:1, from ABAP | Extension points; past them, a freestyle UI5 project |
-| Upgrade | The framework is a transport; the public API is held by a snapshot and deprecations are tracked | SAP's; the template follows the UI5 release |
-| Reuse by other consumers | None, there is no service | The OData service, by anything |
-| Runs on | NetWeaver 7.02 to ABAP Cloud, UI5 1.71 to 2.x | 7.5x and later for RAP, ABAP Cloud for the full model |
-| License | MIT, no per-user cost | Part of the platform license |
-
-→ *[On-Stack or Side-by-Side](/advanced/insights/30-on-stack-or-side-by-side)
-and [One App, Many Systems](/advanced/insights/31-one-app-many-systems) are
-the deployment scenarios in detail*
-
-## What you keep
-
-The decision everything else follows from: an abap2UI5 app is code, not
-configuration. One ABAP class per app, no designer, no generated artifacts,
-no tables that describe a screen. That is what makes it govern itself:
-
-| | abap2UI5 | A tool that stores apps as configuration |
-|---|---|---|
-| What an app is | An ABAP class | Entries in the tool's tables, read by its runtime |
-| Where a change is made | In the development system, in ADT or SE80 | Wherever the tool's designer is open, possibly production |
-| How a change travels | A transport, like any class | The tool's own export, or a customizing transport |
-| How a change is reviewed | As a code diff: in abapGit, a pull request or the transport | In the tool's designer, if it shows a history at all |
-| What a debugger shows | Your code | The tool's runtime interpreting your configuration |
-| What happens if the tool goes away | The classes stay; they are plain ABAP | The apps go with it |
-
-So abap2UI5 needs no rule of its own. Every rule that already applies to
-ABAP, naming conventions, code review, ATC, the four-eyes principle on
-transports, applies to an app without any change. A system closed for
-repository changes is closed for abap2UI5 apps.
-
-- **Authentication is SAP's.** No user store, no token, no session concept
-  of its own. A request that reaches an app has passed SAP logon.
-- **Authorization is two gates.** The authorization object on the ICF node,
-  as for any service, and the app's own authority checks in its code, the
-  same way a transaction or a report does them. The framework adds no
-  central check on purpose.
-- **Data changes are your code's.** An app posts a document by calling the
-  same BAPIs, function modules or RAP actions any other ABAP program calls,
-  so change documents, application logs and the authority checks behind
-  them apply unchanged.
-- **Every roundtrip can be logged.** A monitor interface receives, for each
-  request, the user, the app, the event, the timings and any error. It is
-  off until an installation switches it on.
-- **Clean core.** abap2UI5 uses released APIs only, passes the ABAP Cloud
-  checks and runs in ABAP Cloud, on S/4HANA and on BTP, from the same source
-  that runs on NetWeaver 7.02. It modifies nothing in the SAP standard.
-
-The price is that someone has to write ABAP. There is no click-together
-designer for business users, on purpose: a designer would put a second kind
-of app definition next to the code, and that second kind is exactly what the
-table above has to govern separately.
-
-→ *More on [Security](/configuration/security) and
-[Authorization](/configuration/authorization), and the
-[security model](https://github.com/abap2UI5/abap2UI5/blob/main/docs/security.md)
-a security review starts from: what the framework guarantees, and which test
-holds the code to each guarantee*
-
-## Where it runs
-
-```
-Browser                          SAP system (the only server)
-───────────────────────────      ────────────────────────────────────────────
-generic UI5 shell, loaded   ───▶ ICF node → abap2UI5 handler → your app class
-once; no app code of its         SAP logon, authorization objects, sy-uname
-own                              app state in one table, per user
-```
-
-The browser runs a generic UI5 shell, the same for every app. App code never
-leaves the system; the browser receives the view and the data the app chose
-to bind. There is one HTTP endpoint, an ICF node, and nothing else listens.
-No middleware, no extra server, no BTP subscription, no frontend deployment.
-
-- **Systems:** S/4HANA Public Cloud and BTP ABAP Environment (ABAP for
-  Cloud), S/4HANA Private Cloud and on-premise, and NetWeaver 7.02 or later.
-- **UI5:** the frontend is UI5 itself, 1.71 to 2.x. By default it loads from
-  the public CDN; a productive installation points it at the UI5 the system
-  already ships, which is what a system without internet access uses.
-- **Where an app appears:** a browser tab, a Fiori launchpad tile, SAP Build
-  Work Zone, Microsoft Teams, Microsoft Excel, a native app on iOS and
-  Android, or embedded in a UI5 app of your own.
-
-What Basis does, all of it: pull the package with abapGit, create the ICF
-node and put an authorization object on it, change the four production
-defaults in the user exit (UI5 source, error details, the Content Security
-Policy, the node authorization), and optionally switch on the monitor. There
-is no job to schedule and no schema to migrate on upgrade.
-
-→ *More on [Productive Usage](/configuration/productive_usage),
-[UI5 Versions](/configuration/ui5_versions),
-[Performance](/configuration/performance) and
-[Integration](/integration/)*
-
-## What it costs
-
-abap2UI5 is MIT licensed, commercial use included. No license key, no
-subscription, no per-user, per-system or per-app fee, now or later. The
-apps built with it are standard UI5 freestyle apps, licensed the way your
-organization licenses every other UI5 app. It runs on the ABAP stack and
-the UI5 version you already have.
-
-What is not free is the work: an ABAP developer's time to write the screen,
-and the evenings of the volunteers who maintain the framework. Support is
-the community's, on GitHub issues and Slack, on a best-effort basis; there
-is no vendor SLA to buy from the project. Companies and freelancers offer
-paid implementation, training and support agreements around it.
-
-→ *More on the [Cost Calculator](/resources/cost_calculator),
-the [License](/resources/license) and [Support](/resources/support)*
-
-## The objections
-
-The questions a review board raises, with the honest answer to each.
-
-**It is an open-source project. What if the maintainers stop?**
-The installed version keeps running, the source is in your system in full,
-readable and changeable, and the apps stay ordinary ABAP classes. Nothing is
-called at runtime that is not in your system, apart from the UI5 library,
-which you can host yourself. A build renamed into your own namespace is one
-workflow run ([Namespaces, Renaming](/advanced/renaming)).
-
-**Is this another UI5 wrapper that will not survive the next UI5 release?**
-The frontend is UI5 itself, not a copy of it, and every merge is run in the
-browser on the oldest supported release and on UI5 2.x. Releases are tagged
-and listed ([Release Notes](/resources/changelog)); what is on its way out is
-announced and tracked until removal ([Deprecations](/resources/deprecations)),
-and the public API apps use is held by a snapshot, so a change to it fails
-the framework's own pull request.
-
-**Every click is a roundtrip. Is that fast enough?**
-A roundtrip is one HTTP POST carrying only what changed, served by the ABAP
-stack that already serves everything else. For the screens this page is
-about, worklists, forms, cockpits, it is the same round trip a SAP GUI
-screen makes, in a browser. What it is not built for is a real-time
-collaborative editor or an app that holds its state offline
-([Performance](/configuration/performance)).
-
-**Our clean-core guideline names RAP. Where does this leave us?**
-Side by side. abap2UI5 passes the ABAP Cloud checks and modifies nothing in
-the standard, so it is clean core in the technical sense, but it is not
-SAP's programming model. The usual outcome is a scope: standard
-transactional screens in RAP, the tools around them in abap2UI5, both in one
-launchpad.
-
-**Who is accountable when something breaks?**
-Your developer, for the app, the same as for any class in the system; the
-community, for the framework, on a best-effort basis; a commercial partner,
-if you sign one. Security reports are acknowledged within three business
-days ([Security](/configuration/security)).
-
-**Is anybody actually running this in production?**
-Yes, see below. And every release is tested against Standard ABAP and ABAP
-Cloud, downported and linted against NetWeaver 7.02, and run in the browser
-on the oldest and the newest supported UI5 release
-([verified on](https://github.com/abap2UI5/abap2UI5/blob/main/docs/verified-on.md)).
-
-## Who runs it
-
-Companies run abap2UI5 apps for EWM and PP on desktop and mobile devices,
-consultancies offer workshops and certifications for it, and it has been
-featured in SAP Developer News and at SAP TechEd. [Who Uses abap2UI5?](/resources/who_uses)
-lists the companies with their system release and use case;
-[References](/resources/references) lists the talks, articles and videos by
-year. Both are open for your own row.
-
-## How to evaluate it in a week
-
-Take one real screen your team has to build this quarter. Build it with
-abap2UI5 in a development system, with the people who will maintain it, and
-review it the way your organization reviews ABAP: read the class, transport
-it, run ATC on it, check the authorizations it asks for. Count the files,
-the systems and the tools involved, and the time until a user can click it.
-Then hold this page against the security model and the verified-on page
-with the skepticism you would apply to a vendor's slide, and decide from
-the screen, not from the slide.
-
-Where to start, in order of effort, is under this line.
diff --git a/docs/get_started/about.md b/docs/get_started/about.md
index fac2111a..57742df7 100644
--- a/docs/get_started/about.md
+++ b/docs/get_started/about.md
@@ -35,7 +35,7 @@ A finished app looks like any other UI5 app, because it is one — a selection s
 ## Background
 Since launching in 2023, abap2UI5 has grown from a small side project into a community-driven framework used by ABAP developers worldwide. The framework absorbs frontend complexity, so you can focus on business logic with your existing ABAP skills. Each app ships as an [abapGit](https://abapgit.org) project, so installation across systems needs no separate frontend deployment.
 
-This page is the technical picture. Whether abap2UI5 is the right tool for a screen, what an organization keeps and what it costs is on [Evaluate abap2UI5](/evaluate), written for the people who approve a tool rather than build with it.
+This page is the technical picture. What abap2UI5 means for an organization - what it can build, how it compares, what it costs - is on [abap2UI5 for decision makers](https://abap2ui5.github.io/test-docs/), written for the people who approve a tool rather than build with it.
 
 → *See the [Quickstart](/get_started/quickstart) for step-by-step setup, and [Sample Apps](https://abap2ui5.github.io/playground/samples/) to watch abap2UI5 in action*
 
@@ -118,6 +118,4 @@ abap2UI5 unusually well suited to being written with one.
 Volunteers maintain abap2UI5, and the community is where help comes from:
 [Support](/resources/support) on GitHub and Slack, the
 [Contribution Guide](/resources/contribution) for fixing and building, and
-[sponsorship](/resources/sponsor) if the project saves yours time. Companies,
-workshops and open-source projects already running on it are listed on
-[Who Uses abap2UI5?](/resources/who_uses) — add your own scenario there.
+[sponsorship](/resources/sponsor) if the project saves yours time.
diff --git a/docs/get_started/hello_world.md b/docs/get_started/hello_world.md
index 8fdbaec9..d6cf8f5e 100644
--- a/docs/get_started/hello_world.md
+++ b/docs/get_started/hello_world.md
@@ -147,13 +147,11 @@ From there, pick the direction that fits:
 - **Go live.** Security, performance, the launchpad and the transport are under
   [Configuration](/configuration/installation); [Productive Usage](/configuration/productive_usage)
   is the page to read before the first go-live.
-- **See who runs it.** [Who Uses abap2UI5?](/resources/who_uses) lists ready-to-use
-  apps, real-world scenarios and companies already running on it; the
-  [add-ons](/resources/addons) cover what not every app needs.
-- **Need somebody's approval?** [Evaluate abap2UI5](/evaluate) is
-  the page for the person who decides whether it may be used: when to use it
-  and when RAP, what the organization keeps, what it costs, and the objections
-  a review board raises. Send the link rather than the argument.
+- **Extend it.** The [add-ons](/resources/addons) cover what not every app
+  needs.
+- **Need somebody's approval?** [abap2UI5 for decision makers](https://abap2ui5.github.io/test-docs/) is
+  the page for the person who decides whether it may be used. Send the link
+  rather than the argument.
 
 <!-- samples:start (generated by scripts/link-samples.mjs — do not edit) -->
 
diff --git a/docs/get_started/quickstart.md b/docs/get_started/quickstart.md
index c26619a6..cf4cdc3c 100644
--- a/docs/get_started/quickstart.md
+++ b/docs/get_started/quickstart.md
@@ -147,4 +147,4 @@ is the next page: it is the smallest app that can exist, how to start it, and
 what each line of it does.
 
 If somebody else decides whether abap2UI5 may be used on your system,
-[Evaluate abap2UI5](/evaluate) is the page written for them.
+[abap2UI5 for decision makers](https://abap2ui5.github.io/test-docs/) is the page written for them.
diff --git a/docs/index.md b/docs/index.md
index b4c4d2e5..2c4c962e 100644
--- a/docs/index.md
+++ b/docs/index.md
@@ -18,8 +18,8 @@ description: One ABAP class is one UI5 app - no JavaScript, no OData, no fronten
 # colleague's link, and who has not decided to read a manual yet.
 #
 # So the page answers, in this order: what it is (the hero), the four answers
-# a decision needs — security, integration, AI, cost — what one app looks
-# like, running right here, and then where to go next (the three tiles).
+# a developer asks first — security, integration, AI — what one app looks
+# like, running right here, and then where to go next (the tiles).
 # Under it, one line of where the project lives. A reader who wants the
 # manual is one word away in the bar; this page does not compete with it.
 #
@@ -34,43 +34,24 @@ description: One ABAP class is one UI5 app - no JavaScript, no OData, no fronten
 # two or three paragraphs each - the enterprise card alone ran to 120 words -
 # and four panels of prose under three tiles read as a page that starts
 # over. What a card says now is the claim, one sentence that backs it, and
-# the link to the page that argues it in full: the Evaluate page carries the
-# lifecycle, the exit path and the support model (the About page did, until
-# it was cut back to the technical picture).
+# the link to the page that argues it in full.
 # Nothing in the paragraph is bold: the heading carries the claim, the text
 # reads as one run. The headings are claims too, not labels: "Plays well with what you have"
 # promises something, where "Integration" only named a topic. The last card
 # asks instead, and its first word is the one-word answer.
 #
 # THE ORDER IS AN ARGUMENT: it is safe here, and it fits what you run - then
-# an agent can write it, and it costs nothing. The price is the last card
-# because it is the closing line: a reader who has taken the first three
-# reaches "Nothing." as the answer to the question the cards have built up
-# to. It is not hidden for being last - the tagline says "free, MIT
-# licensed" in the first screen, and the cards are one sentence each now,
-# so all four stand on one desk screen.
+# an agent can write it. The price card that closed the row is gone with the
+# rest of the case for the buyer (THIS PAGE IS FOR THE DEVELOPER, below); the
+# description and the license page still say MIT.
 #
-# THE CARDS ANSWER A BUYER, not only a developer - somebody who would otherwise
-# license a low-code platform, and who asks what a developer does not: who is
-# behind this, what happens when nobody is, how an app is governed, what it is
-# not for. The answers - lifecycle (transports, ATC, ABAP Unit), exit path (a
-# handful of classes and one table), versioned releases, support as it is
-# (the community's, no vendor SLA) - stand on the Evaluate page, and each card
-# links the section that carries them. References by name and a list of what
-# this is NOT for were tried here and taken out again by the maintainer: the
-# limits stay on the Evaluate page, the references on Who Uses abap2UI5.
-#
-# THIS PAGE IS FOR THE MANAGER. A developer has usually found the project by
-# another path - a talk, a sample, the playground - and the person this page
-# has to convince is the one who decides whether it may be used. So nothing
-# here is arranged for a developer's reading order: the cards come before the
-# code. What a developer gets anyway, because it costs the manager nothing,
-# is the example itself - there is no paragraph in front of it any more; the
-# heading and the running app say what it is - one way out behind it (the
-# tutorial, through to transport and unit tests), and the UI5 releases in
-# the integration card. The daily tools
-# - ADT, the ABAP debugger, ABAP Unit, the linter, the MCP server - are on
-# the Tooling page, one click into the manual.
+# THIS PAGE IS FOR THE DEVELOPER. The manual is technical; the case for the
+# person who approves abap2UI5 - what it can build, how it compares with RAP,
+# freestyle UI5 and commercial platforms, what it costs, who runs it - is a
+# site of its own (https://abap2ui5.github.io/test-docs/, abap2UI5/test-docs).
+# This page argues none of that a second time: the hero's second button and
+# the last tile hand that reader over, once each, and every claim on a card
+# links a page of the manual.
 #
 # THE THREE TILES ARE TASKS, NOT PLACES. They used to say Documentation,
 # Samples, Playground - the same three words, in the same order, with the
@@ -105,13 +86,12 @@ description: One ABAP class is one UI5 app - no JavaScript, no OData, no fronten
 # but never displayed is a question this example is not here to answer.
 #
 # EVERY CARD ENDS WITH A WAY OUT, ON A LINE OF ITS OWN: "→ More on …" in
-# italics, the same shape on all four, so the cards read as one structure
+# italics, the same shape on all three, so the cards read as one structure
 # and the eye finds the link in the same place on each. The example's line
 # under the code is the same shape again. The link sits on the topic, never on the word
 # "here" - a reader scanning the links has to be able to tell where each one
-# goes. The cost card's is the calculator - a page of sliders for users,
-# systems, apps and support tiers whose every line comes to zero - in the
-# same "More on …" words as the other three, so the four lines read as one. A second
+# goes, in the same "More on …" words on all three, so the lines read as
+# one. A second
 # link to the same page inside one card is the "every claim once" rule broken
 # with a hyperlink.
 #
@@ -154,15 +134,9 @@ hero:
   # page, but neither is a call to action in the first screen, and a first
   # screen with no primary action reads as a brochure. Same tab (target
   # _self), like every other way into the neighbouring site. The outlined
-  # one opens the page written for the manager this page is written for:
-  # "Evaluate abap2UI5" - when to use it and when RAP, what the organization
-  # keeps, where it runs, what it costs, the objections, and how to test it
-  # on one real screen. It used to open "In a Nutshell", the technical
-  # picture, which is one click into the manual and the page for the
-  # architect. (A playground button stood here before and was taken out as the
-  # third copy of what the page already offered twice; it is back as the
-  # primary action on purpose - the two readers of this page want different
-  # first clicks, and the hero can afford one each.)
+  # one opens "In a Nutshell", the technical picture of how the framework
+  # works. The page for the person who approves abap2UI5 is the last tile,
+  # not a button: this page is the developer's.
   # THE LINE UNDER THE BUTTONS is what the primary one costs. A vendor's
   # first screen says "start free trial" and means a license key, a runtime
   # of your own and a call; this one means a browser tab. Said once, here,
@@ -175,13 +149,13 @@ hero:
       link: https://abap2ui5.github.io/playground/
       target: _self
     - theme: alt
-      text: Evaluate it for your organization
-      link: /evaluate
+      text: See how it works
+      link: /get_started/about
 
 # Four things to do next, each on the page for it. The bar names the
 # places; these name the tasks (see THE THREE TILES ARE TASKS above). The
-# fourth is the decision-maker's task - evaluate it for a team - because a
-# reader who is not going to build anything still has one thing to do. They
+# fourth hands the page over to whoever approves abap2UI5 - a site of its own,
+# so the manual does not argue the case a second time. They
 # are frontmatter, so VitePress draws them under the hero; the published page
 # draws them UNDER THE EXAMPLE (build-site.mjs), where "what next" belongs.
 features:
@@ -198,10 +172,11 @@ features:
     icon: <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" aria-hidden="true"><path fill="none" stroke="currentColor" stroke-width="1.7" stroke-linejoin="round" stroke-linecap="round" d="M3.5 19.5V9l5.5 3.5V9l5.5 3.5V9l6 3.5v7zM3.5 19.5h17M6 4.5h3v7.5"/></svg>
     details: Security, authorizations, the launchpad tile, the transport — what a go-live needs, on one page.
     link: /configuration/productive_usage
-  - title: Evaluate it for your team
+  - title: Send it to whoever decides
     icon: <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" aria-hidden="true"><path fill="none" stroke="currentColor" stroke-width="1.7" stroke-linejoin="round" stroke-linecap="round" d="M4 12.5 9 17.5 20 6.5"/></svg>
-    details: When to use it and when RAP, what your organization keeps, what it costs, and the objections a review board raises — on one page.
-    link: /evaluate
+    details: What abap2UI5 means for an organization — what it can build, how it compares, what it costs — for the person who approves it.
+    link: https://abap2ui5.github.io/test-docs/
+    target: _self
 ---
 
 ## Ready for your enterprise
@@ -210,7 +185,7 @@ abap2UI5 runs inside the security you already have. One HTTP endpoint,
 standard SAP logon, your own authorizations — and an app is an ABAP class, so
 transports, ATC and ABAP Unit apply as they do to everything else you ship.
 
-→ *More on [What you keep](/evaluate#what-you-keep)*
+→ *More on [Security](/configuration/security)*
 
 ## Plays well with what you have
 
@@ -229,15 +204,6 @@ before a developer looks at it.
 
 → *More on [Developing with AI](/get_started/ai)*
 
-## And what does it cost?
-
-Nothing. MIT licensed, commercial use included — no license key, no
-subscription, no per-user fee, and no BTP required. It runs on your ABAP stack
-with the UI5 version already installed, and the license you have is the one
-you keep.
-
-→ *More on [Cost Calculator](/resources/cost_calculator)*
-
 ## Try it out now
 
 ```abap edit
diff --git a/docs/public/evaluate.html b/docs/public/evaluate.html
new file mode 100644
index 00000000..8c0a4423
--- /dev/null
+++ b/docs/public/evaluate.html
@@ -0,0 +1,23 @@
+<!doctype html>
+<!--
+  Redirect: "Evaluate abap2UI5" lived here. The framework README links #what-you-keep and #when-to-use-it-and-when-not, and the new page keeps every section id, so the #fragment is carried over.
+  abap2UI5 for decision makers is its own site now (abap2UI5/test-docs), and
+  the manual is for developers. Old links keep working; delete this only when
+  the old URL has stopped receiving traffic.
+-->
+<html lang="en">
+  <head>
+    <meta charset="utf-8">
+    <title>Page moved - abap2UI5</title>
+    <link rel="canonical" href="https://abap2ui5.github.io/test-docs/">
+    <meta http-equiv="refresh" content="0; url=https://abap2ui5.github.io/test-docs/">
+    <meta name="robots" content="noindex">
+    <script>location.replace('https://abap2ui5.github.io/test-docs/' + location.hash);</script>
+  </head>
+  <body>
+    <p>
+      This page moved to
+      <a href="https://abap2ui5.github.io/test-docs/" target="_self">abap2UI5 for decision makers</a>.
+    </p>
+  </body>
+</html>
diff --git a/docs/public/get_started/evaluate.html b/docs/public/get_started/evaluate.html
index fb85b272..7743ba12 100644
--- a/docs/public/get_started/evaluate.html
+++ b/docs/public/get_started/evaluate.html
@@ -1,29 +1,23 @@
 <!doctype html>
 <!--
-  Redirect for the page that lived at /docs/get_started/evaluate for one day
-  (2026-10-23). It moved to /docs/evaluate when it got the landing layout: the
-  page is sent to the person who approves abap2UI5, and "get_started" in the
-  address said "manual" before they had read a word. The framework's README
-  and two of its docs pages linked the old address - so it keeps working.
-
-  VitePress has no redirect mechanism; files under public/ are copied into the
-  build verbatim, which is why this is a hand-written page. The one-line
-  script keeps a #fragment, because the links into it name sections. Delete
-  it only when the old URL has stopped receiving traffic.
+  Redirect: the page lived at /docs/get_started/evaluate for one day (2026-10-23), then at /docs/evaluate.
+  abap2UI5 for decision makers is its own site now (abap2UI5/test-docs), and
+  the manual is for developers. Old links keep working; delete this only when
+  the old URL has stopped receiving traffic.
 -->
 <html lang="en">
   <head>
     <meta charset="utf-8">
     <title>Page moved - abap2UI5</title>
-    <link rel="canonical" href="https://abap2ui5.github.io/docs/evaluate.html">
-    <meta http-equiv="refresh" content="0; url=/docs/evaluate.html">
+    <link rel="canonical" href="https://abap2ui5.github.io/test-docs/">
+    <meta http-equiv="refresh" content="0; url=https://abap2ui5.github.io/test-docs/">
     <meta name="robots" content="noindex">
-    <script>location.replace('/docs/evaluate.html' + location.hash);</script>
+    <script>location.replace('https://abap2ui5.github.io/test-docs/' + location.hash);</script>
   </head>
   <body>
     <p>
       This page moved to
-      <a href="/docs/evaluate.html">Evaluate abap2UI5</a>.
+      <a href="https://abap2ui5.github.io/test-docs/" target="_self">abap2UI5 for decision makers</a>.
     </p>
   </body>
 </html>
diff --git a/docs/public/resources/cost_calculator.html b/docs/public/resources/cost_calculator.html
new file mode 100644
index 00000000..4f8b1f00
--- /dev/null
+++ b/docs/public/resources/cost_calculator.html
@@ -0,0 +1,23 @@
+<!doctype html>
+<!--
+  Redirect: the cost calculator lived here; the decision makers page carries it.
+  abap2UI5 for decision makers is its own site now (abap2UI5/test-docs), and
+  the manual is for developers. Old links keep working; delete this only when
+  the old URL has stopped receiving traffic.
+-->
+<html lang="en">
+  <head>
+    <meta charset="utf-8">
+    <title>Page moved - abap2UI5</title>
+    <link rel="canonical" href="https://abap2ui5.github.io/test-docs/#what-it-costs">
+    <meta http-equiv="refresh" content="0; url=https://abap2ui5.github.io/test-docs/#what-it-costs">
+    <meta name="robots" content="noindex">
+    <script>location.replace('https://abap2ui5.github.io/test-docs/#what-it-costs');</script>
+  </head>
+  <body>
+    <p>
+      This page moved to
+      <a href="https://abap2ui5.github.io/test-docs/#what-it-costs" target="_self">What it costs</a>.
+    </p>
+  </body>
+</html>
diff --git a/docs/public/resources/references.html b/docs/public/resources/references.html
new file mode 100644
index 00000000..724ef654
--- /dev/null
+++ b/docs/public/resources/references.html
@@ -0,0 +1,23 @@
+<!doctype html>
+<!--
+  Redirect: the References list (talks, articles, videos) lived here; the decision makers page carries it.
+  abap2UI5 for decision makers is its own site now (abap2UI5/test-docs), and
+  the manual is for developers. Old links keep working; delete this only when
+  the old URL has stopped receiving traffic.
+-->
+<html lang="en">
+  <head>
+    <meta charset="utf-8">
+    <title>Page moved - abap2UI5</title>
+    <link rel="canonical" href="https://abap2ui5.github.io/test-docs/#who-runs-it">
+    <meta http-equiv="refresh" content="0; url=https://abap2ui5.github.io/test-docs/#who-runs-it">
+    <meta name="robots" content="noindex">
+    <script>location.replace('https://abap2ui5.github.io/test-docs/#who-runs-it');</script>
+  </head>
+  <body>
+    <p>
+      This page moved to
+      <a href="https://abap2ui5.github.io/test-docs/#who-runs-it" target="_self">Who runs it</a>.
+    </p>
+  </body>
+</html>
diff --git a/docs/public/resources/who_uses.html b/docs/public/resources/who_uses.html
new file mode 100644
index 00000000..96dd30f0
--- /dev/null
+++ b/docs/public/resources/who_uses.html
@@ -0,0 +1,23 @@
+<!doctype html>
+<!--
+  Redirect: "Who Uses abap2UI5?" lived here; the decision makers page carries the list.
+  abap2UI5 for decision makers is its own site now (abap2UI5/test-docs), and
+  the manual is for developers. Old links keep working; delete this only when
+  the old URL has stopped receiving traffic.
+-->
+<html lang="en">
+  <head>
+    <meta charset="utf-8">
+    <title>Page moved - abap2UI5</title>
+    <link rel="canonical" href="https://abap2ui5.github.io/test-docs/#who-runs-it">
+    <meta http-equiv="refresh" content="0; url=https://abap2ui5.github.io/test-docs/#who-runs-it">
+    <meta name="robots" content="noindex">
+    <script>location.replace('https://abap2ui5.github.io/test-docs/#who-runs-it');</script>
+  </head>
+  <body>
+    <p>
+      This page moved to
+      <a href="https://abap2ui5.github.io/test-docs/#who-runs-it" target="_self">Who runs it</a>.
+    </p>
+  </body>
+</html>
diff --git a/docs/resources/cost_calculator.md b/docs/resources/cost_calculator.md
deleted file mode 100644
index 4bfa3d41..00000000
--- a/docs/resources/cost_calculator.md
+++ /dev/null
@@ -1,66 +0,0 @@
----
-outline: [2, 4]
-description: What abap2UI5 costs for your users, systems, apps and support, worked out slider by slider - why every line of the sheet comes to the same number, what that number gets you, and who paid for it.
----
-# Cost Calculator
-
-Set the sliders to your landscape, tick your systems and your support, pick a currency, press Calculate, and read off what abap2UI5 will cost you.
-
-<div class="cost" data-cost>
-<div class="cost-inputs">
-<div class="cost-row"><label for="cost-users">Named users</label><input id="cost-users" type="range" min="0" max="15" value="6" data-stops="1|5|10|25|50|100|250|500|1000|2500|5000|10000|25000|50000|100000|250000" data-unit="user|users"><output for="cost-users">250 users</output></div>
-<div class="cost-row"><span class="cost-label" id="cost-system-label">Your systems</span><span class="cost-choices" role="group" aria-labelledby="cost-system-label" data-none="no system at all"><label><input type="checkbox" name="cost-system" value="702" data-choice="NetWeaver 7.02"> NetWeaver 7.02</label><label><input type="checkbox" name="cost-system" value="731" data-choice="NetWeaver 7.31"> NetWeaver 7.31</label><label><input type="checkbox" name="cost-system" value="740" data-choice="NetWeaver 7.40"> NetWeaver 7.40</label><label><input type="checkbox" name="cost-system" value="750" data-choice="NetWeaver 7.50"> NetWeaver 7.50</label><label><input type="checkbox" name="cost-system" value="752" data-choice="NetWeaver 7.52"> NetWeaver 7.52</label><label><input type="checkbox" name="cost-system" value="s4-onprem" data-choice="S/4HANA on-premise" checked> S/4HANA on-premise</label><label><input type="checkbox" name="cost-system" value="s4-private" data-choice="S/4HANA Private Cloud"> S/4HANA Private Cloud</label><label><input type="checkbox" name="cost-system" value="btp" data-choice="BTP ABAP Environment"> BTP ABAP Environment</label><label><input type="checkbox" name="cost-system" value="s4-public" data-choice="S/4HANA Public Cloud"> S/4HANA Public Cloud</label></span></div>
-<div class="cost-row"><label for="cost-systems">Systems in the landscape</label><input id="cost-systems" type="range" min="0" max="12" value="2" data-stops="1|2|3|4|5|6|8|10|12|15|20|30|50" data-unit="system|systems"><output for="cost-systems">3 systems</output></div>
-<div class="cost-row"><label for="cost-apps">Apps</label><input id="cost-apps" type="range" min="0" max="10" value="4" data-stops="1|2|3|5|10|20|50|100|200|500|1000" data-unit="app|apps"><output for="cost-apps">10 apps</output></div>
-<div class="cost-row"><label for="cost-developers">Developers</label><input id="cost-developers" type="range" min="0" max="9" value="3" data-stops="1|2|3|5|10|20|50|100|200|500" data-unit="developer|developers"><output for="cost-developers">5 developers</output></div>
-<div class="cost-row"><label for="cost-roundtrips">Load</label><input id="cost-roundtrips" type="range" min="0" max="6" value="3" data-stops="100|1000|10000|100000|1000000|10000000|100000000" data-unit="roundtrip a day|roundtrips a day"><output for="cost-roundtrips">100,000 roundtrips a day</output></div>
-<div class="cost-row"><span class="cost-label" id="cost-support-label">Support</span><span class="cost-choices" role="radiogroup" aria-labelledby="cost-support-label"><label><input type="radio" name="cost-support" value="none" data-choice="No support"> No support</label><label><input type="radio" name="cost-support" value="community" data-choice="Community support" checked> Community support</label></span></div>
-<div class="cost-row"><label for="cost-term">Contract term</label><input id="cost-term" type="range" min="0" max="4" value="2" data-stops="1|2|3|5|10" data-unit="year|years"><output for="cost-term">3 years</output></div>
-<div class="cost-row"><label for="cost-currency">Currency</label><select id="cost-currency" data-currency><option value="EUR" selected>EUR</option><option value="USD">USD</option><option value="GBP">GBP</option><option value="CHF">CHF</option><option value="INR">INR</option><option value="JPY">JPY</option><option value="BRL">BRL</option><option value="AUD">AUD</option></select></div>
-</div>
-<p class="cost-actions"><button type="button" class="cost-calculate" data-calculate="Calculate" data-again="Change the numbers">Calculate</button></p>
-<div class="cost-result" data-result hidden>
-<div class="cost-sheet">
-<div class="cost-line"><span class="cost-what">Framework license<small>MIT, commercial use included</small></span><span class="cost-amount" data-amount>€0</span></div>
-<div class="cost-line"><span class="cost-what">Per-user fee<small><span data-echo="cost-users">250 users</span>, and nobody is counting them</small></span><span class="cost-amount" data-amount>€0</span></div>
-<div class="cost-line"><span class="cost-what">Per-system fee<small><span data-echo="cost-systems">3 systems</span>: abapGit pulls the same repository into each of them</small></span><span class="cost-amount" data-amount>€0</span></div>
-<div class="cost-line"><span class="cost-what">Per-app fee<small><span data-echo="cost-apps">10 apps</span>, each one a class in your own system</small></span><span class="cost-amount" data-amount>€0</span></div>
-<div class="cost-line"><span class="cost-what">Developer seats<small><span data-echo="cost-developers">5 developers</span>, with ADT, the playground and the VS Code extension</small></span><span class="cost-amount" data-amount>€0</span></div>
-<div class="cost-line"><span class="cost-what">Platform<small><span data-echo="cost-system">S/4HANA on-premise</span>: the same class runs on every one of them, from 7.02 up</small></span><span class="cost-amount" data-amount>€0</span></div>
-<div class="cost-line"><span class="cost-what">Runtime<small><span data-echo="cost-roundtrips">100,000 roundtrips a day</span>, every one of them served by your own ABAP stack</small></span><span class="cost-amount" data-amount>€0</span></div>
-<div class="cost-line"><span class="cost-what">Frontend hosting<small>the UI5 your system already ships, and no frontend deployment</small></span><span class="cost-amount" data-amount>€0</span></div>
-<div class="cost-line"><span class="cost-what">Support<small><span data-echo="cost-support">Community support</span>: <a href="https://github.com/abap2UI5/abap2UI5/issues" target="_blank" rel="noopener">GitHub issues</a> and <a href="https://abapgit.slack.com/join/shared_invite/zt-46tqufaht-QlrxTzlDqlx85CWbeUnOqg#/shared-invite/email" target="_blank" rel="noopener">Slack</a> are open to everybody either way</small></span><span class="cost-amount" data-amount>€0</span></div>
-<div class="cost-line"><span class="cost-what">Upgrades<small><span data-echo="cost-term">3 years</span> of releases, each one an abapGit pull</small></span><span class="cost-amount" data-amount>€0</span></div>
-</div>
-<div class="cost-total">
-<div><span class="cost-total-what">Total, over <span data-echo="cost-term">3 years</span></span><output data-total>€0</output></div>
-<div><span class="cost-total-what">Per year</span><output data-total>€0</output></div>
-<div><span class="cost-total-what">Per user, per month</span><output data-total>€0</output></div>
-<p class="cost-total-note">The formula is short: every line is zero, and a sum of zeros is zero - no matter what you clicked before. abap2UI5 is <a href="/docs/resources/license">MIT licensed</a>, commercial use included, and what you build with it is a standard UI5 app served by the ABAP stack you already run.</p>
-</div>
-</div>
-</div>
-
-<div class="cost-after" data-result hidden>
-
-<div class="cost-give">
-
-## Free to use is not the same as free to make
-
-Keep in mind that those zeros were written in somebody's evenings - the release you will pull next month, the answer under your issue, the 7.02 downport nobody asked for. That part of the bill is real; it is just not addressed to you.
-
-And it is payable in a currency you already have. If this page took a line out of a budget, here is what puts a little of it back:
-
-- **Star the repository.** One click on [GitHub](https://github.com/abap2UI5/abap2UI5), and the next visitor sees a project rather than an experiment.
-- **Answer somebody.** One reply under an [issue](https://github.com/abap2UI5/abap2UI5/issues) or in [Slack](https://abapgit.slack.com/join/shared_invite/zt-46tqufaht-QlrxTzlDqlx85CWbeUnOqg#/shared-invite/email) saves somebody else an afternoon of searching.
-- **Report what broke.** An [issue](https://github.com/abap2UI5/abap2UI5/issues) with a class that reproduces the problem is half of the fix already.
-- **Post about it.** A short post that mentions [the page](https://www.linkedin.com/company/abap2ui5) and carries **#abap2UI5** is how the word gets around.
-- **Write it up.** A full article in the [SAP Community](https://community.sap.com/) or on [LinkedIn](https://www.linkedin.com/company/abap2ui5) reaches the next person, and lands in the [references](/resources/references).
-- **Add your company.** One row in [Who Uses abap2UI5?](/resources/who_uses) is what answers *is anybody actually running this?*
-- **Sponsor the work.** [The contributors](/resources/sponsor), and the open-source projects it stands on - the smallest amount is a real one.
-
-Pick the one that is easiest this week. None of it comes with an invoice, and all of it counts.
-
-</div>
-
-</div>
diff --git a/docs/resources/references.md b/docs/resources/references.md
deleted file mode 100644
index 8d58d549..00000000
--- a/docs/resources/references.md
+++ /dev/null
@@ -1,32 +0,0 @@
----
-outline: [2, 4]
----
-# References
-
-## 2026
-- Field Service Management Mobile Logging using abap2UI5 [(Decabase Blog - 22.08.2026)](https://blog.decabase.com/field-service-management-mobile-logging-using-abap2ui5-2c18e4ed455d)
-- UI5 in ABAP Cloud (without RAP or Fiori Elements) [(Decabase Blog - 17.08.2026)](https://blog.decabase.com/ui5-in-abap-cloud-without-rap-or-fiori-elements-4e8a70d961c3)
-- Fiori-type Apps built 100% with ABAP [(Logali Group - 23.04.2026)](https://logaligroup.com/magia-en-el-servidor-local-apps-tipo-fiori-creadas-100-con-codigo-abap/)
-
-## 2025
-- Webinar on Launchpad Integration [(YouTube - 30.07.2025)](https://www.youtube.com/watch?v=t5g3F3PHsbw&list=PLLpkZ_86h4quGSfsjohDHt9CrpjXdeA1P)
-- Featured on SAP Developer News [(YouTube - 21.03.2025)](https://www.youtube.com/watch?v=vKrpkDe2mkU&list=PL6RpkC85SLQAVBSQXN9522_1jNvPavBgg&t=90s)
-
-## 2024
-- Automated Deployment of abap2UI5 [(Blog - 17.12.2024)](https://www.nuveplatform.com/blog/deploy-abap2ui5)
-- Webinar on creating UI5 interfaces from ABAP using abap2UI5 [(YouTube - 12.12.2024)](https://www.youtube.com/watch?v=N2OAdxf7Lng)
-- Highlighted in the Boring Enterprise Nerdletter [(YouTube)](https://www.youtube.com/watch?v=I81z6W_BTIA&t=1010s) [(Newsletter - 11.12.2024)](https://boringenterprisenerds.substack.com/p/72-abap2ui5-aancos-crystal-ball-sapta)
-- Webinar on developing UI5 apps with abap2UI5 [(YouTube - 07.11.2024)](https://www.youtube.com/watch?v=0izPA2xrPPI)
-- Featured on SAP Developer News [(YouTube - 14.06.2024)](https://youtu.be/7n16u-Rx8IY?t=7)
-- Cust&Code Videos featuring abap2UI5 [(YouTube - 20.05.2024)](https://www.youtube.com/watch?v=SD1vIt_ty0k)
-- Running abap2UI5 Backend in Browser [(LinkedIn - 02.04.2024)](https://www.linkedin.com/pulse/running-abap2ui5-backend-browser-lars-hvam-petersen-l8zff/?trackingId=4mhMb1v%2FSoa8SmDSiuCEpg%3D%3D)
-- Highlighted in the Boring Enterprise Nerdcast [(YouTube - 29.01.2024)](https://youtu.be/svDZKFBvqR8?t=1050)
-
-## 2023
-- Featured on SAP Developer News [(YouTube - 15.12.2023)](https://www.youtube.com/watch?v=CfH9L03WUCg&t=350s)
-- Join the Advent of Code 2023 with abap2UI5 [(SAP Community - 27.11.2023)](https://blogs.sap.com/2023/11/27/preparing-for-advent-of-code-2023/)
-- Showcased at SAP TechEd 2023 [(YouTube - 02.11.2023)](https://www.youtube.com/watch?v=kLbF0ooStZs&t=3052s)
-- Part of the SAP Developer Code Challenge [(SAP Community - 17.05.2023)](https://groups.community.sap.com/t5/application-development/sap-developer-code-challenge-open-source-abap-week-2/m-p/260727#M1372)
-- Highlighted in the Boring Enterprise Nerdletter [(YouTube)](https://www.youtube.com/watch?v=G62exySitCo&list=PLlxj8-g1r2GlVYXVQnnV5izKwKtEn6KIp&t=1008s) [(Newsletter - 08.03.2023)](https://boringenterprisenerds.substack.com/p/34-abap2ui5-sap-cva-burnout-c2c-shortwave)
-- Featured on SAP Developer News [(YouTube - 26.01.2023)](https://www.youtube.com/watch?v=6BDK55xYttM)
-- See abap2UI5 on ABAP Open Source Projects [(dotabap.org)](https://dotabap.org/)
diff --git a/docs/resources/who_uses.md b/docs/resources/who_uses.md
deleted file mode 100644
index b757d610..00000000
--- a/docs/resources/who_uses.md
+++ /dev/null
@@ -1,31 +0,0 @@
----
-outline: [2, 4]
-description: Companies, workshops and integrations that use abap2UI5, with the system release and the use case, and how to add your own.
----
-# Who Uses abap2UI5?
-
-We'd love to hear how you use abap2UI5. Whether in customer projects, integrations, workshops, open-source contributions, or any other initiative, sharing your scenario can inspire others to try the project and help the abap2UI5 community grow.
-
-## Customer Projects
-**Does your company use abap2UI5?** <br>
-Showcase how abap2UI5 apps reshape real-world workflows. Add your scenario here:
-
-|  Company | System | Use Case |
-| ------------------- | ------------- | ------------- |
-| [Emineo](https://emineo.ch/) | ABAP 7.57  | Apps for EWM and PP, running on desktop and mobile devices |
-| [Swiss Krono](https://www.swisskrono.com/) | ABAP 7.55  | Apps for EWM, running on mobile devices |
-
-## Integrations and Workshops
-**Do you host workshops, build integrations, or use abap2UI5 in creative ways?** <br>
-Inspire the community by sharing your initiatives so others can learn from your contributions:
-
-|  Company | Description |
-| ------------- | ------------- |
-| [Nuve Platform](https://www.nuveplatform.com) | On-demand SAP systems with automated abap2UI5 setups |
-| [Logali Group](https://logaligroup.com) | Webinars and certifications for abap2UI5 |
-
-<br>
-
-_Ready to showcase your project? Add to this list directly or reach out at <contact@abap2UI5.org>. We'd love to hear what you're building._
-
-Thank you for being part of the abap2UI5 community! ❤️
diff --git a/scripts/build-site.mjs b/scripts/build-site.mjs
index 7b9ce0de..2c942f7a 100644
--- a/scripts/build-site.mjs
+++ b/scripts/build-site.mjs
@@ -323,10 +323,6 @@ const BAR_DOCS = withRelease(marked('data-site="docs"'));
 /* The ids the bar brings with it, which no heading of a page may also take. */
 const BAR_IDS = new Set([...BAR_DOCS.matchAll(/\bid="([^"]+)"/g)].map((m) => m[1]));
 const BAR_HOME = withRelease(marked(`href="${HOME}"`));
-/* The bar with no section marked: the Evaluate page is neither the front
-   door nor a chapter, and a bar that said "Documentation" in bold over it
-   would put the reader the page is written for into the manual. */
-const BAR_PLAIN = withRelease(BAR);
 
 /* THE OTHER HALF OF THE PAIR IS THE BORROWED MARKUP'S, so it is checked rather
  * than assumed. `data-site` above says which page to come back to; `data-back`,
@@ -989,50 +985,6 @@ const home = ({ body, fm, page }) => {
 </main>`;
 };
 
-/* ---- the landing page ------------------------------------------------
- *
- * The one chapter drawn like the front door: `layout: landing` in the
- * frontmatter (docs/evaluate.md says why). The hero's name, tagline, buttons
- * and note come from the frontmatter the way the front door's do; its H1 is
- * the page's own, taken out of the body and printed once in the hero; the
- * image is a screenshot rather than a mark, so it is drawn at the width a
- * screenshot needs. The H2 sections become bands (no hinge, so no cards),
- * the tiles stand after the last of them, and the figures under the hero. */
-const landing = ({ body, fm, page }) => {
-  const h = fm.hero || {};
-  const img = h.image || {};
-  const h1 = (body.match(/<h1[^>]*>([\s\S]*?)<\/h1>/) || [, ''])[1].replace(/<[^>]+>/g, '');
-  const rest = body.replace(/<h1[^>]*>[\s\S]*?<\/h1>\s*/, '');
-  const shot = img.src ? (() => {
-    const at = BASE + String(img.src).replace(/^\//, '');
-    const box = measure(path.join(DOCS, 'public', at.slice(BASE.length)));
-    const size = box && box.w ? ` width="${box.w}" height="${box.h}"` : '';
-    return `<div class="hero-image hero-shot"><img src="${esc(at)}" alt="${esc(img.alt || '')}"${size} decoding="async" fetchpriority="high"></div>`;
-  })() : '';
-  return `<main class="home landing" id="main-content" tabindex="-1">
-  <section class="hero">
-    <div class="hero-main">
-      ${h.name ? `<p class="hero-name">${esc(h.name)}</p>` : ''}
-      <h1 class="hero-text">${h1}</h1>
-      ${h.tagline ? `<p class="hero-tagline">${esc(h.tagline)}</p>` : ''}
-      <div class="hero-actions">${(h.actions || []).map((a) => `
-        <a class="hero-action ${a.theme === 'brand' ? 'primary' : 'plain'}" href="${esc(linkOf(a.link))}"${a.target ? ` target="${esc(a.target)}"` : ''}>${esc(a.text)}</a>`).join('')}
-      </div>
-      ${h.note ? `<p class="hero-note">${esc(h.note)}</p>` : ''}
-    </div>
-    ${shot}
-  </section>
-  ${factsLine('hero-facts')}
-  <div class="vp-doc bands">${bands(rest)}<section class="tiles">${(fm.features || []).map(tile).join('')}
-  </section></div>
-  <div class="doc-foot">
-    <a class="edit" href="${esc((config.themeConfig.editLink?.pattern || '').replace(':path', page))}"
-       target="_blank" rel="noopener">${esc(config.themeConfig.editLink?.text || 'Edit this page on GitHub')} ↗</a>
-    <span class="updated">Last updated: <time datetime="${lastTouched(page)}">${lastTouched(page)}</time></span>
-  </div>
-</main>`;
-};
-
 /* ---- the ABAP, tokenised by the file the catalogue tokenises with -------
  *
  * Not "the same colours" - the same PROGRAM. `abap-highlight.mjs` is what
@@ -1415,7 +1367,6 @@ for (const page of pages) {
   const name = fm.title || titleOf(src, page);
   const route = routeOf(page);
   const isHome = fm.layout === 'home';
-  const isLanding = fm.layout === 'landing';
   /* The theme's own title template, and its own rule for the preview: a
      chapter previews as itself, the front door as the project. A name two
      chapters share carries the section that tells them apart. */
@@ -1448,13 +1399,13 @@ for (const page of pages) {
          sentence cannot be taken from. */
       description: isHome ? (fm.description || SITE_DESC) : (describe(src) || SITE_DESC),
     }),
-    bar: isHome ? BAR_HOME : isLanding ? BAR_PLAIN : BAR_DOCS,
-    main: isHome ? home({ body, fm, page }) : isLanding ? landing({ body, fm, page }) : chapter({ body, page, route }),
+    bar: isHome ? BAR_HOME : BAR_DOCS,
+    main: isHome ? home({ body, fm, page }) : chapter({ body, page, route }),
     /* The front door sets its "More on …" lines in italic, in the first
        screen; unpreloaded, the italic arrived a round trip after the roman
        and those four lines were drawn twice. A chapter has italic here and
        there and fetches it when it needs it. */
-    italic: isHome || isLanding,
+    italic: isHome,
   });
 
   const to = path.join(OUT, 'docs', page.replace(/\.md$/, '.html'));
diff --git a/scripts/lib/cross-site.mjs b/scripts/lib/cross-site.mjs
index db49fea6..9453d368 100644
--- a/scripts/lib/cross-site.mjs
+++ b/scripts/lib/cross-site.mjs
@@ -64,6 +64,7 @@ export const NEIGHBOURS = [
   '/linter/',               // the linter's rule reference
   '/layout-editor/',        // the layout editor, published by abap2UI5/layout-editor's pages workflow
   '/web-abap2UI5-build/',   // a live build of the frontend, credited on Sponsor
+  '/test-docs/',            // abap2UI5 for decision makers, published by abap2UI5/test-docs
 ];
 
 /** What a retired deployment was replaced BY, so the error can say it. */
diff --git a/scripts/lib/facts.mjs b/scripts/lib/facts.mjs
index 32340f50..08387472 100644
--- a/scripts/lib/facts.mjs
+++ b/scripts/lib/facts.mjs
@@ -1,5 +1,5 @@
 /*
- * facts — the counted figures the front door and the Evaluate page print.
+ * facts — the counted figures the front door prints.
  *
  * This repository owns no number about the framework, and keeps none by hand:
  * the one page that carried four figures of its own (`resources/samples.md`)
diff --git a/scripts/site-css/docs.css b/scripts/site-css/docs.css
index c34bc86b..77269b4e 100644
--- a/scripts/site-css/docs.css
+++ b/scripts/site-css/docs.css
@@ -806,30 +806,13 @@ html { scroll-padding-top: 62px; }
    has always drawn it. */
 .hero-image { flex: 1 1 auto; min-width: 0; display: flex; justify-content: center; transform: translate(-32px, -32px); }
 .hero-image img { display: block; width: 200px; height: auto; border: 0; border-radius: 0; }
-/* The landing page's hero carries a screenshot where the front door has the
-   mark: drawn at the width a screenshot needs, framed like the ones in the
-   chapters, and not shifted up and left the way the mark is. */
-.landing .hero-image.hero-shot { transform: none; justify-content: flex-end; padding-left: 32px; }
-.landing .hero-image.hero-shot img {
-  width: 100%; max-width: 520px; height: auto;
-  border: 1px solid var(--line); border-radius: 6px;
-}
-/* Its tables are tables - a header row, cells that wrap - not the front
-   door's two-column fact sheet, which is what `.home table` is styled as. */
-.landing .vp-doc table { max-width: none; }
-.landing .vp-doc table thead { display: table-header-group; }
-.landing .vp-doc table td:first-child { width: auto; white-space: normal; }
-/* The bands follow one another as sections of one argument, so each one
-   after the first opens on the hairline the H2 carries and a little air. */
-.landing .band + .band { padding-top: 8px; }
-.landing .bands .tiles { margin-top: 8px; }
-
 /* The three things to do next - build a first app, find a sample, take one
    to production. Under the example rather than under the hero
    (build-site.mjs places them), so the row is one band of the grid below
    and takes its spacing from the grid's row gap. */
-/* Four tiles, one per task - build, find, ship, evaluate - and the fourth is
-   the one for the reader who builds nothing. Two by two under 1100px, where
+/* Four tiles, one per task - build, find, ship, and hand the page for the
+   decision maker over - the fourth is the one for the reader who builds
+   nothing. Two by two under 1100px, where
    four 13px details in a row stop being readable. */
 .tiles {
   display: grid; grid-template-columns: repeat(4, minmax(0, 1fr)); gap: 16px;
@@ -1016,9 +999,6 @@ html { scroll-padding-top: 62px; }
 @media (max-width: 860px) {
   .hero { display: block; }
   .hero-image { display: none; }
-  /* ...but the landing page's screenshot stays, under the text: it is the
-     one picture the reader of that page gets. */
-  .landing .hero-image.hero-shot { display: flex; padding: 24px 0 0; justify-content: flex-start; }
   .tiles { grid-template-columns: minmax(0, 1fr); }
 }
 
@@ -1287,124 +1267,6 @@ html { scrollbar-gutter: stable; }
   p, li, blockquote { orphans: 3; widows: 3; }
 }
 
-/* ---- the cost calculator ----------------------------------------------
- *
- * resources/cost_calculator: a sheet of sliders whose every line comes to
- * the same number. Plain form controls in the page's own type, the accent
- * on the slider's thumb and on the total, and nothing that needs the
- * script - the page reads the same with the sliders dead. */
-.cost { margin: 20px 0; }
-.cost-row {
-  display: grid; grid-template-columns: minmax(0, 11em) minmax(0, 1fr) minmax(0, 13em);
-  gap: 6px 16px; align-items: center;
-  padding: 10px 0; border-bottom: 1px solid var(--line); font-size: 14px; line-height: 1.55;
-}
-.cost-row label { font-weight: 600; }
-.cost-row input[type="range"] { width: 100%; margin: 0; accent-color: var(--accent); }
-.cost-row output { text-align: right; font-variant-numeric: tabular-nums; color: var(--fg-dim); }
-.cost-row select {
-  grid-column: 2 / -1; justify-self: end; font: inherit; padding: 4px 8px;
-  border: 1px solid var(--line); border-radius: 6px; background: var(--bg); color: inherit;
-}
-/* A choice rather than a scale: radio buttons or checkboxes, across the
-   columns the slider and its readout would take. The links that used to sit
-   beside them are down in the sheet now - an input row is for choosing, and a
-   link in one is a way out of the page before it has said anything. */
-.cost-row .cost-label { font-weight: 600; }
-.cost-row .cost-choices { grid-column: 2 / -1; display: flex; flex-wrap: wrap; align-items: center; gap: 6px 8px; }
-.cost-row .cost-choices label { display: inline-flex; align-items: center; gap: 6px; margin-right: 12px; font-weight: 400; }
-.cost-row .cost-choices input[type="radio"],
-.cost-row .cost-choices input[type="checkbox"] { margin: 0; accent-color: var(--accent); }
-/* The sheet is what the button hands out: hidden until Calculate is pressed,
-   the inputs greyed while it shows, and the button then offers a new round. */
-.cost-actions { margin: 16px 0; }
-.cost-calculate {
-  font: inherit; font-size: 13px; font-weight: 600; line-height: 34px; padding: 0 16px;
-  border: 1px solid transparent; border-radius: 6px; cursor: pointer;
-  background: var(--accent); color: var(--accent-fg, #fff);
-}
-.cost-calculate:hover { filter: brightness(1.08); }
-.cost-calculate:disabled { cursor: progress; opacity: .7; }
-.cost-inputs[data-locked] .cost-row { opacity: .5; }
-/* ON A PHONE A ROW IS TWO LINES: the label with its readout on the first and
-   the slider the whole width of the second - the shape a phone's own settings
-   give a slider - where the readout used to take a third line of its own. A
-   choice's boxes go under their label rather than beside it: nine systems in
-   the column beside "Your systems" left the label wrapped to a word a line and
-   the boxes to a two-word column. The button is the row's whole width, and
-   the height of a finger. */
-@media (max-width: 620px) {
-  .cost-row { grid-template-columns: minmax(0, 1fr) auto; }
-  .cost-row output { grid-column: 2; grid-row: 1; }
-  .cost-row input[type="range"] { grid-column: 1 / -1; grid-row: 2; }
-  .cost-row .cost-choices { grid-column: 1 / -1; }
-  .cost-calculate { width: 100%; line-height: 44px; }
-}
-/* A thumb rather than a pointer: each box the size of a target and the word
-   beside it a row the height of one, the slider a band a finger can land on,
-   and the currency list a size iOS does not zoom the page in on - a control
-   set under 16px is one it magnifies on focus and leaves magnified. Nothing
-   here moves under a mouse. */
-@media (pointer: coarse) {
-  .cost-row .cost-choices label { min-height: 32px; }
-  .cost-row .cost-choices input[type="radio"],
-  .cost-row .cost-choices input[type="checkbox"] { width: 18px; height: 18px; }
-  .cost-row input[type="range"] { height: 32px; }
-  .cost-row select { font-size: 16px; }
-}
-.cost-sheet { margin: 20px 0 0; padding: 0 16px; border: 1px solid var(--line); border-radius: 8px; background: var(--bg-sunken); }
-.cost-line {
-  display: flex; justify-content: space-between; align-items: baseline; gap: 16px;
-  padding: 10px 0; border-bottom: 1px solid var(--line); font-size: 14px; line-height: 1.55;
-}
-.cost-line:last-child { border-bottom: 0; }
-.cost-line small { display: block; font-size: 13px; color: var(--fg-dim); }
-.cost-amount { font-weight: 600; font-variant-numeric: tabular-nums; white-space: nowrap; }
-.cost-total {
-  display: grid; grid-template-columns: repeat(3, minmax(0, 1fr)); gap: 16px;
-  margin: 16px 0 24px; padding: 16px 20px; border: 1px solid var(--accent); border-radius: 8px;
-}
-.cost-total > div { display: flex; flex-direction: column; gap: 4px; font-size: 13px; color: var(--fg-dim); }
-.cost-total output { font-size: 28px; line-height: 1.15; font-weight: 600; color: var(--accent); font-variant-numeric: tabular-nums; }
-.cost-total > div:first-child output { font-size: 40px; }
-/* The one line the sheet cannot total. The answer above it is ten zeros, so
-   the way to say that somebody still paid for them is a panel of its own -
-   the accent border the total carries, on the quieter background, so it reads
-   as the other half of the answer rather than as a footnote or a plea. The
-   four ways are a list without markers, two columns where there is room, each
-   led by what it is: three of them cost an evening and one costs money, and
-   they are in that order on purpose. */
-.cost-give {
-  margin: 28px 0 0; padding: 4px 24px 20px; border: 1px solid var(--accent);
-  border-radius: 8px; background: var(--bg-sunken);
-}
-.cost-give h2 { margin: 16px 0 10px; padding: 0; border: 0; }
-.cost-give p { font-size: 14px; }
-.cost-give > :last-child { margin-bottom: 0; }
-/* Named down to the element, because both themes give a list in an article a
-   marker and an indent of its own. */
-.cost-give ul {
-  display: grid; grid-template-columns: repeat(2, minmax(0, 1fr)); gap: 12px 24px;
-  margin: 16px 0; padding: 0; list-style: none;
-  font-size: 13px; line-height: 1.6; color: var(--fg-dim);
-}
-.cost-give ul li { margin: 0; padding: 0; }
-/* The lead of a way is a line of its own - and only the lead: a strong later
-   in the sentence (the tag a post carries) is a word inside it. */
-.cost-give ul li strong:first-child { display: block; }
-.cost-give ul li strong { color: var(--fg); font-weight: 600; }
-@media (max-width: 620px) { .cost-give ul { grid-template-columns: 1fr; } }
-/* The note is the sheet's last line rather than a paragraph under it: the
-   three figures answer the question, and the sentence that says why they are
-   all the same character belongs inside the same border. It spans the grid,
-   sits on a hairline under the figures, and is the size of a caption - a note
-   on the total, not a fourth number. */
-.cost-total-note {
-  grid-column: 1 / -1; margin: 4px 0 0; padding-top: 14px;
-  border-top: 1px solid var(--line); font-size: 13px; line-height: 1.6; color: var(--fg-dim);
-}
-@media (max-width: 620px) { .cost-total { grid-template-columns: 1fr; } }
-
 /* ---- the front door's example folds on a phone --------------------------
  *
  * The example is 137 lines, and on 390px of width that was 4,000 of the
diff --git a/scripts/site-js/site.js b/scripts/site-js/site.js
index 3f524704..d5088bd1 100644
--- a/scripts/site-js/site.js
+++ b/scripts/site-js/site.js
@@ -14,7 +14,6 @@
 import { setUpPlayground } from './playground.js';
 import { setUpCodeLines, watchCodeLines } from './code-lines.js';
 import { markDirective, setUpLinkToSelection } from './link-to-selection.js';
-import { setUpCostCalculator } from './cost-calculator.js';
 import { entryOf, forgetOnReload, handOff, lastVisited, rememberHere, rememberScroll, restoreScroll, takeHandoff } from './site-memory.js';
 
 /* ---- a refresh starts over ---------------------------------------------
@@ -51,10 +50,6 @@ forgetOnReload([SECTIONS_KEY, SEARCH_KEY]);
 setUpPlayground();
 setUpLinkToSelection();
 
-/* The cost calculator's sliders and the sheet under them (cost-calculator.js):
-   two delegated listeners, and nothing to do on any page but that one. */
-setUpCostCalculator();
-
 /* A number beside every line of every listing, and an address for it - #B2L42
    is line 42 of the second listing on the page. `watchCodeLines` hangs the
    document's listeners, `setUpCodeLines` numbers what is on this page. */
diff --git a/test/cost-calculator.test.mjs b/test/cost-calculator.test.mjs
deleted file mode 100644
index 690bc409..00000000
--- a/test/cost-calculator.test.mjs
+++ /dev/null
@@ -1,217 +0,0 @@
-/*
- * The cost calculator (resources/cost_calculator): a sheet of sliders whose
- * every line comes to zero, because that is what abap2UI5 costs.
- *
- * Two things are worth holding. The arithmetic - theme/cost-model.js, the
- * half with no DOM in it - so that the joke stays true in code: every line
- * is zero and so is the sum, for any setting of any slider. And the page
- * against the script: the readouts and the amounts are written into the
- * markup, so what the button reveals is what the page already says, and a
- * slider whose written readout is not what the script would write for its
- * starting position would flicker to the truth on load.
- *
- *   npm test
- */
-import { test } from 'node:test';
-import assert from 'node:assert/strict';
-import { readFileSync } from 'node:fs';
-import { fileURLToPath } from 'node:url';
-import { dirname, join } from 'node:path';
-import { amount, line, listed, reading, stopsOf, total } from '../docs/.vitepress/theme/cost-model.js';
-
-const ROOT = join(dirname(fileURLToPath(import.meta.url)), '..');
-const PAGE = readFileSync(join(ROOT, 'docs', 'resources', 'cost_calculator.md'), 'utf8');
-const HOME = readFileSync(join(ROOT, 'docs', 'index.md'), 'utf8');
-
-test('a reading is the stop at the position, with its unit', () => {
-  assert.equal(reading(stopsOf('1|5|10'), 0, 'user|users'), '1 user');
-  assert.equal(reading(stopsOf('1|5|10000'), 2, 'user|users'), '10,000 users');
-  assert.equal(reading(stopsOf('1|5|10000'), '2', 'user|users'), '10,000 users', 'a slider\'s value is a string');
-  assert.equal(reading(stopsOf('Community|Premium'), 1), 'Premium');
-  assert.equal(reading(stopsOf('1|5'), 9, 'year|years'), '5 years', 'past the end is the end');
-  assert.equal(reading(stopsOf('1|5'), -1, 'year|years'), '1 year');
-  assert.equal(reading(stopsOf('1|5'), 'x'), '1');
-  assert.equal(reading(stopsOf(''), 3), '');
-});
-
-test('choices read out as a list', () => {
-  assert.equal(listed([], 'no system at all'), 'no system at all');
-  assert.equal(listed(['S/4HANA on-premise']), 'S/4HANA on-premise');
-  assert.equal(listed(['NetWeaver 7.50', 'BTP ABAP Environment']), 'NetWeaver 7.50 and BTP ABAP Environment');
-  assert.equal(listed(['A', 'B', 'C']), 'A, B and C');
-});
-
-test('an amount is the currency\'s own zero', () => {
-  assert.equal(amount(0, 'EUR'), '€0');
-  assert.equal(amount(0, 'USD'), '$0');
-  assert.equal(amount(0, 'JPY'), '¥0');
-  /* A code and its number are joined with a no-break space, so they never
-     part at a line's end. */
-  assert.equal(amount(0, 'CHF'), 'CHF\u00a00');
-  assert.equal(amount(0, 'XYZ'), 'XYZ\u00a00', 'a code the runtime does not know still reads');
-});
-
-test('every line is zero, and so is the sum, whatever the sliders say', () => {
-  assert.equal(line('250,000 users'), 0);
-  assert.equal(line(), 0);
-  assert.equal(total({}), 0);
-  assert.equal(total({ users: 250000, systems: 50, support: 'Enterprise Plus', term: 10 }), 0);
-  for (let i = 0; i < 100; i++) {
-    assert.equal(total({ a: Math.random() * 1e9, b: -1, c: Infinity, d: 'many', e: NaN }), 0);
-  }
-});
-
-test('the page and the script agree on what every slider says at load', () => {
-  const sliders = [...PAGE.matchAll(
-    /<input id="([^"]+)" type="range" min="(\d+)" max="(\d+)" value="(\d+)" data-stops="([^"]+)"(?: data-unit="([^"]*)")?>/g,
-  )];
-  assert.ok(sliders.length >= 6, `${sliders.length} sliders`);
-  const ids = new Set();
-  for (const [, id, min, max, value, stops, unit] of sliders) {
-    ids.add(id);
-    const all = stopsOf(stops);
-    assert.equal(Number(min), 0, id);
-    assert.equal(Number(max), all.length - 1, `${id}: max is the last stop`);
-    assert.ok(Number(value) <= Number(max), `${id}: starts on a stop`);
-    const said = reading(all, Number(value), unit || '');
-    const out = PAGE.match(new RegExp(`<output for="${id}">([^<]*)</output>`));
-    assert.ok(out, `${id} has a readout`);
-    assert.equal(out[1], said, `${id}: the readout at load is what the script would write`);
-    for (const echo of PAGE.matchAll(new RegExp(`<span data-echo="${id}">([^<]*)</span>`, 'g'))) {
-      assert.equal(echo[1], said, `${id}: an echo at load is what the script would write`);
-    }
-  }
-  /* A choice made with radio buttons or checkboxes: what is ticked at load,
-     read out as a list, is what the sheet echoes - and the group's name is an
-     echo target like a slider's id. */
-  const groups = new Map();
-  for (const [, kind, name, choice, on] of PAGE.matchAll(/<input type="(radio|checkbox)" name="([^"]+)" value="[^"]+" data-choice="([^"]+)"( checked)?>/g)) {
-    if (!groups.has(name)) groups.set(name, { kind, chosen: [] });
-    assert.equal(groups.get(name).kind, kind, `${name} is one kind of choice`);
-    if (on) groups.get(name).chosen.push(choice);
-  }
-  assert.ok(groups.size >= 2, `${groups.size} groups`);
-  for (const [name, { kind, chosen }] of groups) {
-    ids.add(name);
-    if (kind === 'radio') assert.equal(chosen.length, 1, `${name}: exactly one choice is made at load`);
-    const none = PAGE.match(new RegExp(`aria-labelledby="${name}-label" data-none="([^"]*)"`))?.[1];
-    for (const echo of PAGE.matchAll(new RegExp(`<span data-echo="${name}">([^<]*)</span>`, 'g'))) {
-      assert.equal(echo[1], listed(chosen, none), `${name}: the echo at load is what is ticked at load`);
-    }
-  }
-  for (const [, id] of PAGE.matchAll(/data-echo="([^"]+)"/g)) assert.ok(ids.has(id), `an echo of ${id} has a slider or a choice`);
-  for (const [, id] of PAGE.matchAll(/<label for="([^"]+)"/g)) {
-    assert.match(PAGE, new RegExp(`<(?:input|select) id="${id}"`), `the label ${id} names a control`);
-  }
-});
-
-test('every amount on the page is the chosen currency\'s zero', () => {
-  const amounts = [...PAGE.matchAll(/<(?:span|output) [^>]*data-(?:amount|total)[^>]*>([^<]*)</g)].map((m) => m[1]);
-  assert.ok(amounts.length >= 10, `${amounts.length} amounts`);
-  const currency = PAGE.match(/<option value="([A-Z]{3})" selected>/)[1];
-  for (const a of amounts) assert.equal(a, amount(0, currency));
-});
-
-test('the sheet waits for the button', () => {
-  assert.match(PAGE, /<button type="button" class="cost-calculate" data-calculate="Calculate" data-again="[^"]+">Calculate<\/button>/);
-  assert.match(PAGE, /<div class="cost-result" data-result hidden>/, 'the sheet is hidden until Calculate is pressed');
-  assert.ok(PAGE.indexOf('<div class="cost-inputs">') < PAGE.indexOf('data-calculate='), 'the inputs come first');
-  assert.ok(PAGE.indexOf('data-calculate=') < PAGE.indexOf('data-result'), 'then the button, then the sheet');
-  /* The words under the calculator wait with it: the formula and the one line
-     that is not zero are markdown inside a wrapper that carries the same mark,
-     with blank lines around the markdown so the renderer still renders it. */
-  const after = PAGE.indexOf('<div class="cost-after" data-result hidden>\n\n');
-  assert.ok(after > PAGE.lastIndexOf('<div class="cost-result"'), 'the words under the sheet wait for the button too');
-  assert.ok(PAGE.trimEnd().endsWith('\n\n</div>'), 'and the wrapper closes after the last of them');
-  assert.ok(PAGE.indexOf('\n## Free to use is not the same as free to make', after) > after, 'the section is markdown inside it, heading and all');
-});
-
-/* What the sheet carries that the inputs deliberately do not: the links to the
-   issue tracker and to Slack. They sat in the support row, which is a way out
-   of the page in the middle of filling it in, and they belong on the Support
-   line of the answer instead.
-
-   There was a list under the total here too - what the zeros get you - on the
-   grounds that ten identical characters are a thin reward for nine sliders.
-   It was taken out again: the sentences under the sheet say the same thing in
-   the page's own voice, and the list said it twice. Its rules went out of both
-   stylesheets with it. */
-test('the links wait for the sheet, and lead out of it only there', () => {
-  const inputs = PAGE.slice(PAGE.indexOf('<div class="cost-inputs">'), PAGE.indexOf('data-calculate='));
-  assert.doesNotMatch(inputs, /<a /, 'nothing leads out of the page while it is being filled in');
-  const sheet = PAGE.slice(PAGE.indexOf('<div class="cost-result"'), PAGE.indexOf('<div class="cost-after"'));
-  assert.match(sheet, /Support<small>[^<]*<span data-echo="cost-support">/, 'the sheet has a support line');
-  assert.match(sheet, /github\.com\/abap2UI5\/abap2UI5\/issues/, 'and the issue tracker is on it');
-  assert.match(sheet, /abapgit\.slack\.com\/join\/shared_invite/, 'and Slack');
-  assert.doesNotMatch(sheet, /cost-perks|<\/ul>/, 'and nothing is left of the list that used to close the sheet');
-});
-
-/* The page answers in zeros, so the section that says somebody still paid for
-   them is a panel rather than a paragraph after the sheet - and what it asks
-   for is mostly not money: four ways, three of which cost an evening. The
-   ways are pinned because the ONE that takes money is the one a page like
-   this drifts towards over time, and the other three are the point. */
-test('the front door\'s cost card leads here, and the page ends on the four ways', () => {
-  assert.match(HOME, /\]\(\/resources\/cost_calculator\)/, 'the cost card links the calculator');
-  const last = PAGE.slice(PAGE.lastIndexOf('\n## '));
-  assert.ok(PAGE.indexOf('<div class="cost-give">') < PAGE.lastIndexOf('\n## '), 'the section stands in a panel of its own');
-  assert.match(last, /\]\(\/resources\/sponsor\)/, 'the last section is the one that asks');
-  assert.match(last, /open-source/i);
-  const ways = (last.match(/^- \*\*/gm) || []);
-  assert.equal(ways.length, 7, 'seven ways, each led by what it is and each one thing to do');
-  for (const way of last.split('\n').filter((l) => l.startsWith('- **'))) {
-    assert.match(way, /\]\(/, `${way.slice(0, 28)}… says where to do it`);
-  }
-  /* Every way says where to do it, and the four places are not
-     interchangeable: two to answer somebody in, two to say it out loud. And
-     every way carries a link, because a way without one is a wish. */
-  assert.match(last, /abapgit\.slack\.com\/join\/shared_invite/, 'Slack');
-  assert.match(last, /github\.com\/abap2UI5\/abap2UI5\/issues/, 'the issue tracker');
-  assert.match(last, /linkedin\.com\/company\/abap2ui5/, 'the project page a post can mention');
-  assert.match(last, /community\.sap\.com/, 'the SAP Community');
-  assert.match(last, /#abap2UI5/, 'and the tag that collects those posts');
-  assert.match(last, /\]\(\/resources\/references\)/, 'where what is written about it lands');
-  assert.match(last, /\]\(\/resources\/who_uses\)/, 'and the list a company can put itself on');
-  /* An intro that counts the ways goes stale the moment one is added or
-     taken out - which is exactly how it went stale. The count was then taken
-     out of the intro altogether, which is the other way of never being
-     wrong; so the number is held to the list only while the intro states
-     one. All but one cost an evening; that one is the money. */
-  const said = last.match(/- (\w+) that cost an evening, and one that costs money/);
-  const words = ['zero', 'one', 'two', 'three', 'four', 'five', 'six', 'seven',
-                 'eight', 'nine', 'ten', 'eleven', 'twelve'];
-  if (said) {
-    assert.equal(said[1], words[ways.length - 1], `${ways.length} ways, so the intro says ${words[ways.length - 1]} plus the one that costs money`);
-  }
-});
-
-/* The stylesheet is written twice - scripts/site-css/docs.css for the site the
-   build renders, docs/.vitepress/theme/style.css for VitePress's second
-   opinion - and the calculator's rules are the same text in both, from the
-   grid a row is down to the two lines it becomes on a phone. One edited
-   without the other is a page that is right in one build and wrong in the
-   other. */
-test('the two stylesheets carry one calculator, its phone rules included', () => {
-  const block = (file) => {
-    const css = readFileSync(join(ROOT, file), 'utf8');
-    const from = css.indexOf('.cost { margin: 20px 0; }');
-    const to = css.indexOf('.cost-total { grid-template-columns: 1fr; } }', from);
-    assert.ok(from > 0 && to > from, `${file} carries the calculator`);
-    return css.slice(from, to);
-  };
-  const site = block('scripts/site-css/docs.css');
-  assert.equal(block('docs/.vitepress/theme/style.css'), site, 'the theme carries the same calculator');
-  /* On a phone a row is the label with its readout, then the slider across the
-     whole width; a choice's boxes go under their label; the button is the
-     width of the row and the height of a finger. */
-  const phone = site.slice(site.indexOf('@media (max-width: 620px) {'));
-  assert.match(phone, /\.cost-row output \{ grid-column: 2; grid-row: 1; \}/);
-  assert.match(phone, /\.cost-row input\[type="range"\] \{ grid-column: 1 \/ -1; grid-row: 2; \}/);
-  assert.match(phone, /\.cost-row \.cost-choices \{ grid-column: 1 \/ -1; \}/);
-  assert.match(phone, /\.cost-calculate \{ width: 100%; line-height: 44px; \}/);
-  /* Under a thumb the boxes are the size of a target, and the currency list is
-     the one size iOS does not zoom the page in on. */
-  const thumb = site.slice(site.indexOf('@media (pointer: coarse) {'));
-  assert.match(thumb, /input\[type="checkbox"\] \{ width: 18px; height: 18px; \}/);
-  assert.match(thumb, /\.cost-row select \{ font-size: 16px; \}/);
-});