theme
cubesite.css — the colors, type, header, cards and prose every project site is built from, in both light and dark.
cubesite
One brand, one stylesheet, one Pages workflow — for every cubicecho repo.
What it does
Every repo under Cubic Echo should have a site at
cubicecho.github.io/<repo>/ — even the small libraries,
whose whole story is a paragraph and an install line. cubesite is what makes
that cheap: a scaffold that writes the site, a stylesheet they all share, and
one Pages workflow that is the same file in every repo.
-
-
brand
The mark, the wordmark, the tokens, and the few rules for using them. see them ↗
-
template
A one-page Eleventy site, already branded, with the TODOs marked. Fill in three of them and it is a real site.
-
pages.yml
Build
site/, refuse to publish an empty one, deploy. The same file in every repo, so a fix travels.
Why
The same argument as cubeui,
one layer out. Four repos had a site before this one existed —
mcp-router, mcp-skills-manager, auto-cal,
cubeui — and each had written its own stylesheet, its own
layout, its own header. They do not look like the same org, because nothing
made them. One of them wears a 🔀 as its logo.
The other half is coverage. Most repos had no site at all, so the only
public face of something like agent-core was a README in
GitHub's chrome — fine for a reader already on GitHub, nothing for a link
in a chat or a search result. A one-page site is cheap. It was just never
anybody's job.
Get started
git clone https://github.com/cubicecho/cubesite
cd cubesite && npm install
# add a site to a repo that has none
node scripts/scaffold.mjs ../<repo>
# re-brand a repo that already has one
node scripts/scaffold.mjs ../<repo> --theme
# which repos are still missing a site?
npm run auditFull documentation lives in the project README: https://github.com/cubicecho/cubesite