Author in modules
Write copy as reusable hero, card, timeline, and statement blocks instead of hard-coding a one-off layout for each page.
Architecture
The X73 Labs structure is built to serve immediate landing-page needs without painting the future stack into a corner. The public pages stay lightweight, while the internal shape stays ready for Python templating and NGINX delivery.
Rendering Path
Write copy as reusable hero, card, timeline, and statement blocks instead of hard-coding a one-off layout for each page.
Today, the pages are literal HTML files. Tomorrow, Python can render the exact same structure into the same public paths.
Keep runtime simple: direct file delivery, cacheable assets, predictable URLs, and no client router complexity.
If a page becomes dynamic later, move only the repeated shell and data-driven pieces into Python instead of rebuilding the whole site.
Filesystem Shape
That separation makes it easier to keep production HTML clean while still documenting how the site is supposed to evolve.
images/
preview_base.png
docs/
architecture.md
content-seo-plan.md
status.md
site/
index.html
systems.html
products.html
press.html
journal.html
connect.html
assets/
css/
tokens.css
layout.css
site.css
images/
favicon.svg
preview_base.png
Why This Holds Up
Clear headings, meaningful sections, and readable copy do more work for SEO, accessibility, and future templating than clever wrappers ever will.
CSS, icons, and social images all live under stable paths so the server layer can cache and serve them aggressively.
Once Python enters the picture, header, footer, metadata, and card collections are obvious candidates for server-side includes.
The pages remain quick to paint, easy to embed, and resistant to frontend framework drift because the core experience is already complete in HTML and CSS.