Open Claude Code in your own website's project folder, then copy this prompt and paste it in. It rebuilds the layout and interface only: your existing colours, fonts, logo and voice are kept, and this template's palette is used only if your site has no branding yet.
Rebuild the layout and interface of my blog as a reading-first journal with a listing page and a long-form article page, following the structure of a blog template I am copying.
Live template to study: https://templateinterface.com/templates/blog-article/
Before writing any code, open that link and read through it in detail. Analyse the rendered page and the other pages it links to and its source files in the same folder (https://templateinterface.com/templates/blog-article/index.html, https://templateinterface.com/templates/blog-article/article.html, https://templateinterface.com/templates/blog-article/styles.css and https://templateinterface.com/templates/blog-article/script.js): the section order, the layout grid and breakpoints, every component, the spacing and type scale, each interactive state, and how the script behaves. Summarise what you found before you start. Treat the live template as the source of truth for layout and interface, and the notes below as a summary of it. It is not a source of branding: the branding rule still applies. If the link cannot be loaded, say so and work from the description below.
Branding rule, which overrides anything below: this template supplies layout and interface only. If my site already has branding (colours, logo, typefaces, icon style, photography, tone of voice), keep all of it exactly. Read my existing stylesheets and pages first, list the brand colours and fonts you found, and map them onto the roles this layout needs (background, surface, text, muted text, accent, accent on hover, border, success, error). Where a role has no brand colour, derive one from the brand palette rather than borrowing the template's. Check that every text and control pairing still meets WCAG AA contrast with my colours and adjust shade, not hue, if one fails. Only if my site has no branding at all, use the palette and type described in the design direction below.
Page structure, in order:
- Listing page header: a masthead with the journal's name and a short promise, and a few section links.
- Featured essay: one large card with category, title, standfirst, author and reading time.
- Latest essays: topic filter buttons with a live count of posts shown, over a grid of post cards, with an empty state.
- About: two or three sentences on who writes the journal and why.
- Subscribe: an email form on a dark band, with a visible label and a note on how often you send.
- Article page: a reading progress bar, the article header (category, title, standfirst, byline, date, reading time) and a cover band.
- Article body beside a contents sidebar that marks the section being read: a lead paragraph with a drop cap, pullquote, lists, a figure with a caption, a code sample, a note and an author box.
- Newer and older article links, then the footer.
Design direction (use this palette only if my site has no branding):
- Warm off-white paper (#faf7f2), near-black ink (#1d1b18) and one editorial red (#b3261e) for links and small labels.
- A book serif for headlines and body text (Charter, falling back to Cambria or Georgia) at a comfortable 18 to 20px, with a line length of about 65 characters.
- Drawn cover shapes in a few muted colours instead of stock photos.
Behaviour:
- Topic filters show and hide cards in place, update the count and say so in a status line.
- The contents sidebar highlights the section in view and collapses into a disclosure on narrow screens.
- The reading progress bar is decorative and hidden from assistive technology.
- The subscribe form validates the email inline and shows a demo notice if there is no backend.
- A sun or moon button in the header switches between dark and light mode. Derive both modes from my site's branding, open in dark mode by default, remember the choice, and set it before the first paint so the page never flashes the wrong mode.
Build rules:
- Plain HTML, CSS and JavaScript. No framework, build step or external resources unless my project already uses them, in which case follow its conventions.
- Mobile first: one column at 320px with no horizontal scrolling, widening at breakpoints that suit the content.
- Semantic landmarks (header, nav, main, footer), one h1, headings in order, visible labels on every field, and a visible focus style on every control.
- Every interactive state (hover, focus, active, disabled, selected, error, empty, loading or success) is designed, not left to browser defaults.
- Respect prefers-reduced-motion.
- Any form without a real backend says so visibly when submitted instead of pretending to send.
- Use my real content. Where you have none, write short, clearly marked placeholder copy for me to replace, never invented facts presented as real.
When you finish, check the page at 375px and 1440px, confirm there are no console errors, and list anything you could not keep from my branding.