Point humble, jazzy, lyrical and rolling to RoboStack/robostack and deprecate the rest (#206)

* Point humble, jazzy, lyrical and rolling links to robostack-distros

These four distributions are moving into the robostack-distros monorepo
(RoboStack/robostack#54). Link their distro pages, issue
links and contributing instructions there; Noetic, Kilted and the EOL
distros keep their own repositories.

* Use RoboStack/robostack and mark the other distros deprecated

The monorepo will live at RoboStack/robostack. Noetic, Kilted, Galactic
and Foxy are not moving into it and are no longer maintained, so say so
on their distro pages, the support page and the contributing guide.

* Add a page explaining the move to the RoboStack monorepo

Users land on distro pages, Getting Started, Support and Contributing
without knowing the repositories changed. Explain the move and the
deprecation of Noetic, Kilted, Galactic and Foxy on one page, and link
to it from an admonition on each of those pages.

* Write the monorepo page so it still reads well later

Drop "until now" and "nothing changes" phrasing that only makes sense
right after the move; describe the setup as it is, and the move as
something that happened in 2026.

* List the monorepo page under Docs and shorten the notice

The page explains where packages come from, so it belongs with the docs;
it stays cross-listed under Community. The notice only needs to point to
the move; the page itself covers the deprecated distros.

* List every page in exactly one navigation section

Contributing was in the Docs sidebar and the monorepo page in the
Community sidebar, while the header highlighted the other tab for them.
Clicking such an entry switched the header tab and the sidebar under
you. Keep each page only in the group of the tab that highlights it.

* Label the distro page's GitHub link "Distro config"

The repository name is the same for every maintained distro now, so it
no longer tells the reader anything; the link goes to the distro's own
folder. The repository is still named in the tooltip.

* Make the monorepo note a reusable component

The same note was copied into Getting Started, Support and Contributing,
with a variant on the distro pages. MonorepoNote renders both, and takes
the list of maintained distros from distros.ts, so the wording lives in
one place. Support and Contributing become .mdx to use it.

* Explain how to build a single package from the monorepo

A full build takes hours; contributors working on one patch only need
build-one. Document the generate-recipes step, the build number bump an
already published package needs, and where the output ends up. Also
drop the build steps for the deprecated distros.

* Apply suggestion from @ruben-arts

* Adding packages updated

Author: ruben-arts

astro.config.mjs

@@ -63,7 +63,9 @@ export default defineConfig({
       sidebar: [
         // One top-level group per header tab (src/components/Header.astro);
         // the Sidebar override shows only the current page's group, so these
-        // group labels never render. Slugs are set explicitly in each page's
+        // group labels never render. List each page in exactly one group, the
+        // one whose tab nav.ts highlights for it, so the sidebar and the
+        // header tabs never disagree. Slugs are set explicitly in each page's
         // frontmatter to keep the published mixed-case URLs
         // (`GettingStarted.html`, `FAQ.html`, ...).
         {
@@ -79,9 +81,7 @@ export default defineConfig({
             },
             { label: "JupyterRos", slug: "JupyterRos" },
             { label: "FAQ", slug: "FAQ" },
-            // Cross-listed; its primary section is Community (the last
-            // group containing a page wins in the Sidebar override).
-            { label: "Contributing", slug: "Contributing" },
+            { label: "RoboStack monorepo", slug: "Monorepo" },
           ],
         },
         {

src/components/DistroHead.astro

@@ -24,16 +24,16 @@ const { distro } = Astro.props;
     </h1>
     <p class="support">{supportLine(distro)}</p>
   </div>
-  <!-- The label is spelled out for screen readers because the repo name is
+  <!-- The label is spelled out for screen readers because the visible text is
        dropped on narrow screens, where the mark alone carries the link. -->
   <a
     class="repo"
     href={repoUrl(distro)}
-    aria-label={`${repoName(distro)} on GitHub`}
-    title={`The recipes that build the ${distro.channel} channel`}
+    aria-label={`${title(distro)} distro config on GitHub`}
+    title={`The recipes in ${repoName(distro)} that build the ${distro.channel} channel`}
   >
     <span class="repo__icon" aria-hidden="true"></span>
-    <span class="repo__name">{repoName(distro)}</span>
+    <span class="repo__name">Distro config</span>
   </a>
 </div>
 

src/components/MonorepoNote.astro

@@ -0,0 +1,36 @@
+---
+import { Aside } from "@astrojs/starlight/components";
+import type { Distro } from "../data/distros";
+import { DISTROS, isDeprecated, repoUrl, title } from "../data/distros";
+
+/**
+ * The "RoboStack is now a monorepo" note, linking to /Monorepo.html. Shown on
+ * the docs pages and on the distro pages of the maintained distros; pass
+ * `distro` on a distro page to word it for that one and link its folder.
+ */
+interface Props {
+  distro?: Distro;
+}
+
+const { distro } = Astro.props;
+
+// "Humble, Jazzy, Lyrical and Rolling", in the order of distros.json.
+const names = DISTROS.filter((d) => !isDeprecated(d)).map(title);
+const maintained = `${names.slice(0, -1).join(", ")} and ${names.at(-1)}`;
+---
+
+<Aside title="RoboStack is now a monorepo">
+  {distro ? (
+    <p>
+      {title(distro)} is now built from{" "}
+      <a href={repoUrl(distro)}>RoboStack/robostack</a>, together with the other
+      maintained distributions. <a href="/Monorepo.html">Read what changed</a>.
+    </p>
+  ) : (
+    <p>
+      {maintained} are now built from one repository,{" "}
+      <a href="https://github.com/RoboStack/robostack">RoboStack/robostack</a>.{" "}
+      <a href="/Monorepo.html">Read what changed</a>.
+    </p>
+  )}
+</Aside>