Repository navigation
Feat: pivot the landing page to the project directory - #135
Conversation
Replace the 'Platform primitives / RossoCortex data plane' narrative with a project-focused landing page: an org-level intro plus three groups of project cards (core projects, research collaborations, automation & repo maintenance). Each card carries only the essence of the project and links to its repository, where the details, instructions, and examples live. The earlier platform direction stays on the page as a 'Past activities' section: the data-plane functions and services cards return as a historical record (shipped through v0.8), each pointing at the repository where that work lives today (RossoCortex is renamed to cortex throughout). The old landing page is additionally archived as a draft backup (welcome-platform-story.mdx), and the site tagline is updated to match the new focus. Assisted-By: Claude (Anthropic AI) <noreply@anthropic.com> Signed-off-by: Mariusz Sabath <mrsabath@gmail.com>
✅ Deploy Preview for animated-crumble-fb8862 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
| platform owners can build on. It comes in three parts: RossoCortex, a data plane that mediates | ||
| what agents do, a set of services agents can call and a set of tools and frameworks for observability, | ||
| security, governance and administration. It's open source, framework-neutral, |
There was a problem hiding this comment.
I'm confused what the "three parts" refer to with the various commas, especially assuming "data plane.." is meant to describe RossoCortex rather than a separate "part"
There was a problem hiding this comment.
Good catch — that sentence now only lives in the archived draft: true backup of the old page, which stays verbatim. The live copy in rossoctl/rossoctl#2662 reads "RossoCortex (a data plane); a set of callable services; and tooling …" with the paragraph split (1031f192).
The GitHub button next to Get started rendered taller than its neighbour: MDX parsed the multi-line JSX children as a markdown paragraph inside the link, adding paragraph spacing inside the button. Write the Link on a single line so both CTAs render identically. The ecosystem plugin's editUrl now points at this repo instead of the archived rossoctl/ecosystem-guide, so the landing page's "Edit this page" link resolves (it previously 404'd on a doubled path). Assisted-By: Claude (Anthropic AI) <noreply@anthropic.com> Signed-off-by: Mariusz Sabath <mrsabath@gmail.com>
The historical data-plane/services cards and the archived-repositories table are gone from the page. The pre-pivot narrative remains available in the repo as the draft backup (welcome-platform-story.mdx). Reverts the Accordion now/discontinued extensions, which existed only to render those cards; the component is back to its pre-PR shape. Assisted-By: Claude (Anthropic AI) <noreply@anthropic.com> Signed-off-by: Mariusz Sabath <mrsabath@gmail.com>
The hero's Get started button now anchors to the Core projects section on the landing page instead of /docs/, which still presents the earlier platform work. Each project card always shows an explicit Get started link to its own repository in the footer, so the per-project entry point is unmistakable even before reading the card. Assisted-By: Claude (Anthropic AI) <noreply@anthropic.com> Signed-off-by: Mariusz Sabath <mrsabath@gmail.com>
aslom
left a comment
There was a problem hiding this comment.
Review: pivot the landing page to the project directory
Approving. The pivot is cleanly executed and every verification claim in the
description checks out against the deploy preview. Notes below are follow-ups, not
blockers.
Verified independently against the Netlify preview and the head commit
(5869daa):
id="core-projects"is present and the hero "Get started" anchor resolves to it- all 11 project cards render, across the three expected groups
(core-projects,context--governance,automation--repo-maintenance) - every card repo link and sibling/project-site link returns 200, and all 13 linked
repos are public and un-archived (autobench-claudecode,context-guruproject
site, cortex install stats included) - the
editUrlfix works: "Edit this page" on the landing page now resolves to
rossoctl/.github/tree/main/ecosystem/welcome.mdx(200), not the archived
ecosystem-guide draft: truedoes keep the archived narrative out of the build —
/welcome-platform-storyand/welcome-copyboth 404 on the preview, matching the
welcome-copy.mdprecedent exactly (same frontmatter shape, same comment banner)- no deprecated or archived repo is listed anywhere on the page
- DCO green, Netlify deploy preview green, no CI/agent/dependency config touched and
no secrets in the diff
Two things worth a follow-up: the moca card's "(Go)" annotation elsewhere in this
series looks inverted relative to the repo's actual stack, and ProjectCards uses raw
<a> where the sibling GitHubStars component uses Docusaurus <Link>. Details
inline.
Nice touch documenting why the editUrl base has no ecosystem/ segment — that
doubling is exactly the kind of thing that gets "fixed" back into a bug later.
| {items.map((item) => ( | ||
| <div className={styles.card} key={item.repo}> | ||
| <h3 className={styles.name}> | ||
| <a |
There was a problem hiding this comment.
[low] Sibling components in this repo use the Docusaurus <Link> for external
hrefs — GitHubStars/index.tsx imports @docusaurus/Link and renders a <Link>
with a https://github.com/... href. ProjectCards uses raw <a> in both places
(title here, footer links below).
Functionally fine — rel="noopener noreferrer" is set correctly on every anchor, so
there's no security gap, and <Link> passes external URLs straight through anyway.
It's purely a consistency note for whoever edits this next.
Also worth noting the repo URL is built twice per card (here and on the footer "Get
started" anchor); hoisting it would remove the duplication:
const repoUrl = `https://github.com/${item.repo}`;There was a problem hiding this comment.
Addressed in 1ccf1a4 — the card title and footer anchors now render through @docusaurus/Link, matching GitHubStars, and the repository URL is built once per card (const repoUrl) instead of twice.
| <div className="margin-top--md margin-bottom--lg"> | ||
| {/* Primary CTAs point at the project repos (docs hidden pre-launch). */} | ||
| <Link className="button button--lg cta-primary margin-right--sm" href="/docs/">Get started</Link> | ||
| <Link className="button button--lg cta-primary margin-right--sm" href="#core-projects">Get started</Link> |
There was a problem hiding this comment.
[low] The hero "Get started" now points at #core-projects, an on-page anchor,
while the adjacent GitHub button is a real external link. Both verified working on the
preview.
One consequence worth being deliberate about: /docs/ still exists and returns 200,
but nothing in the hero routes there anymore. That matches the PR's stated intent
(docs still present the earlier platform work), so no change requested — just
flagging that the docs are now reachable only via the navbar, which is easy to forget
when the docs section is eventually refreshed.
There was a problem hiding this comment.
Ack, and thanks for flagging the consequence. The remaining funnels into /docs/ (announcement bar, navbar Documentation + version dropdown) are being tracked as a follow-up until the docs themselves catch up with the current focus.
| <div className="rosso-intro"> | ||
|
|
||
| rossoctl is a set of platform primitives for agent security, resilience, reliability and efficiency that | ||
| platform owners can build on. It comes in three parts: RossoCortex, a data plane that mediates |
There was a problem hiding this comment.
[low] This is the sentence @evaline-ju asked about on the first pass ("confused
what the 'three parts' refer to with the various commas"). The comma-spliced list —
RossoCortex, a data plane that mediates what agents do, a set of services agents can call and a set of tools... — reads as four items rather than three because the
appositive isn't set off.
It's archived, draft: true, build-excluded prose, so it genuinely does not matter
here. Raising it only because the same sentence is being added as live prose in
rossoctl/rossoctl#2662 (INSTALLER.md:3), where it is reader-facing. Fixing it
there is the useful move; semicolons already do the job in the 2662 variant, which is
most of the way there.
There was a problem hiding this comment.
Left verbatim on purpose — welcome-platform-story.mdx is the archived draft: true backup of the pre-pivot page, so it stays byte-identical to what was live. The reader-facing variant of this sentence is fixed in rossoctl/rossoctl#2662 (1031f192): the appositive is parenthesized and the intro paragraph is split.
Match the sibling GitHubStars component and render the card anchors through @docusaurus/Link instead of raw <a>, and build the repository URL once per card instead of twice (title and footer Get started anchor), per review feedback. Assisted-By: Claude (Anthropic AI) <noreply@anthropic.com> Signed-off-by: Mariusz Sabath <mrsabath@gmail.com>
Summary
Replaces the "Platform primitives / RossoCortex data plane" landing narrative with a project directory that matches the org's current focus. The homepage now leads with a short org-level intro plus three groups of project cards:
Each card carries a high-level essence of the project — grounded in the current READMEs, epics, and recent PRs of each repo — and links to its repository, where all details, instructions, and examples live. The Cortex card covers today's story (the observability/cost proxy,
agentop, tool-definition pruning) including Cortex Local on end-user machines and Cortex Remote, deployed along the harness, as the explored direction. Repo families link the main repo and list public siblings (private siblings are skipped).Details:
ProjectCardscomponent (src/components/ProjectCards/) — responsive card grid following the site's design tokens (brand-red title link, 1px emphasis border, muted footer links)ecosystem/welcome-platform-story.mdx(same pattern aswelcome-copy.md), not linked in the sidebar/docs/, which still presents the earlier platform work; every project card also carries an explicit "Get started ↗" footer link to its own repositoryLink, avoiding an MDX paragraph-inside-JSX pitfall)editUrlpoints at this repo, so the landing page's "Edit this page" link resolves (it previously 404'd via the archivedecosystem-guide)Verification
npm run buildpasses with no new broken-link warningsnpm run typecheckpassesid="core-projects") and all 11 "Get started ↗" card links verified in the built HTMLAssisted-By: Claude Code