Static HTML content management
Management of site content via static files within the content/{slug}.html directory (part of the site/journeys/ system).
Architecture & Implementation
- Storage: Content is stored as pre-rendered
.htmlfiles; currently lacks a native interface for editing content blocks. - Security: All administrative mutations must implement the Same-Origin Guard via
requireSameOriginForMutatingRequest(). - UI Issue: The Ticker Bar is currently obscuring the second row of the homepage navigation (Quick-Nav).
Development Roadmap
- Visual Editor: Development of a block-based editing interface (analogous to Adobe Express) to support the sequential arrangement of text and photo blocks.
- Content Ingestion: Parsing and merging existing Japan Trip PDFs into a single unified blog post.
References
- 2026 04 14 New Claude Plan