# Website project brief: a bicycle repair shop

Start with one visitor goal: requesting a repair quote. This fictional bicycle repair shop brief defines three pages, a clear contact action and the checks to run before launch. Replace the placeholders with information you can verify.

## Scope for the first version

### Home: help visitors decide

Explain which bikes the shop repairs, where it operates and how to request a quote. Use approved photos and opening hours. Leave prices, customer reviews and credentials out until the owner supplies them.

### Services: explain the work

Describe puncture repairs, brake adjustments and routine servicing. Mark the service list as example content until it is confirmed. Make the quote action reachable from each service; do not promise a fixed price or turnaround without evidence.

### Contact: make the next step clear

Use placeholders for the public phone number, location and email address. A form should validate required fields and show a clear demo message until a real submission service is connected. It must not claim a message was sent when it was not.

## Prompt to adapt

Create a responsive three-page website for a fictional bicycle repair shop: Home, Services and Contact. The visitor goal is to request a repair quote. Use placeholders [shop name], [city], [public phone], [public email] and [opening hours]. Add clear navigation, a service list and a quote action on each page. Label service descriptions as example content until the owner approves them. Do not invent reviews, prices, certifications, repair times or customer results. Keep the contact form in demo mode: validate name, email and repair details, then explain that nothing was sent. Do not store submitted details or call an external service in this prototype. Use labelled fields, visible keyboard focus, readable contrast and a mobile menu that opens and closes. Include a useful page title and description for each page. Generate the first version, then identify what must be configured and tested before launch. Do not add payments, accounts or booking automation.

## Usage notice

Choosing an example or downloading a brief uses no AI allowance. Starting a build or asking for changes uses your account's applicable plan usage or credits. Check your plan and available usage before you start.

## Checks to run before launch

### Follow the visitor journey

Open each page and follow every quote link. Check the mobile menu at 390px wide and a desktop layout. Navigation should reach the intended page, with no hidden buttons or horizontal overflow.

### Test the contact form honestly

Try an empty form, an invalid email and a valid example. The first two should explain what needs fixing; the last must say it is a demo and that nothing was sent. Connect a real service separately, then confirm delivery and failure handling before accepting customer messages.

### Use the keyboard and inspect the content

Tab through the menu, links and form. Focus should stay visible and fields should have labels. Replace every placeholder and verify the services, hours and images with the business owner.

### Prepare the published site

Review unique page titles, descriptions, one main heading per page, canonical URLs, a sitemap and image sizes on the actual hosting domain. Confirm HTTPS and any data handling notice needed for the connected form. A preview alone does not verify these launch requirements.

## Owner checklist

Replace [shop name], [city], [public phone], [public email] and [opening hours]. Supply approved photos and service descriptions. Keep the contact form in demo mode until delivery, failure handling and data handling have been checked. This checklist describes expected behavior; it is not evidence that a generated site has passed testing.

## Next steps

- AI coding assistant for source review: https://brainbaby.ai/coding
- AI for small business workflows: https://brainbaby.ai/for-companies
- Compare plans and builder allowances: https://brainbaby.ai/pricing

## About this resource

An original Brainbaby planning resource. It is not source code, a working app or a published website. Free to adapt under CC BY 4.0: https://creativecommons.org/licenses/by/4.0/
