Marketing Site Operations (www.wikantik.com)

The marketing site is ~20 static HTML pages living in the wikantik repo's marketing/ directory — no build step, no framework. nginx on the cloudflare host serves the deployed bundle; Cloudflare tunnels expose it.

Layout

• index.html, platform/ (feature deep-dives), compare/ (alternative pages), enterprise/ (SSO/SCIM/audit/RBAC/self-hosting pages)
• templates/page.template.html — the skeleton for new pages (head/meta/OG/JSON-LD structure)
• assets/, styles.css, robots.txt, sitemap.xml, ads.txt
• verified-wiki-links.json — the outbound wiki-link allowlist: every wiki URL used on marketing pages, added only after confirming a live 200. This is the guard against marketing pages linking 404ing or renamed wiki pages.
• form-backend/, form-helper.mjs, test/ — dev-only; excluded from the deployed bundle by the deploy script's allowlist

Page conventions

• <title>, meta description, OG/Twitter titles, and the JSON-LD headline must stay consistent when retitling — there are four places to change, not one.
• SEO targeting is data-driven: check the webmaster_* metrics for the queries a page shows for before wordsmithing (see Search Visibility Exporter).
• Cross-linking to the wiki is encouraged (inbound link equity for wiki pages) — through the allowlist convention only.

Deploy

bin/deploy-marketing.sh rsyncs the allowlisted bundle to a staging dir on the host, then copies into /var/www/www.wikantik.com under interactive sudo and chowns to www-data. A human must run it — from a Claude session, ! bin/deploy-marketing.sh. --dry-run previews. It verifies on-origin via :8000 afterward.

See Also

• Web Properties Hub
• Host: cloudflare — Static Sites and Tunnel Origin