A GOOD PLACE TO BEGIN

A little clarity.
A better first version.

You don’t need a perfect specification. A few thoughtful details can give your idea a much more useful starting point.

A FIELD GUIDE TO YOUR FIRST BRIEF

Tell the builder what matters.

Think of your first prompt as a short introduction to the project. Make these five things clear:

  1. Who is it for?Describe the people who will use the site and what they already know.
  2. What should it do?Choose the main action or question the website needs to help with.
  3. What belongs on it?List the essential pages and the content you already have.
  4. What should it feel like?Give a visual direction: calm and editorial, playful and colourful, or precise and practical.
  5. What are the constraints?Mention accessibility needs, mobile use, required technology, and anything the builder should avoid inventing.
“Create a website for an independent furniture maker. Visitors should be able to explore three collections and learn about the materials. Include Home, Collections, and About pages. Use warm neutrals, generous spacing, and clear type. Make it work well on mobile. Use labelled placeholder images until I provide the photography.”

After the first version, request one meaningful change at a time. “Make the collection descriptions easier to scan” gives you a clearer result to review than “make everything better.”

01 / KEEP EXPLORING

Understand the workflow

Follow an idea from the initial brief through the preview, refinement, and review.

Take the walkthrough
02 / KEEP EXPLORING

Know your project

Learn why readable source, Git history, and project downloads matter after the first build.

Explore source and history
03 / KEEP EXPLORING

Plan the next step

Get a sense of what to check before a project moves from a private preview to the public web.

Read about publishing