fix(site): compressHTML whitespace mode; contributing example link to a real map

compressHTML: true restores pre-7 whitespace collapse (space preserved
between text and inline elements) — the systemic fix for the glue bug
hand-patched across pages; the source-level vitest guard stays as a
second layer. The old Map_Format.adoc reference no longer exists —
point step 03 at a fully-worked map in the corpus instead (resolves
once interscript/maps#180 lands the .isc migration).

Author: ronaldtse

astro.config.mjs

@@ -10,6 +10,9 @@ import node from "@astrojs/node"
 // @astrojs/node. Deploy target: any Node-capable host.
 export default defineConfig({
   site: "https://www.interscript.org",
+  // Collapse whitespace to a single space (pre-7 behavior) instead of
+  // JSX-style removal, which glues text to adjacent inline elements.
+  compressHTML: true,
   output: "static",
   adapter: node({ mode: "standalone" }),
   integrations: [vue()],

src/pages/contributing.astro

@@ -11,10 +11,9 @@ import Base from "../layouts/Base.astro"
       <p class="eyebrow eyebrow-accent">Contributing</p>
       <h1>Add a transliteration system.</h1>
       <p class="hero-deck">
-        Interscript grows when contributors encode romanization systems
-        from authority documents into the open-source corpus. This page
-        walks through the process — it's more straightforward than it
-        looks.
+        Interscript grows when contributors encode romanization systems from authority documents
+        into the open-source corpus. This page walks through the process — it's more straightforward
+        than it looks.
       </p>
     </div>
   </section>
@@ -26,10 +25,11 @@ import Base from "../layouts/Base.astro"
         <h2>Find a system to add</h2>
       </header>
       <p>
-        Browse the <a href="/maps">catalogue</a> to see what's already
-        covered. Then check the <a href="https://github.com/interscript/maps/issues" rel="noreferrer">issue tracker</a> for requested systems. If the system you want isn't listed
-        anywhere, open a new issue describing the authority document so
-        maintainers can confirm scope.
+        Browse the <a href="/maps">catalogue</a> to see what's already covered. Then check the <a
+          href="https://github.com/interscript/maps/issues"
+          rel="noreferrer">issue tracker</a
+        > for requested systems. If the system you want isn't listed anywhere, open a new issue describing
+        the authority document so maintainers can confirm scope.
       </p>
     </article>
 
@@ -39,63 +39,59 @@ import Base from "../layouts/Base.astro"
         <h2>Read the authority document</h2>
       </header>
       <p>
-        Most authority romanization tables are published as PDFs.
-        Read carefully — the rules include edge cases (word-initial vs
-        word-medial, before/after context, special characters). Note
-        every rule with its source page number; you'll cite it in the
-        map metadata.
+        Most authority romanization tables are published as PDFs. Read carefully — the rules include
+        edge cases (word-initial vs word-medial, before/after context, special characters). Note
+        every rule with its source page number; you'll cite it in the map metadata.
       </p>
       <p>
-        If the authority document isn't freely available, look for
-        secondary sources (Wikipedia, library science journals) that
-        describe the rules. Cite the secondary source in those cases.
+        If the authority document isn't freely available, look for secondary sources (Wikipedia,
+        library science journals) that describe the rules. Cite the secondary source in those cases.
       </p>
     </article>
 
     <article class="step">
       <header>
         <span class="step-num tnum">03</span>
-        <h2>Write the map in the Ruby DSL</h2>
+        <h2>Write the map in ISC</h2>
       </header>
       <p>
-        Maps live in <a href="https://github.com/interscript/maps" rel="noreferrer">github.com/interscript/maps</a>,
-        named <code>{"{authority}-{lang}-{source_script}-{dest_script}-{year}.imp"}</code> (e.g. <code>bgnpcgn-ukr-Cyrl-Latn-2019.imp</code>).
+        Maps live in <a href="https://github.com/interscript/maps" rel="noreferrer"
+          >github.com/interscript/maps</a
+        >, named <code>{"{authority}-{lang}-{source_script}-{dest_script}-{year}.isc"}</code> (e.g. <code
+          >bgnpcgn-ukr-Cyrl-Latn-2019.isc</code
+        >).
       </p>
-      <pre><code set:html={`# bgnpcgn-ukr-Cyrl-Latn-2019.imp
+      <pre><code set:html={`# bgnpcgn-ukr-Cyrl-Latn-2019.isc
+system "BGN-PCGN:ukr-Cyrl:Latn:2019" {
+
 metadata {
-  authority_id: bgnpcgn
-  id: 2019
-  language: iso-639-2:ukr
-  source_script: Cyrl
-  destination_script: Latn
-  name: Romanization of Ukrainian (2019)
-  url: https://github.com/interscript/maps/blob/main/docs/bgnpcgn-ukr-2019.pdf
+  authority_id bgnpcgn
+  id 2019
+  language iso-639-2:ukr
+  source_script Cyrl
+  destination_script Latn
+  name Romanization of Ukrainian (2019 Agreement)
+  url https://assets.publishing.service.gov.uk/...
 }
 
-aliases {
-  # custom aliases if needed
+tests {
+  "Алушта" -> "Alushta"
+  "Борщагівка" -> "Borshchahivka"
 }
 
-stage {
+stage main {
+  run map.cyrllatn.stage.main
   parallel {
-    sub "а", "a"
-    sub "б", "b"
-    sub "в", "v"
-    # … all single-char rules
-    sub "щ", "shch"
-    sub "ь", "ʹ"
-    sub "'", "'"   # apostrophe stays
+    sub "'" ""
   }
-
-  # Title-case names at word boundaries
-  sub any("a".."z"), upcase, before: boundary
 }
-
-test "Антон", "Anton"
-test "Київ", "Kyiv"`} /></pre>
+}`} /></pre>
       <p>
-        The DSL has more options (capture groups, before/after
-        constraints, run rules that compose stages) — see the <a href="https://github.com/interscript/interscript-ruby/blob/main/docs/Map_Format.adoc" rel="noreferrer">Map Format guide</a> for the full reference.
+        The format has more options (capture groups, before/after constraints, run rules that
+        compose stages) — the corpus itself is the reference; see <a
+          href="https://github.com/interscript/maps/blob/main/maps/bgnpcgn-ukr-Cyrl-Latn-2019.isc"
+          rel="noreferrer">bgnpcgn-ukr-Cyrl-Latn-2019.isc</a
+        > for a fully-worked map.
       </p>
     </article>
 
@@ -105,16 +101,13 @@ test "Київ", "Kyiv"`} /></pre>
         <h2>Add test vectors</h2>
       </header>
       <p>
-        Every map ships with <code>test</code> directives — input →
-        expected output pairs pulled from the authority document or
-        real-world examples. These run against the Ruby interpreter
-        and, via the JSON IR, against the TypeScript runtime. Failures
-        block merge.
+        Every map ships with <code>test</code> directives — input → expected output pairs pulled from
+        the authority document or real-world examples. These run against every engine — the Ruby interpreter
+        and the TypeScript ISC runtime. Failures block merge.
       </p>
       <p>
-        Aim for at least 10 test vectors covering common cases,
-        diacritics, edge cases, and (where applicable) word-boundary
-        behavior. Cite source pages in code comments.
+        Aim for at least 10 test vectors covering common cases, diacritics, edge cases, and (where
+        applicable) word-boundary behavior. Cite source pages in code comments.
       </p>
     </article>
 
@@ -124,18 +117,15 @@ test "Київ", "Kyiv"`} /></pre>
         <h2>Open a pull request</h2>
       </header>
       <p>
-        Fork <code>interscript/maps</code>, push your branch, open a PR.
-        The CI pipeline runs the Ruby test suite, regenerates the JSON
-        IR, and re-checks the parity suite. Maintainers review the map
-        against the source document; if rules are missing or wrong,
-        they'll point out specific page numbers.
-      </p>
-      <p>
-        Once merged, the new system is automatically:
+        Fork <code>interscript/maps</code>, push your branch, open a PR. The CI pipeline runs the
+        test suite against every engine and re-checks the parity suite. Maintainers review the map
+        against the source document; if rules are missing or wrong, they'll point out specific page
+        numbers.
       </p>
+      <p>Once merged, the new system is automatically:</p>
       <ul>
         <li>Available in the Ruby gem (next release)</li>
-        <li>Available in <code>interscript-ts</code> via the JSON IR</li>
+        <li>Available in <code>interscript-ts</code> via the ISC runtime</li>
         <li>Live on <a href="/">interscript.org</a> (next site build)</li>
         <li>Available through the <a href="/api-docs">REST API</a></li>
       </ul>
@@ -144,8 +134,9 @@ test "Київ", "Kyiv"`} /></pre>
     <section class="contrib-cta">
       <h2>Need help?</h2>
       <p>
-        Open a <a href="https://github.com/interscript/maps/issues" rel="noreferrer">GitHub issue</a> with the authority document and what you've tried. The community
-        is friendly and the maintainers are responsive.
+        Open a <a href="https://github.com/interscript/maps/issues" rel="noreferrer">GitHub issue</a
+        > with the authority document and what you've tried. The community is friendly and the maintainers
+        are responsive.
       </p>
     </section>
   </section>