Build a website
Go from a clear brief to a tested public site.
Reviewed 6 October 2026 · 2 min read
Before you start
Decide whether you need a content site, interactive app or shop. Accounts, payments and persistent data add backend requirements.
Provide the existing repository or request a new project. Name the hosting destination and whether publishing is included.
Step by step
- Write a brief covering audience, pages, primary action, content and visual references.
- Build the key page and responsive navigation first, using real copy.
- Add forms, data handling and validation. Keep secrets on the server.
- Test links, keyboard use, mobile layouts, form errors, persistence and access controls.
- Build for production, deploy through the selected hosting workflow, and verify public URLs while signed out.
Try this
Create a small portfolio with Work, About and Contact pages. Use my supplied content. Make phone navigation work without hover. Validate the contact form and explain how messages are delivered. Test public navigation and a failed submission.
Check the result
- Every link and form has a real destination or clear unavailable state.
- Direct visits and refreshes work on nested URLs.
- The public site works without a private network or signed-in browser.
- Metadata, image descriptions and readable error pages are present.
If something goes wrong
For redirect loops, inspect the exact URL and redirect chain, including HTTPS and trailing slashes. Do not keep adding redirects blindly.
A successful build does not prove the deployed server serves new files. Check real content and interactions after deployment.