Website Development v1.0
This site is the reference implementation of this workflow. Everything below was done on innerstack.ai in September 2026, in this order, and the reasons are ours rather than received wisdom.
The current procedure
- Hosting and WordPressHostinger with LiteSpeed, PHP 8.3, daily backups, and Force HTTPS once the certificate issues. Nameservers point at the host rather than the registrar so DNS and SSL are managed in one place. adopted
- Theme: Kadence, no starter templateKadence plus Kadence Blocks. The global palette and typography panels take brand colours and Google Fonts directly, and the header builder does a sticky header without a page builder. We skipped the starter templates on purpose — they bring markup we would spend longer removing than writing. adopted
- Content model as code, not clicksCustom post types for journal entries and workflows, plus taxonomies for topic, status and source, registered in a single PHP snippet through WPCode rather than assembled in a plugin UI. It is version-controlled, portable to another host, and exposes its fields to the REST API so agents can write to it. adopted
- Brand as a snippet, not a child themeFonts, CSS custom properties and the palette load from one snippet. A child theme would be the textbook answer; for a site with no template overrides it is more moving parts than the job needs. adopted
- Wikilinks and previewsYada Wiki resolves double-bracket links between notes and generates backlinks. Hover previews are the piece we are still choosing — Linkz.ai does exactly what we want, and a glossary plugin is the cheaper fallback. evaluated
- Performance and cachingLiteSpeed Cache on the host’s Advanced preset: minification, font-display optimisation, deferred JS, no CSS combining. The aggressive preset is faster on paper and breaks more. adopted
Sitemap, schema and indexing live in the SEO workflow rather than here.