<!--
IndexTitle: Sample User Journey
IndexDescription: Example journey from rough ideas to first framework-neutral website page drafts.
IndexType: Setup
IndexStatus: Draft
LastEdited: 2026-05-23
-->

# Sample User Journey

Read `UserSetupGuide.md` first if you want the full beginner guide. Use this file when you want a quick example of the method in motion. Use `TemplateGuidance.md` when you want to copy the method into another repository.

## Overview

This journey shows how a beginner can move from rough ideas to first website page drafts without choosing a website framework too early.

The repository becomes the source of truth: it stores the user's decisions, prompts, drafts, reviews, open questions, and next tasks.

## Example User Scenario

The user is a solo consultant with scattered notes about services, audience, and past work. They want a practical web presence but do not know what the homepage should say yet.

They have:

- A rough business idea.
- A few service notes.
- Some examples of previous work.
- No final website platform decision.
- A willingness to work in small local passes.

## Step-By-Step Journey

1. **Start with repository orientation.**
   The user or agent reads `AGENTS.md`, `README.md`, `Plans/UserSetupGuide.md`, and `Plans/TemplateGuidance.md`.

2. **Run the discovery prompt.**
   The user copies `Plans/UserDiscoveryPrompt.md` and answers with whatever they know. The goal is not perfect language. The goal is usable source material.

3. **Save the first decisions.**
   The agent turns the discovery output into short Markdown notes for identity, audience, offer, proof, tone, and first pages.

4. **Collect non-blocking questions.**
   If a decision matters but does not block the immediate work, the agent adds it to `Plans/OpenQuestions.md`.

5. **Draft the first page set.**
   The agent creates or updates plain Markdown page drafts under `Content/Website/Pages`. The first page set can include Home, Start Here, How It Works, Offers, and About.

6. **Keep content framework-neutral.**
   The drafts avoid framework syntax, styling decisions, dependencies, deployment notes, or theme assumptions.

7. **Review before editing.**
   The agent reviews the drafts for clarity, credibility, completeness, tone, unsupported claims, and practical next steps before making a larger rewrite.

8. **Refine one focused area.**
   The user or agent picks one small improvement, such as clarifying the homepage call to action or tightening the offer language.

9. **Use local-first workflow.**
   Work stays local during draft passes. Commit, push, and sync happen at meaningful milestones, not after every tiny edit.

10. **End with a copy-ready handoff.**
    The agent reports only the summary, files changed, planning files to review, questions added or changed, and next recommended task.

## Files The User Interacts With

- `AGENTS.md` - repository rules for agents and maintainers.
- `README.md` - project identity and structure.
- `Plans/UserSetupGuide.md` - beginner workflow guide.
- `Plans/TemplateGuidance.md` - how to copy the method into another repository.
- `Plans/UserDiscoveryPrompt.md` - discovery prompt for identity, audience, offer, proof, tone, pages, assets, and next steps.
- `Plans/OpenQuestions.md` - batched human decisions.
- `Content/Website/Pages/Index.md` - page draft overview and rules.
- `Content/Website/Pages` - framework-neutral website source drafts.

## What The Agent Does

- Reads the repository instructions before editing.
- Keeps the pass small and focused.
- Turns rough user answers into structured Markdown.
- Adds non-blocking decisions to `OpenQuestions.md`.
- Drafts or refines page source files in plain Markdown.
- Leaves durable planning or review context in the repository.
- Avoids frameworks, dependencies, automation, and deployment choices unless requested.
- Reports with a short copy-ready fenced `text` block.

## What The Human Reviews

- Whether the identity statement sounds true.
- Whether the target audience is specific enough.
- Whether the first offer direction is accurate.
- Whether proof or credibility claims are supported.
- Whether the tone sounds practical and credible.
- Whether the first page list matches the user's real goals.
- Whether any open questions should be answered now.

## End-Of-First-Session Result

By the end of a good first session, the user should have:

- A clearer identity statement.
- A target audience summary.
- A first offer direction.
- A proof or credibility inventory.
- A first page list.
- Plain Markdown page draft starters.
- A small set of non-blocking open questions.
- A next recommended local task.

The website is not built yet. That is intentional. The project now has enough source material to review, improve, and eventually turn into a maintainable website.

For the broader setup checklist, return to `UserSetupGuide.md`. To apply the pattern to another project, continue with `TemplateGuidance.md`.
