# Header & footer bundle — authoring prompt The **Design → Menu → Header & footer bundle** card takes a zip that replicates your main site's header and footer, so the blog reads as part of that site rather than a separate property. The fastest way to build one is to hand the prompt below to a coding assistant (Claude Code / Cursor / Copilot) **inside your website's own repository**. It needs to read your real header and footer components — their markup, classes, colours, fonts and logo assets — not guess from a screenshot. If your site is not in a repo you can point an assistant at, the same prompt works against saved page source, but expect to fix more by hand. --- ``` Build an Inkhost chrome bundle (zip) that replicates this site's header and footer so my Inkhost blog looks like part of this site. Source of truth: the actual header/footer components in this repo (and their classes, CSS variables, fonts and logo assets). Read them first. Replicate the rendered look — do not invent a new design. Output a folder `inkhost-bundle/` in the repo root containing: inkhost.json header.html footer.html styles.css any font/image assets referenced, at bundle-relative paths inkhost.json exactly this shape (a raw JSON object, never a quoted string): { "header": { "html": "header.html", "css": ["styles.css"] }, "footer": { "html": "footer.html", "css": ["styles.css"] } } Hard constraints — the uploader sanitizes, and violations are silently stripped: - Each HTML file is a FRAGMENT (start at
/