# Website Starter Kit

Plan and build landing pages, business sites, portfolios, blogs, and documentation sites with strong navigation, search visibility, accessibility, and performance.

## Best For

This kit is for a project such as **Northstar Studio, a five-page service website with case studies and a qualified-lead contact form**. Use it when the main outcome is best described as a website project. If the idea combines several types, start with the [Custom Project Starter Kit](../15%20-%20Custom%20Project%20Starter%20Kit/README.md), decide which product pattern dominates, and then return here.

## Quick Start

1. Replace **[PROJECT NAME]** with the working product name and **[PROJECT DESCRIPTION]** with a two-sentence explanation of who it helps and what it enables.
2. Complete [Project Overview](Project%20Overview.md), [Idea Validation](Idea%20Validation.md), and [Target Users](Target%20Users.md). Record evidence separately from assumptions.
3. Rank the ideas in [Feature Planning](Feature%20Planning.md) and freeze the first release in [MVP Scope](MVP%20Scope.md).
4. Complete the [Full PRD Template](Full%20PRD%20Template.md) and make explicit decisions in the design and technical files.
5. Paste the completed planning files plus [Master Build Prompt](Master%20Build%20Prompt.md) into the coding tool. Ask it to pause after its understanding summary if anything important conflicts.
6. Use the testing, deployment, launch, and completion documents as release gates.

## What a Strong Website Project Proves

- [ ] A target user can understand the offer within ten seconds.
- [ ] A target user can reach any primary page in two navigation actions.
- [ ] A target user can submit a contact request with clear confirmation.

## Suggested First-Release Boundary

- home page
- one reusable content template
- about or proof page
- contact path
- responsive navigation
- basic SEO, accessibility, analytics, and performance checks

Defer these until evidence supports expansion: CMS authoring, multilingual content, site search, personalization, advanced experimentation.

## Core Files

- [Project Overview](Project%20Overview.md)
- [Idea Validation](Idea%20Validation.md)
- [Target Users](Target%20Users.md)
- [Problem and Solution](Problem%20and%20Solution.md)
- [Feature Planning](Feature%20Planning.md)
- [MVP Scope](MVP%20Scope.md)
- [Full PRD Template](Full%20PRD%20Template.md)
- [User Stories](User%20Stories.md)
- [User Flow](User%20Flow.md)
- [Information Architecture](Information%20Architecture.md)
- [UI UX Design Brief](UI%20UX%20Design%20Brief.md)
- [Design System](Design%20System.md)
- [Technical Architecture](Technical%20Architecture.md)
- [Recommended Tech Stack](Recommended%20Tech%20Stack.md)
- [Database Plan](Database%20Plan.md)
- [API Plan](API%20Plan.md)
- [Security and Privacy](Security%20and%20Privacy.md)
- [Development Roadmap](Development%20Roadmap.md)
- [Master Build Prompt](Master%20Build%20Prompt.md)
- [Frontend Build Prompt](Frontend%20Build%20Prompt.md)
- [Backend Build Prompt](Backend%20Build%20Prompt.md)
- [Testing Prompt](Testing%20Prompt.md)
- [Debugging Prompt](Debugging%20Prompt.md)
- [Deployment Guide](Deployment%20Guide.md)
- [Launch Checklist](Launch%20Checklist.md)
- [Improvement Roadmap](Improvement%20Roadmap.md)
- [Project Completion Checklist](Project%20Completion%20Checklist.md)

## Working Rules

- Write a measurable outcome before selecting technology.
- Label uncertain statements as **Assumption**, then assign a validation action.
- Do not add a feature to the MVP without a user story, acceptance criteria, and an owner.
- Sample names, data, prices, results, and credentials must be marked as examples; never present them as live truth.
- Keep the first release small enough to test end to end.

## Definition of Ready

The project is ready for implementation when the primary user, core problem, first-release flow, data boundaries, security risks, technical approach, test plan, and deployment owner are all documented. Continue with the [Master Build Prompt](Master%20Build%20Prompt.md) only after those decisions are coherent.