Name the shared pages in each language and check the spellings on every build

Context and Problem Statement

The names are settled: the units in capitals, lowercase or, when necessary, with an initial capital; AKIoT with its lowercase o; SOLFARMA as one word (brand-architecture.md). What was open is everything around them: how AKRIBIS One is written in text, the identifiers in files, CSS and URLs, and the words of the addresses every site has. Today one site writes AKLEIA and akleia on the same page, three set “AKRIBIS · One” in type, one writes “Parte de AKRIBIS”, and the only site that translates its sections keeps Spanish slugs for its legal and thank-you pages under /en/ and /pt/. How is each name written in each place, what are the shared pages called in each language, and how is a misspelling caught before it is published?

Decision Drivers

Criteria 1 (trust), 2 (one family), 7 (three languages) and 9 (generated and tested) of ADR-0009; ADR-0005 (the endorsement line); ADR-0023 (the pages every site has); ADR-0025 (the URL grammar).

Considered Options

• The slugs as data in the anatomy and the spelling rules as a list the checker runs over every page’s text
• A written style guide, applied in review
• Slugs chosen by each site

Decision Outcome

Proposed: the first option.

• In text. The settled forms stand: AKRIBIS, AKURALAB, AKUTEMP, AKRIMET, SOLFARMA, AKLEIA, AKZOTEC, SINGULAR4, AKIoT in capitals in running text, headings and buttons; all lowercase only where the mark is lowercase or a design asks for it; an initial capital only when the capitals would shout (a legal text, a long list). The names are the same in the three languages. The parent is AKRIBIS Group; the offer is AKRIBIS One, two words, a capital O, and never with the lockup’s middle dot, which belongs to the mark: “AKRIBIS · One” in type is a redrawn mark. The endorsement is “Una unidad de AKRIBIS One” (ADR-0005) and its two proposed translations, never “Parte de”.
• Identifiers. The brand id is lowercase ASCII (akribis, akuralab, solfarma, singular4, akiot, akribis-group, akribis-one), the same in file names, CSS files, data-brand, the register and the repositories; the Worker names drop the dot (akrimetcom). File names follow ADR-0028: <brand>-<piece>-<colourway>[-<variant>].<format>.
• Addresses. Under the URL grammar of ADR-0025 (lowercase ASCII, hyphens, a trailing slash), the shared pages are called, in Spanish, English and Portuguese: home /; contact contacto, contact, contato; thank-you gracias, thank-you, obrigado; privacy privacidad, privacy, privacidade; the legal notice aviso-legal, legal-notice, aviso-legal; the 404 one file at the root. They live in brand/anatomy.yaml and /anatomy.json; the site package reads them, so a site never types a slug; the checker’s pages rule verifies that each exists for every language. A site’s own slugs follow the same grammar and are translated too, one word per language, without accents.
• The check. standards.yaml lists the spellings that are never written (SOL FARMA, Sol Farma, AKIOT, Akiot, AKRIBIS · One, AKRIBIS ONE, Akribis One, Parte de AKRIBIS, among others); the checker’s naming rule reads every page’s visible text and fails the build on one. Text that quotes a wrong form as an example says so with data-naming="quoted"; code is skipped. This site’s topic pages and records quote them and pass.

Consequences

• Good, because “what is this page called in Portuguese” has one answer, in data, and a site with a page missing in one language does not build.
• Good, because the misspellings that exist today on the sites become a failing build when each is rebuilt.
• Open: the word list grows as cases appear; the case of unit names in long legal texts waits for Voice (1.5); whether the lowercase form may be used in running text at all.