Skip to content

Redesign the website and state production use accurately - #161

Merged
tonibergholm-codento merged 8 commits into
mainfrom
website-overhaul
Nov 20, 2026
Merged

tonibergholm-codento merged 8 commits into
mainfrom
website-overhaul

Conversation

@tonibergholm-codento

Copy link
Copy Markdown
Collaborator

The site was one narrow column of monospaced text, and it described all three projects as experiments. Two of them now run in production at Codento Engine, and the pages did not say so.

This is a full redesign:

  • Design system: light and dark themes, system fonts, one accent color, a 1104px layout with prose capped at 68ch, a skip link and visible focus states. There are no external requests and no new dependencies.
  • Home page: a one-sentence hero, a card per project with a status badge, and an "In production" section that says exactly what Codento Engine runs and what it does not.
  • Project pages: one template for all three. A status panel sits beside the hero, followed by quickstart, features, how it works, security and limits, recent changes, FAQ and docs links.
  • Learn pages: the new layout and typography. Article text is unchanged.

Production claims are scoped. src-control's badge covers sc-forge only, as Codento Engine's project Git host. Sentinel's badge covers observe mode only, as the auditing npm proxy in Engine's build stack. git.agentic is stated as not in production use. The existing caveats stay: pre-1.0, cryptography not independently audited, alpha APIs, and the rollback target still under verification.

Routes, canonical URLs and JSON-LD types are unchanged. The only script is a copy button on quickstart panels, and pages work without it.

Proof: npm run build and npm run check:seo pass for 9 pages. The route check against wrangler dev passes. A contrast script over 38 color pairs shows 5.0:1 or better in both themes. I reviewed full-page screenshots at 1440 and 390 wide in light and dark.

Merging deploys to production through the website-production environment, which waits for owner approval.

Created with Claude Fable 5.2 in Claude Code.

The site was a single narrow column of monospaced text and described
all three projects as experiments. This replaces it with a design
system in Base.astro (color, type, spacing and radius tokens, light and
dark themes from the system setting, a sans-serif stack for prose and
mono for code only) and rebuilds every page on it.

Base now renders the skip link, header, main landmark and footer. The
three project pages share one template in layouts/Project.astro: hero
with a status panel, section nav, quickstart, features, how it works,
security and limits, recent changes, FAQ and doc links.
data/projects.ts holds one status badge vocabulary used by the home
cards and the project pages.

Content changes follow the 2026-11-20 fact sheet. The home page and the
src-control and Sentinel pages now say what Codento Engine runs in
production: sc-forge as its project Git host, and Sentinel as its
auditing npm proxy in observe mode. Each "In production use" badge
sits next to its scope. The pages keep the caveats: git.agentic is not
in production and its rollback target at 1M-row scale is unverified,
src-control is pre-1.0 with unaudited cryptography, and Sentinel is a
pre-1.0 alpha whose block mode is not proven in production.

Routes, canonical URLs and JSON-LD types are unchanged. The only
script is an inline copy button for command panels, added by JS so the
pages work without it.
The redesign changed the learn index and the four article pages, so
their modifiedTime, the Article dateModified and the sitemap lastmod
move to 2026-11-20. The article text itself is unchanged.
State each project's maturity and production use the same way the
pages do, add sc-forge and the Sentinel repository to the sources, and
replace the em dashes.
The recent-changes bullet on the git.agentic page said the sidecar
isolates credentials from the worker, while the security section on
the same page says full isolation still needs separate service
identities. The bullet now says what the deployment does and repeats
the limit.

The quickstart notes now state only what the demo README or the
commands themselves show. Inline code keeps its border when it wraps
across lines, and an unused type token is removed.
@coderabbitai

coderabbitai Bot commented Nov 20, 2026 •

Copy link
Copy Markdown

Important

  • Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: bfda04f2-61ab-4ea7-9d71-10f055254767
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 20, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-20T13:35:18.764911Z ec753a0 New commits
🔒 Security Review ✅ Completed 2026-11-20T13:36:28.716491Z ec753a0 New commits
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

Wide code scrolled inside a pre that keyboard users could not focus.
The Panel component now wraps its code in a focusable region with a
label, so the arrow keys scroll it without JavaScript. Tables get a
minimum width so they scroll inside their wrapper on small screens
instead of crushing their columns.

The copy button now reports success or failure, including a clipboard
denial, through a polite live region and its own label.

Section accepts a heading id so the FAQ heading keeps its old
#frequently-asked-questions anchor next to the new #faq section id.
git.agentic: a commit versions all six dimensions, but rollback only
restores prompts, tracked memory and schema. It records the code SHA
without checking it out, records tool fingerprints without applying
them, and leaves a model change to an operator redeploy
(crates/agenticd/src/rollback/mod.rs). The page, the FAQ and its
JSON-LD, the home page and llms.txt now say that, and the dimension
table has a column for what rollback does with each. The invented
v0.7 transcript is replaced by an excerpt of the recorded run in
examples/langgraph-rollback/demo.cast; the em dashes inside it are
the program's own output. The quickstart no longer runs
docker-compose, because run-demo.sh starts compose itself. The npm
audit claim is removed.

src-control: the demo script is described as a check for leftover
artifacts, since it runs with spill enabled and compares two file
lists. Memory-only statements now say "with spill disabled". The
provenance text says signing and verification are supported and that
amend, rebase and merge results start unsigned.

Sentinel, checked against the pkg-registry README: the sandbox claim
is limited to runs Sentinel starts and states the Linux Landlock
helper requirement and the default allowed reads. Scoring text
separates the block verdict from HTTP enforcement. Retraction is
scoped to native or claimed packages with 72 hours and 1,000
downloads as policy defaults, and advisories reach other
installations on the corpus release schedule. The feature intro no
longer makes claims about npm.

The home page gets back its #git-agentic, #src-control, #sentinel and
#learn fragment ids, and the dimension table is a focusable scroll
region.
Sentinel: the sandbox applies to enforced runs only (run-scripts,
install --enforce, exec). `sentinel install` without --enforce just
routes npm through the proxy. The restrictions are described as
defaults that approved capabilities can relax.

The 403 under block and the served tarball under observe apply to
scoring verdicts on tarballs that have not been retracted. A
retracted tarball gets a 410 in either mode.

A local retraction reaches other installations only if the advisory
is submitted to the steward, which accepts only packages in claimed
namespaces. Peers see it when they load a signed corpus that contains
it.

src-control: new commits created by amend, rebase or merge start
unsigned. A fast-forward merge can land on a commit that is already
signed, so "results" was too broad.

The copy button cancels its previous reset timer before starting a
new one, so a second click is not reset early by the first.
@tonibergholm-codento
tonibergholm-codento merged commit e545ed6 into main Nov 20, 2026
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant