the evolving website
← All journal entriesDaily entry

A new design and a simpler publishing workflow

Design and structure

  • Replaced browser-default styling with shared typography, spacing, colour and navigation.
  • Kept the manifesto on Home. Added a future-only ranked Roadmap and a Solution Design page.
  • Grouped early journal records while keeping their original addresses and text.
  • Added metadata, structured data, a sitemap and crawler access guidance.
Page structure · 18 October 2026

Dated page map: the manifesto homepage connects to Journal, Roadmap and Solution Design.

The original design proposal is preserved in the design evolution record.

Homepage comparison · 16–18 October 2026
The original homepage: one hello-world sentence on a white page.
Original homepage · 16 October 2026.
The homepage candidate with the manifesto headline, shorter supporting copy and clear journal and roadmap links.
Homepage copy candidate · 18 October 2026. Captured at the same 1440 × 900 viewport; prepared for release, not evidence of improved reader outcomes.

Publishing and Linux retirement

  • Proved the GitHub → Cloudflare Pages release path with basic checks and live verification.
  • Removed the project’s Linux runner, publisher, daily monitoring, alert hooks and dedicated accounts.
  • Preserved useful history and the original candidate in a private Windows archive.
Release flow after Linux retirement · 18 October 2026

Historical flow: AI-assisted candidate, GitHub source and checks, explicit Cloudflare Git build, then live verification and saved records. Linux retired; recurring AI work was disabled at this milestone.

Read the retirement milestone for the transition and trade-offs.

Reader navigation

  • Added section links to longer articles and links to earlier project context.
  • Build, link and browser checks passed for the published changes. Reader benefit remains unmeasured.
  • The navigation record keeps the original reasoning and limitations.

One-week AI trial

  • A scheduled activation completed a production release. Later owner-triggered rehearsals published the trial explanation, diagrams and corrected homepage wording.
  • Enabled scheduled AI work at 5 am, 11 am, 5 pm and 11 pm fixed GMT+10, from 18–25 October 2026.
  • Windows must be awake with the app running. Each run can assess up to 20 ideas and publish its recommended eligible batch without separate approval for every release.
  • First recurring slot: 18 October, 5 pm. Last: 25 October, 11 am. Hard stop: 25 October, 1:45 pm GMT+10. Review before extending.
  • Cloudflare automatic Git deployment triggers stay disabled. The AI task requests each build.
  • Kept one shared roadmap and left Linear out. Consolidated Notion into a short current hub and historical archives.
Finite trial loop · 18 October 2026

Owner ideas and research feed a scheduled AI task on Windows, then GitHub checks and merge, a requested Cloudflare build, and live verification. Saved outcomes inform the next decision.

Read the trial milestone or current Solution Design. This snapshot preserves the trial model; it does not establish a successful full week.

Writing style and visual references

  • Applied the owner’s writing style across current pages, labels and daily summaries.
  • Shortened repeated explanations and used direct dot points.
  • Kept the manifesto headline, facts and original historical article bodies.
  • Added image descriptions and discovery metadata. These help readers and crawlers; they do not guarantee indexing or AI citations.
Writing-style workflow · 18 October 2026

The roadmap and writing-style guidance feed the AI task. Changes pass through GitHub, Cloudflare and live verification; saved results inform the next run.

Writing examples guide the style. Their private details stay out of the website.

What we will assess

  • Useful changes, no-change decisions, failures, costs where recorded and owner effort.
  • Whether readers can find updates, explain changes and identify what comes next.
  • Use saved records and feedback to improve decisions; the AI model is not training itself.
Technical record

Record: 2026-10-18-daily-summary · status: implemented · verdict: inconclusive. Technical verification does not establish reader benefit.

All journal entries · Future ideas · Solution Design