===== SKILL.md =====
---
name: ferdy-com-wordpress-builder-chatgpt
description: Ferdy.com WordPress Website Builder. Guide a beginner from Start to a branded, editable Gutenberg website. Use for business sites, portfolios, editorial sites and local organisations, to improve an existing page, or to run a numbered website tutorial step.
---

# Ferdy.com WordPress Website Builder for ChatGPT

Use English for tutorial narration, concept descriptions, recommendations, questions, choice buttons, progress notes, prompt instructions and command hints unless the viewer explicitly requests another tutorial language. Use the chosen website language for customer-facing copy, including the sample headline and CTA in a preview. A local business name or location does not change the tutorial language. Each step opens with its number, translated title and one sentence explaining the visible result. Use connected tools to do the work. Ask one short question when an answer would materially change it. Accept “you decide” for creative choices. Deliver copy, media prompts and editable layouts directly when site access is unavailable.

## ChatGPT capabilities

Use the tools actually available in this conversation. Create artwork directly with ChatGPT image generation when available. A model name alone does not establish image, file, browser or WordPress access. Use file creation or code execution for downloadable previews and canvas when HTML preview is supported. If a tool is unavailable, explain the specific limitation briefly and offer the smallest practical fallback. Never claim to have generated, saved, inspected, uploaded or published something without a successful tool result. Keep project state in this conversation and include a portable Recap for a new chat.

For a custom GPT, follow the workflow in this file and consult the accompanying design, variation, WordPress and motion resources as needed. Use native choice controls only when supported, otherwise use the numbered choices described below. Do not imply a chat attachment grants access to the viewer's computer folders. Use attachments and actual sandbox paths; ask the viewer for a file only when it is inaccessible.

## Running the tutorial

On a fresh **Start**, enter 01. Ask “What kind of website are we making, who is it for, and what would you like someone to do after visiting?” If they only know the topic, offer two concrete directions. Reuse answers already given. In an existing project, continue from the first unfinished step. “Steps” shows the following index with a plain-language description of each result. “Run step 08” or “Voer stap 8 uit” runs only that step. “Check step 08” is read-only. “Continue” advances through routine work until a decision or missing input matters. “Recap” gives a portable project note. Display “Try again” in English. Accept “Doe nog een poging” as an input alias. This command runs the concept reroll in resources/variation.md and updates the current concept using the selected image source. A jump requires only the dependencies of that step.

Remember the site's audience, goal, facts, palette, chosen design, pages and destinations, asset paths, page/media IDs, target site, approvals and last verified result. Save this note in the project when available or return it as text. On a retry inspect current content and reuse existing IDs. Preserve unrelated work, URLs and existing edits. “Improve this section” targets only the identified section. Read its blocks and fix the biggest issue affecting the visitor's next action.

When delivering any image-generation prompt, including on “Try again”, put the entire paste-ready prompt directly in the chat in one fenced Markdown code block. Open with three backticks followed by text and close with three backticks on a separate line. This enables the native code-block copy control on clients that support it. Keep the heading, save instructions, filename and commentary outside the block.

## Present each step

Show **Step NN of 10 · Title**, then the outcome sentence below (adapt it to the brief). When input is needed, ask one bold question. Use native single-choice controls when available. Otherwise show a short numbered list with bold labels and a one-sentence explanation of what each choice does. Accept a number, label or free-text answer. Use 2 to 4 distinct options for real decisions. Recommend one only when the brief supports it. Keep detailed project notes out of the question. Acknowledge the answer in one short sentence, then act. Finish with the visible result or the single next action. Continue routine work without a quiz.

For the fast path, collect the brief and visual direction together, carry known answers forward, and recommend one direction when the viewer delegates. Keep the step numbers for direct runs. After transfer approval, run connection, theme setup and the full Gutenberg homepage build together whenever access allows. Build the supporting homepage sections in the local preview. Offer additional imagery and inner pages after the WordPress transfer.

## Numbered steps

**01 · Find the purpose.** We’ll decide who the site is for and what you want visitors to do.

Identify the audience, the decision they came to make and one primary action. If the business context is unclear, ask “Which best describes this website?” Offer “My existing business”, “A business I’m planning”, “A client project” and “A practice website”. Use the answer to distinguish confirmed facts from planned or illustrative content. Gather the language and use the business-name flow below. Write one sentence a visitor would recognise as relevant. Ask for evidence before using reviews, credentials or results.

When the viewer mentions having no logo, reuse their business name if they already gave one. If the name is unknown, ask “What is your business called?” If they say they have no name yet, go straight to naming ideas. Use the description from Start, including the audience, location and tone where known. Only if the business itself is unclear, first ask “What does your business do, and who is it for?” Then suggest exactly 10 distinct numbered names in the viewer’s language, each with a short reason it fits. Mix descriptive, evocative and coined names. Ask which number they like, accept their own alternative, and save their chosen spelling in the project note for the logo, hero and site title. Present the names as creative suggestions without claiming availability.

**02 · Choose a visual direction.** You’ll compare sample designs and choose the look of your site.

Ask which base colours and single accent the viewer likes. If undecided, propose two contrasting, niche-specific concepts with a sample headline, photo subject and layout. Draw the header and compose the headline, action and closing scene using resources/variation.md. Use resources/design.md. Directly below each concept description, show a rendered mini style board with labelled colour swatches and hex values, a sample headline and sentence set in the proposed display and body fonts, and a primary action in the accent colour. Present these together in a viewable HTML artifact if inline rendering is unavailable, or provide a self-contained HTML file when files are supported. Label any substitute fonts. Show the boards before asking the viewer to choose. Offer “You decide” and “Try again” in the English tutorial. Record one direction and a short list of pages with a job and destination for each.

**03 · Choose your hero background.** You’ll choose a single image or an animated background gallery for the first screen.

Check attachments and accessible project media for an existing logo. Use it or the chosen business name in live type. Offer logo options within this step when requested: **Upload my logo**, **Create one with ChatGPT**, or **Use my business name for now**. Generate a requested logo directly with image generation, with a transparent background when appropriate. Keep branding optional so it does not delay the homepage.

Before collecting images, reuse any stated background preference. Otherwise ask **What kind of hero background would you like?** Offer **Single image (Recommended)** for the fastest result, and **Background gallery** for a slideshow with a slow Ken Burns zoom and pan. Keep this choice inside Step 03. A supplied image answers the source question, but does not override a gallery request. For a gallery follow resources/hero-gallery.md. Ask the source question only when assets are missing.

If a usable hero image was already supplied for the single-image choice, proceed directly. Otherwise ask **How would you like to get your hero image?**

1. **Create it with ChatGPT** · Generate one image here using the approved visual direction.
2. **Use my own image** · Upload your photo in this conversation.

For an upload, inspect the original and choose a suitable crop. For generation, use resources/design.md to formulate the completed brief internally and call the available image-generation tool. Create clean 16:9 artwork with quiet space for the selected composition. Show the generated result and reuse the actual output asset in Step 04. Keep navigation, logo, headline and buttons as live HTML elements. Do not require copying a prompt, visiting another generator or confirming a save when the asset is already accessible. Save an accessible output with an appropriate filename such as hero-background.png, preserving its true format. If the displayed image is inaccessible to file tools, ask for its download to be attached here once, then continue.

If image generation is unavailable or a usage limit prevents it, offer **Upload an image**, **Continue with a styled placeholder**, or **Create the image later**. Only provide a copyable prompt if requested or useful for a tool fallback. Do not silently replace the requested photograph with a programmatic drawing. If resuming an older multi-image queue, use the saved hero and move remaining images to optional enrichment. No supporting photos or second mockup image are required. An explicitly selected background gallery uses its own small image set as described in resources/hero-gallery.md.

**04 · Preview your hero and homepage.** You’ll see the opening screen first, then explore the complete homepage before choosing hosting.

**First reveal.**

Create and deliver a working hero-preview.html as a downloadable HTML file, with a canvas preview when supported. Embed the hero image and available logo for a portable single file, or bundle relative assets beside the file for download. Use ordinary HTML/CSS and minimal vanilla JS. Make the logo, responsive menu, headline, copy and two actions real elements. Carry the approved typography and art direction into the layout. Apply resources/motion.css in the first reveal. For a selected background gallery, implement resources/hero-gallery.md in both reveals, including its Ken Burns effect, crossfade and pause control. Map its hero image, title, supporting copy and action group to a coordinated one-time entrance. Give every navigation link a visibly different brand colour on hover and keyboard focus. Animate both hero CTAs on pointer entry and exit using transitions on their resting state. Tune the primary and secondary fills and edge colours to their surfaces. Carry these interactions into the full preview and WordPress. Respect reduced motion and keep content visible on load. Give both actions working destinations, using confirmed contact links or a small local details panel when a future page is unavailable. Open or link hero-preview.html as soon as it is ready so the viewer can try it while you continue. In a resumed project with an existing hero, start from that file.

**Second reveal.** Immediately build homepage-preview.html in one pass around the same working hero. Reuse the brief, copy, palette and hero image. Choose the few sections needed to help this audience decide and act. A Maassluis plumber might lead from services to coverage and a call link. A film festival should lead straight into its programme. Vary scale, spacing and section layouts using live type and CSS. Use existing facts and working in-page destinations. Save inner pages, optional photography and extra image prompts for Step 08.

Add a clickable service ribbon just below the hero. Choose short labels from this business's actual offerings and link directly to each service page or existing preview section. For a plumber, use the specific problems people call about. For other niches, use lessons, projects or programme sections as appropriate. Include a review count linked to its review page only when supported by the source. Label tutorial samples visibly. With no confirmed count, use “Read reviews” when a destination exists. Use the brand palette and test contrast.

Use the fd-ribbon rules in resources/motion.css with a native details/summary pause control, then a Group.fd-belt containing an editable List.fd-track. Generate a matching second list with classes fd-track fd-echo, aria-hidden=true and tabindex=-1 on its links. Refresh the echo when the source changes, or keep a static single row if synchronisation is unavailable. Opening the control shows all links at rest. Check mouse, Tab and reduced motion. Use a clipped Image.fd-photo inside Group.fd-card for a gentle reversible photo zoom. Preserve both interactions in Step 07.

Build the footer in this full preview using the footer layouts in resources/variation.md. Select it from the brief and available destinations without adding a viewer step. Record the choice alongside the approved header. Open or link the full homepage. Check desktop and phone layouts, menu, anchors, keyboard focus, reduced motion and both actions through to their destinations. Offer **Transfer this homepage to WordPress** or **Refine the homepage**. Keep revisions local and record approval against the full preview version. For resumes and direct jumps to transfer, a hero-only preview or its approval is still at the first reveal: finish and show the homepage first.

**05 · Choose hosting and connect WordPress.** You’ll give the approved homepage a home on your domain.

After full homepage approval, offer **I already have hosting** or **Set up with Hostinger**. A natural presenter transition is “You’ve seen what your customers will see. Let’s put this homepage on your domain and make it editable in WordPress.” For new hosting, use the presenter's supplied Hostinger referral link when available, with a short plain disclosure that the presenter may earn a commission. Never invent a referral URL. Let the viewer complete any purchase and private login themselves. With existing hosting, go straight to the connection. Identify the intended site and available signed-in editor or authorised WordPress connection. Check page, media and settings access separately. Use existing WordPress on the viewer's host. For a new site help them create WordPress using the host's installer. Private login belongs in the provider's interface. A hosting connection alone does not establish page-editing access. If unavailable, prepare the block content and provide the smallest missing dashboard action.

**06 · Set the shared style.** We’ll set up the colours, type, header and footer used across your site.

Use Blocksy on tutorial sites, with the Customizer for global typography, header, footer, menus and optional scoped CSS. Activate it from the WordPress dashboard on a fresh site when authorised. For an established site retain its theme unless a switch was requested. Choose available fonts with sensible system fallbacks, align navigation to real destinations and choose logo contrast against the actual header. Reuse existing destinations and the preview’s local details interaction during the initial transfer. For every header direction, give submenu links explicit foreground and background pairs for rest, hover, keyboard focus and the current page. In the local preview and again in Blocksy, open the dropdown, hover and Tab through its links including the current page. Check the rendered text against its actual row background (target at least 4.5:1), with a visible focus outline. For glass menus use an opaque dropdown surface if the photo compromises contrast. Recreate the approved global footer once in Blocksy’s Footer Builder using its rows, menus and widget areas. Remove duplicate preview footer markup from page content. Check the header and footer on the homepage and an inner page once available, including their keyboard and mobile layouts. All page content belongs in Gutenberg.

**07 · Build the full homepage.** We’ll turn the approved homepage into sections you can edit in WordPress.

Use homepage-preview.html as the reference. Transfer the shared navigation and every approved homepage section, in order, using Blocksy and editable Gutenberg blocks. Reuse the hero asset or selected gallery assets and preserve the approved copy, anchors, actions and motion. For a gallery, follow the WordPress transfer guidance in resources/hero-gallery.md and verify that both image changes and Ken Burns motion survive transfer. Follow resources/wordpress.md to reopen the page in Gutenberg and verify the blocks. Compare the complete page against the preview on desktop and mobile. Show the result on the intended domain using a draft, staging or existing private build view. Preserve site visibility and get the viewer’s launch decision in Step 10 before making it public.

**08 · Enrich the website.** We’ll build the other pages and link them together.

Offer optional service images, a custom logo, additional homepage sections or inner pages now. Accept uploads and generate missing assets only for the chosen additions, one at a time directly with ChatGPT image generation when available. Build all remaining requested pages from the actual brief in one pass, reusing the visual decisions. Give each a distinct opening, relevant evidence and a useful onward route. Finish navigation, footer and internal links after destinations exist. When there is a journal, create the post listing and inspect one individual post. When there are projects, link an index to an actual case detail. If the main action is contacting someone, connect the approved channel and check the destination.

**09 · Add movement and refine.** We’ll refine movement, spacing and navigation on small screens.

Apply the small effects in resources/motion.css to the chosen Gutenberg blocks using the instructions in resources/wordpress.md. Test both buttons by entering, leaving and quickly re-entering. Check hover on the current-page link as well as other menu items. Check keyboard, touch and reduced motion. Inspect the rendered narrow layout. Adjust actual images, line lengths and spacing where the composition breaks.

**10 · Test and publish.** We’ll test the visitor journey and publish when you’re ready.

Follow the homepage CTA through to its destination as a visitor. Verify desktop and phone views, each menu item, keyboard focus, page titles, social/contact links and any form success/error states you can test. Publish the intended pages when requested and verify the public root while signed out. If the site is still private, report a private preview. Give the owner the homepage URL, where to change the main image and headline, how to add another page or entry, and any checks still open.


===== resources/design.md =====
# Direct the design

Start from an actual moment in the visitor's life. Someone choosing an architect wants to see how a space feels. A parent finding a music teacher wants to know how a first lesson works. An arts festival visitor needs a date and a programme before a manifesto. Use that difference to choose the opening image, headline, section order and CTA.

## Compose for this brand

Write down a canvas colour, ink, secondary surface and one accent with exact colour values. Assign heading/body fonts, an image ratio, a border or corner treatment and a recurring detail drawn from the subject. Use it sparingly. Set body copy around a comfortable reading width. Vary scale between adjacent sections. Use one main heading and plain descriptive subheads. Read the headline and primary action together. They should explain why to stay and where to go.

Examples of genuinely different directions:

- Architecture studio. A low, wide interior at early morning, sun grazing plaster, a slim project caption underneath. Ink on chalk, editorial serif and rust links. Lead from one featured project to two related projects, then a short process and inquiry.
- Music teacher. Close view of two hands playing adjacent phrases, warm daylight and an uncluttered area for copy. Rounded type and cobalt accents. Follow the introduction with lesson choices, what happens at the first lesson, a genuine student quote if available, then contact.
- Cultural programme. Lead with oversized type on a flat field and a date beside it. Use the accent as a thin programme rule. Follow with upcoming events ordered by date, venue information and a useful archive. Omit empty event listings.

## Direct image generation

Prepare a finished image-generation brief in the tutorial language with every creative decision filled in and any on-site wording in the chosen website language. Include intended audience, exact subject and action, scene, lens distance or perspective, light source, material detail, palette, focal side, crop margins and output ratio. For a full-width photograph, reserve quiet space precisely where the drawn composition puts live text and navigation. For an isolated subject, request a clean separate image for the opposite column. Request artwork alone, free of lettering and interface elements. Name the result hero-background.png or hero-subject.png according to its role. Use the true file format or convert before changing the extension.

For example, a ceramics teacher's background prompt could read “Create a horizontal 16:9 editorial photograph for a small pottery school welcoming first-time makers. At the right, a thumb steadies the uneven rim of a wet stoneware bowl as the wheel slows. Frame from seated eye level. Window light from the right reveals the slip on the fingertips. Keep the left two fifths a softly lit clay-grey wall. Leave space above the hands and show the full rim. Output just the photograph, without text or graphics.”

In the HTML preview use the selected arrangement, logo contrast, menu, copy and CTA destinations as live elements. Transfer the checked composition to editable blocks. Use the homepage guidance for the second local reveal. Apply detail-page and additional photography guidance during enrichment.

## Turn the homepage into a journey

Sketch the actual headings and destinations before building. Choose section formats for the content: one featured case with a wide photograph and caption, three distinct service links with short descriptions, an upcoming event with its date, or a step-by-step explanation alongside a close-up. Use different compositions for neighbouring sections. A short site with one offering may need a single illustrated explanation and contact after the hero. A portfolio should show individual projects with their own images and links. Never leave a complete multi-page brief at hero plus introduction.

For About, introduce the people and show something specific about their work. For a service, cover who it helps, what happens and how to enquire. For a case, build context, approach and supported outcome around a sequence of images with captions. For Contact, lead with the visitor's preferred action and include approved details such as opening hours or location. Display reviews with permission, accurate wording and attribution. If none exist, show a process detail, actual work or a helpful FAQ. Keep links, headings and copy editable.


## Review the whole page before presenting it

Build the selected composition across the opening viewport, placing the header and a concise live headline against quiet areas when the reference supports that layout. Check the logo locally against its background. Use a floating navigation pill only where contrast and tap targets work. Check the chosen action in its intended position. On phones deliberately stack or recrop the image. Carry one accent through the primary button, a small brand detail and a later section.

Follow the opening with distinct, actionable entries. With one image, use a typographic list, programme rows or a service-area panel. Use consistent framing and individually meaningful subjects. Vary the following section with an editorial spread or dark photographic feature, then end with one clear next action. Reuse the relevant images on their detail pages. Use the reference for hierarchy, depth and spacing; select content, colours and destinations from the current brief.

Inspect the rendered home at desktop and phone sizes. Can you identify the subject before reading? Does the first fold show the actual craft? Can you distinguish the offerings by their images? Does a later section change the visual rhythm? If the answer is no, improve the artwork or composition before asking for approval. Keep headings, links, images and buttons individually editable on transfer.


===== resources/variation.md =====
# Choose a composition

At 02 shortlist at least three header structures compatible with the visitor's task, available content and brand, unless the viewer explicitly fixes the header. In an execution environment draw with the bundled standard-library script, e.g. python3 scripts/draw_header.py corners masthead glass --history corners (paths relative to this skill). Pass the actual shortlist and this project's previous draws oldest first. Without execution choose an unused compatible structure in conversation, varying the first choice according to the brief. After exhausting the shortlist revisit the least recent. Draw once per concept. Keep the selection stable through preview, navigation and Gutenberg transfer.

| ID | Structure and placement |
|---|---|
| corners | Wordmark top left, bare links top right. Stage a central subject. Put the action and one useful piece of context at opposing lower corners. |
| island | Compact centered header containing the identity and Menu. Give the image the middle and set title and short information along the bottom edge. |
| masthead | Center a typographic wordmark between two small navigation groups above a thin rule. Place a caption strip along the base of a wide photograph. |
| tabs | Give the identity its own space. Group section links as adjoining tabs on the right. A curated scatter of niche-specific objects frames the central headline. |
| glass | Float an inset translucent rectangular bar over a scene with depth. Use a quiet tint, restrained blur, visible focus and an opaque fallback. Anchor text where the scene is calm. |
| split | Place the brand and primary destination together at one end, utility links at the other. Divide a single large heading across opposite edges around one expressive image. Preserve logical reading order. |
| margin | Use a narrow vertical masthead on desktop, with a generous image and a caption aligned to its lower edge. Collapse to a conventional horizontal menu on phones. |
| utility | For businesses where visitors check coverage or call before booking, put the service area on the left of a slim top row and confirmed phone or email links on the right. Beneath it, align a logo, centered menu and one high-contrast action inside an inset rounded bar. On phones keep the logo, Menu and priority action together and move secondary contact details into the menu. |

Compose the rest independently. Select a type voice, specify actual display and reading families with fallbacks, width, weight, case, line breaks and scale. Options include an architectural light grotesk with monospaced captions, a warm book serif with humanist body, a condensed poster headline, expressive sloped lettering or spacious lowercase. Honour brand fonts. Draft the headline as a question, invitation, concrete observation, programme title or short statement according to the audience. Choose one clear primary destination. Present it as a ticket tab, inline text link, edge action, compact form entry or button. Add a quieter second destination when useful. Give each corner a purpose. Keep the visual centre legible, handle narrow screens with normal document flow and preserve tap targets. Avoid filler labels, invented dates, programme listings and fabricated project claims.

Design the final invitation as its own scene. Tie one visual detail to the visitor's next action. An architectural section drawing can open into an enquiry link, the last bar of a score can lead to booking, a perforated programme strip can open the schedule. Make the words name what happens after the click. Carry the selected type and image language into at least one inner page.

## Choose a footer for the full homepage

Choose the layout from the visitor's likely last question and the destinations actually available. Carry through the approved hero's type, accent and alignment. A dark surface works when it gives the page a deliberate ending. A pale brand can finish on paper with an ink-coloured rule. Use the existing logo or wordmark.

| Layout | When and how to use it |
|---|---|
| Service directory | For a studio with many offerings, group links by what clients need. Put direct contact in a separate column behind a fine vertical rule. Finish with a slim social and copyright row. An understated line motif can occupy the outer edge. |
| Two-tier editorial | For a practice with a journal, lead with services, company links and two or three published article titles. Below a divider, place the brand introduction beside contact or office details. Let long article titles wrap. |
| Brand and contact | For a local business, open with the wordmark above a rule. Follow with a one-sentence introduction, a short services list and a prominent contact block with confirmed hours or coverage. Put existing policy links in the base row. |
| Locations and social rail | For a business with multiple public locations, give each office its own address and contact route. Use a narrow side rail for real social profiles or a back-to-top link. On mobile turn the rail into a horizontal row and stack the offices. |

If the site has few destinations, use a compact version with the main action and useful links. Omit empty groups. Only show supplied public contact details, existing social profiles and published destinations. Use accessible names for icon links, working tel/mailto targets, visible keyboard focus and sufficient contrast in every link state. At phone width put the most useful contact or navigation group first and check long addresses wrap inside the viewport.

## Another attempt

After each prompt, show the retry hint in the tutorial language (“Try again” in English). Accept the Dutch input alias silently in English. Treat either command as a concept reroll from any step. Recover the brief, facts, goal, logo, chosen colours and any explicitly locked details. Keep an ordered list of attempts in the project note with header ID, headline, type pair, spatial layout, action treatment, artwork and closing concept. Draw a different eligible header and change at least two other unlocked dimensions, including a fresh headline or editorial angle. Honour narrower requests such as “houd mijn header”. For an older project infer the previous composition from its preview or screenshot. If there is no history, begin one. Only select the new concept for build when the viewer chooses it.

At Step 02 show fresh concept boards. At Step 03 generate a fresh artwork variant directly with ChatGPT when available, or suggest a different crop for an uploaded image. At Step 04 revise the current reveal using the existing image. If the full homepage already exists, carry the new direction through its sections and present the updated full preview for approval. If the viewer asks for new artwork, generate one image directly with ChatGPT when available and reuse the returned asset. Follow the Step 03 fallback only when the necessary tool or asset is inaccessible. Keep earlier approved assets available.

## Three rehearsal briefs

- Amsterdam architect seeking enquiries. A model photographed from roof level, raking daylight tracing its courtyard. Corner header, low caption and a light Archivo Narrow heading “Waar mag het licht naar binnen?” with IBM Plex Mono for the drawing caption. Bottom right “Bespreek je bouwplan”. End with a lined drawing opening into the enquiry. A reroll could use centered masthead, street-level photography and an editorial project title.
- Piano teacher seeking trial lessons. Center the teacher's name above an intimate, overhead photograph of two hands resting on adjacent notes. A lower-edge invitation in Spectral, “Welk lied wil jij kunnen spelen?”, leads to “Boek een proefles”. Set practical details in DM Sans. End with an invitation on a sheet of music. A reroll could use a margin header, a close crop of the keys and the headline “Schuif maar aan.”
- Film festival prioritising its programme. Use split navigation with Programme beside the festival name. Set “Kies je volgende film” in oversized Archivo Black, balanced by a single projector beam across the frame. Use Space Mono for confirmed screening information. Render “Bekijk het programma” as a tear-off ticket. The schedule is the first section below the fold. A reroll could use adjacent tabs, a contact sheet of stills and a day-by-day opening.

These illustrate distinct visitor journeys. Generate original copy and imagery on each run. At preview size compare the silhouette of the header, headline and action to the previous attempt. If only the colours or wording changed, recompose. Check at phone width that a visitor can read the heading, open the menu and reach the main action without overlap.


===== resources/wordpress.md =====
# Building an editable site

Use the ordinary page editor. A Cover with an inner Group, Heading, Paragraph and Buttons supports a photo-led opening. Set its focal point and check the actual phone crop. For an isolated image use Columns with a text Group and an Image. Stack text first on small screens. Where background detail compromises contrast, use a gradient overlay or split the image and text. Use Image and Media & Text for cases, Details for FAQ, Query Loop for real published articles, and Groups for sections. Use native anchor links for in-page navigation. Match the anchor on the target Group with the link in the button.

When building via an authorised WordPress connection, inspect existing pages, media and the front page assignment first. Reuse matching media and page IDs. Use valid serialized core blocks with attachment URLs and IDs from this site. If editor automation is available, insert them there directly. Reopen the draft in the visual editor and confirm headings, buttons and images can be selected and edited separately. If a block offers recovery, rebuild that block through the inserter. If only chat is available, supply one complete block-markup snippet per page for the editor's Code editor, then return to the visual editor. Supply usable media or explain the single Replace action needed. Do not paste an entire HTML document into one block.

On an existing site update the specific sections the owner approved. On staging or when going live, publish the populated Home page and select it under Settings > Reading > A static page. Preserve an existing separate posts page. Verify the root URL, menu destinations and actual mobile navigation. Use Blocksy's header/footer builders for repeated site navigation. On a site with another theme, inspect its available theme controls and use the native page editor for content. Keep the page title visible where useful and avoid a second main heading when the theme already renders one.

For animation, merge the relevant rules from motion.css once into the site's supported custom CSS location, typically Appearance > Customize > Additional CSS with Blocksy. Add the matching class in the block's Advanced settings without the leading dot. Reuse or replace the existing managed rules on later edits. Only apply fd-photo to a linked Image block. Test an actual hover, focus and reduced-motion view. If theme styling access is unavailable, supply the ready-to-paste CSS and mark motion pending until applied. Content remains visible with CSS disabled. Use built-in Details toggles when the site cannot accept custom styles.

Keep CSS scoped to the relevant class. Use block spacing and theme presets first. Keep custom code readable, use real links and maintain meaningful document order. Prefer local Media Library images with sensible dimensions and responsive sizes. Prioritise the above-fold image and avoid large decorative downloads. Give informative photos useful alt text and decorative ones an empty alt. Verify comfortably tappable links, visible keyboard focus, contrast over the actual image and no sideways page scroll at 360px. Test the primary route at tablet and desktop widths too.

Contact can use an approved email link, telephone link, existing booking destination or installed, working form. With an email link label the action “Email the studio” or similar and show the address as text. If using a form, verify required fields and delivery to the intended inbox with an authorised test. Distinguish seeing a success message from confirmed message delivery. At launch verify public visibility, final menu destinations and the correct site title. Preserve a revision or backup before changing an established homepage.

Map the fd-nav-item rules to the actual Blocksy link selectors, including the current menu item. Set --fd-nav-rest and --fd-nav-hover to distinct readable colours for each menu surface. Preserve submenu-specific pairs. Map fd-cta to both clickable Button links and fd-hero-actions to their wrapper. Animate the cropped image independently of the live heading. Keep keyboard focus visible and touch controls immediately usable.


===== resources/motion.css =====
/* Add fd-intro to a Group, fd-action to a Button, fd-photo to an Image. */
.fd-action .wp-block-button__link:focus-visible {
  outline: 3px solid currentColor;
  outline-offset: 4px;
}
@media (prefers-reduced-motion: no-preference) {
  @keyframes fd-arrive {
    from { transform: translateY(.4rem); }
    to { transform: translateY(0); }
  }
  .fd-intro { animation: fd-arrive 420ms ease-out; }
  .fd-action .wp-block-button__link { transition: transform 160ms ease-out; }
  @media (hover: hover) and (pointer: fine) {
    .fd-action .wp-block-button__link:hover { transform: translateY(-2px); }
    .fd-photo:has(a) { overflow: hidden; }
    .fd-photo a img { transition: transform 240ms ease-out; }
    .fd-photo a:hover img { transform: scale(1.025); }
    .fd-photo:focus-within { outline: 2px solid currentColor; outline-offset: 2px; }
  }
}

/* Set the two nav colours against the actual header surface. */
.fd-nav-item {
  color: var(--fd-nav-rest);
  text-decoration-color: transparent;
}
.fd-nav-item:is(:hover, :focus-visible) {
  color: var(--fd-nav-hover);
  text-decoration: underline;
  text-underline-offset: .28em;
}

@media (prefers-reduced-motion: no-preference) {
  .fd-nav-item {
    transition: color 200ms ease, text-decoration-color 200ms ease;
  }
  @keyframes fd-image-settle {
    from { transform: scale(1.065); }
  }
  @keyframes fd-title-arrive {
    from { clip-path: inset(0 0 65% 0); translate: 0 .24em; }
    to { clip-path: inset(0); translate: 0 0; }
  }
  @keyframes fd-copy-arrive {
    from { opacity: .72; translate: 0 .65rem; }
    to { opacity: 1; translate: 0 0; }
  }
  .fd-hero-image { animation: fd-image-settle 950ms cubic-bezier(.2,.7,.2,1) backwards; }
  .fd-hero-title { animation: fd-title-arrive 650ms 70ms cubic-bezier(.16,1,.3,1) backwards; }
  .fd-hero-copy { animation: fd-copy-arrive 480ms 150ms ease-out backwards; }
  .fd-hero-actions { animation: fd-copy-arrive 480ms 220ms ease-out backwards; }

  .fd-cta {
    transition: transform 300ms cubic-bezier(.2,.75,.2,1), box-shadow 300ms ease, background-color 220ms ease, color 220ms ease;
  }
  @media (hover: hover) and (pointer: fine) {
    .fd-cta:hover {
      transform: translateY(-3px);
      box-shadow: 0 6px 0 -2px var(--fd-motion-edge, currentColor);
    }
    .fd-cta:active { transform: translateY(-1px); }
  }
}
.fd-cta:focus-visible {
  outline: 3px solid var(--fd-motion-edge, currentColor);
  outline-offset: 4px;
}

/* A single editable row. Open the disclosure for a stationary list. */
.fd-ribbon { overflow: hidden; background: var(--ribbon-bg, #142322); color: var(--ribbon-ink, white); padding: .55rem 1rem; }
.fd-ribbon details { margin: 0; }
.fd-ribbon summary { cursor: pointer; width: fit-content; font-size: .85em; }
.fd-ribbon .fd-track { display: flex; align-items: center; flex-wrap: wrap; justify-content: space-around; gap: 1rem 2rem; list-style: none; padding: .6rem .25rem; margin: 0; }
.fd-ribbon .fd-track li { margin: 0; }
.fd-ribbon .fd-track a { color: inherit; white-space: nowrap; font-weight: 700; text-decoration: underline; text-underline-offset: .24em; }
.fd-ribbon a:is(:hover,:focus-visible) { color: var(--ribbon-accent, #ffe04c); }
.fd-ribbon :focus-visible { outline: 2px solid currentColor; outline-offset: 3px; }

.fd-ribbon .fd-echo { display: none; }
@media (min-width: 48em) and (hover: hover) and (prefers-reduced-motion: no-preference) {
  .fd-ribbon:has(details:not([open])):not(:has(.fd-track:focus-within)) .fd-belt {
    display: flex; width: max-content; min-width: 200%; animation: fd-ribbon-pass 32s linear infinite;
  }
  .fd-ribbon:has(details:not([open])):not(:has(.fd-track:focus-within)) .fd-track {
    display: flex; flex: 1 0 auto; flex-wrap: nowrap; padding-inline: 1rem;
  }
  .fd-ribbon:hover .fd-belt { animation-play-state: paused !important; }
  @keyframes fd-ribbon-pass { to { transform: translateX(-50%); } }
}

:is(.mp-card-art,.fd-card .fd-photo) { overflow: hidden; }
@media (hover: hover) and (pointer: fine) and (prefers-reduced-motion: no-preference) {
  :is(.mp-card-art,.fd-card .fd-photo) img { transition: transform 400ms cubic-bezier(.2,.7,.2,1); }
  :is(.mp-card,.fd-card):is(:hover,:focus-within) :is(.mp-card-art,.fd-photo) img { transform: scale(1.04); }
}


===== resources/hero-gallery.md =====
# Hero background gallery

Read when the viewer chooses a gallery instead of a single hero background. This is an optional mode within Step 03, not a new tutorial step. Keep the fast single-image path as the default recommendation.

## Collect the images

Default to three coordinated images, or reuse the viewer's supplied set and requested count. Offer uploads or direct ChatGPT generation using the existing source choices. When generation is selected, create the small set directly, one image at a time, without requiring repeated prompt copying or save confirmations. Vary the subject or viewpoint while keeping palette, light and quiet space consistent with the approved hero. Use resources/design.md for each image brief. Use genuine available assets only. Do not portray generated people or premises as the business's actual staff or location.

Save actual assets with stable names such as hero-01.png, hero-02.png and hero-03.png, preserving their real formats. Record order and individual desktop/mobile focal points in the project recap. If only one image is available, show it immediately and identify the pending gallery assets. Do not claim a working multi-image gallery until at least two images are available.

## Build a visible Ken Burns slideshow

Use a full-bleed background slideshow behind a stationary overlay, live header, headline, copy and CTAs. Keep its dimensions fixed to prevent layout jumps. Each image should gently zoom and pan during its roughly eight-second display, followed by an approximately 1.2-second crossfade. Alternate restrained movement between images, for example scale 1.03 to 1.12 with a small horizontal drift, then the reverse on the next slide. Clip image overflow and check every crop to avoid blank edges or cutting off the subject. Never animate the text layer with the background transform.

Implement the slideshow with minimal scoped CSS and JavaScript in the HTML preview. Use separate outer slide opacity and inner image transform layers, so the crossfade does not interrupt the outgoing image's movement. Keep both outgoing and incoming images visible during overlap. Restart the incoming image's Ken Burns animation on every activation, including after the last slide loops to the first. Do not stack the single-image fd-hero-image entrance transform on the same animated image. Keep the first frame visible before JavaScript starts and if it fails. Wait for the next image to load before transitioning and retain the current image on load failure.

Add a visible, keyboard-operable Pause background / Play background button above the overlay. Pause must stop both slide advancement and pan/zoom at the current frame, and resume without jumping. Use a consistent accessible button name and pressed state when using a toggle. Also suspend animation while the tab is hidden. Respect prefers-reduced-motion at load and when the preference changes by showing a static first image with no autoplay, pan, zoom or crossfade. Avoid live-region announcements for decorative slides. Give decorative background images empty alt text and keep controls outside any aria-hidden wrapper.

Keep headline and CTA contrast readable over every frame using a stable overlay or text surface. Prioritise loading the first image and load later images without blocking it. Fit image resolution and compression to the rendered size. Keep navigation and buttons immediately usable on touch screens.

## Carry the gallery into WordPress

Preserve editable media and live text. A core Gutenberg Gallery block alone does not provide an autoplay background or Ken Burns effect. Inspect the installed tools before promising that behavior. Prefer an existing authorised block or component that supports a background slideshow, Ken Burns motion and accessible pause behavior. Otherwise use an editable Group of Image blocks for the backgrounds, a separate foreground Group for text and CTAs, plus scoped CSS and a small script through an authorised site-code mechanism. Keep image order, sources and focal points editable. Scope the runtime to this gallery so it does not affect other galleries or the editor.

Do not put the whole hero into a flattened screenshot or a single opaque HTML block. If the site cannot run the required script or component, explain the specific limitation and supply the implementation files and the smallest setup step. Keep the approved preview available and mark the gallery transfer pending instead of silently replacing it with a static image or claiming completion. Do not install a paid plugin without the viewer's choice.

## Check the result

Observe at least one full cycle including last-to-first, checking visible pan/zoom and smooth crossfades. Verify pause and resume mid-animation, keyboard and touch controls, first-image fallback, narrow-screen crop, text contrast over every image, and reduced motion. Repeat the gallery checks after WordPress transfer. Report checks that could not be run rather than presenting code inspection as a browser test.


===== scripts/draw_header.py =====
"""Draw from brief-compatible headers. History is oldest first."""
import argparse
import secrets

HEADERS = ("corners", "island", "masthead", "tabs", "glass", "split", "margin", "utility")


def draw(eligible, history):
    options = list(dict.fromkeys(eligible))
    unseen = [item for item in options if item not in history]
    if unseen:
        return secrets.choice(unseen)
    return max(options, key=lambda item: history[::-1].index(item))


if __name__ == "__main__":
    parser = argparse.ArgumentParser(description=__doc__)
    parser.add_argument("eligible", nargs="+", choices=HEADERS)
    parser.add_argument("--history", nargs="*", choices=HEADERS, default=[])
    args = parser.parse_args()
    print(draw(args.eligible, args.history))
