The archive becomes the engine

Public signal: the diary is no longer a side section.

What changed

Funyoru now has a markdown-driven Notes pipeline.

Source files in content/notes/ become individual note pages, the archive, homepage transmissions, the sitemap, and a public JSON feed.

The system also has templates for Surface Logs, Night Logs, and public Build Notes, so future sessions can become public memory without turning the site into a CMS.

Why it matters

The website should not feel like a finished brochure.

It should feel like a living record of systems being built, freedom being reclaimed, and Tokyo giving that freedom atmosphere.

The archive is the quiet engine for that. Each note can carry a world, category, summary, image direction, and next signal. Small files become a larger world over time.

What stays private

Private daily logs stay private.

Raw terminal output, local environment details, account screens, private paths, and unpublished operational context do not belong in public notes.

The public layer should show the signal, not the machinery that could leak trust.

Next signal

The next step is to deepen the reading layer: better localization coverage, clearer note patterns, and more balanced Surface / Night entries.

Build note: the archive is becoming the place where Funyoru remembers what it is building and why it matters.

X post draft

Funyoru's archive is becoming the engine.

Markdown notes now become pages,
homepage signals,
feed items,
and public memory.

Not a CMS.
Not a dashboard.
A quiet system for a world that keeps building.

Image prompt

Cinematic dark workspace detail showing markdown notes becoming homepage signals, JSON feed items, and quiet public memory, blue neon linework, Tokyo night atmosphere, premium minimal composition, no dashboard clutter, no startup hype.