Skip to content

Redesign the site around composition and the mesh - #5

Merged
marcos-mendez merged 1 commit into
mainfrom
feat/enterprise-redesign
Sep 30, 2026
Merged

marcos-mendez merged 1 commit into
mainfrom
feat/enterprise-redesign

Conversation

@marcos-mendez

Copy link
Copy Markdown
Contributor

What

A redesign of keellinux.org for the composition architecture (decisions 0023 to 0041), keeping IPv6-first and declarative as the project's identity.

Pages:

  • index.html: hero with the approved copy, six pillars each with a build status badge, a composition diagram (Core, Web, runtime, application; data services beside; the mesh between), installation modes, the request pipeline, the declarative workflow, signed layers with the build measurements, standards, status.
  • architecture.html: composition, overlays, appliances, applications, the manifest (0041), the spec, IPv6-first, layers, upgrades.
  • security.html: keys and identity (with what is not done yet), the pipeline, default states per mode, exposure classes, network changes, secrets, package provenance.
  • cloud.html: installation modes and discovery, the mesh, the etcd registry, failover and failback, directory replication, backup and object storage, monitoring, what it does not promise.
  • roadmap.html: a static copy of tracker#46 with per-phase progress and links to the decision issues.
  • guidelines.html: kept, updated for the tracker, the retired LAMP/LAPP appliances and the brand guide (mark description and colours).

Every claim is true of the code or labelled Decided, Partly built or Goal, with the decision linked on the tracker. No commercial content, no places, no invented numbers; the measurements are the existing ones, labelled as measured on the build host.

Design and scripts

Dark and light themes (same toggle, same keel-theme key), responsive to phone width with no horizontal scroll (checked at 390 px). Vanilla JS, self-hosted, lazy-loaded when the element nears the viewport: the hero mesh canvas, the pipeline canvas, the terminal replay (output lines from keel's docs), scroll reveal. All respect prefers-reduced-motion; pages work without JS. Plausible stays and is now on every page, not only the home page. og:image and canonical URLs are absolute.

sitecheck

New rules with tests: required description and social meta; no resource from another origin except the analytics script (pages and stylesheets); forbidden terms (pricing, customers, contracts, city names and the like) and em dashes in the copy; references to https://keellinux.org/ checked as paths in the tree; data-src counts as a reference. Coverage 99 percent.

Test plan

  • python3 tools/sitecheck.py .: 6 pages, 0 findings
  • unit tests pass under coverage (99 percent, bar 95)
  • Playwright: every page, desktop and mobile, light and dark; no JS errors, no horizontal overflow
  • Maintainer review of copy and design on the preview
  • Check the Pages deploy after merge

The site now describes the architecture decided on 2026-09-30 (0023 to
0041) and keeps IPv6-first and declarative as its identity. Six pages: the
home, architecture, security, cloud and replication, a roadmap mirrored
from tracker#46, and the guidelines. Every claim is either true of the
code or labelled as decided or a goal, with its decision linked on the
tracker.

Kept from the previous site: the IPv6 examples, the signed content
addressed layers and the build measurements, labelled as measured on the
build host, the standards, and an honest status. The core, stack and app
diagram is replaced by a composition diagram: Core, Web, runtime and
application, with the data services beside them, joined by the mesh.

Animations are vanilla JavaScript, self-hosted and loaded only when their
element comes into view: a mesh of IPv6 nodes in the hero, the request
pipeline, a terminal replay of inspect, diff and apply with output lines
from the keel documentation, and scroll reveal. All of them stop under
prefers-reduced-motion, and every page works without JavaScript.

sitecheck gains four rules, each with tests: the description and social
meta tags are required, nothing is loaded from another origin but the
analytics script (in pages and in stylesheets), the copy names no
commercial offer, customer or city and has no em dash, and a reference to
https://keellinux.org/ is checked as a path in the tree. data-src counts
as a reference, so a lazily loaded script is not an orphan.
@marcos-mendez
marcos-mendez merged commit 951815e into main Sep 30, 2026
1 check 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