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 community's home page as a forum front page with a thread list and an in-place thread reader, following the structure of a community forum template I am copying.
Live template to study: https://templateinterface.com/templates/community-forum/
Before writing any code, open that link and read through it in detail. Analyse the rendered page and its source files in the same folder (https://templateinterface.com/templates/community-forum/index.html, https://templateinterface.com/templates/community-forum/styles.css and https://templateinterface.com/templates/community-forum/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:
- Header: logo, section links, a Start a thread button and the signed-in member; sticky.
- Welcome band: the community's pitch and three figures (members, threads, answers).
- Three columns on wide screens: categories on the left; the thread list in the middle; community extras on the right.
- Thread list: search, a Latest, Most liked and Unanswered switch, thread cards with tags, an excerpt, last activity, reply and like counts, and an empty state.
- Thread reader that replaces the list in place: a bar with All threads and Follow, the original post, replies nested one level with collapse buttons, an accepted answer marked, likes, and a reply form.
- Side column: a featured event or challenge card, the most helpful members, and the house rules.
- A compose dialog for new threads, and a footer.
Design direction (use this palette only if my site has no branding):
- Warm flour-cream ground (#faf4ea), dark plum-brown ink (#2a1a24) and a deep plum accent (#6b2a5e), with soft colour washes for category tags.
- A book serif for headings (Iowan Old Style or Palatino) and a system sans for posts and controls.
- Rounded cards with a soft shadow and drawn photo placeholders.
Behaviour:
- Category, search and sort combine on one list and announce the result count.
- Opening a thread moves focus to its title, and All threads returns focus to the card that opened it.
- Likes toggle with aria-pressed and update the count. The compose form is a native dialog with inline validation.
- Posting 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.