<!--
IndexTitle: How It Works
IndexDescription: Website page draft explaining the plan-write-organize-build workflow.
IndexType: Content
IndexStatus: Draft
LastEdited: 2026-05-30
-->

# How It Works

Plan, write, organize, review, build, publish, and improve.

Get Established On The Web uses a simple guided setup sequence: plan, write, organize, review, build, publish, and improve.

The aim is to create a prepared foundation for using AI to build your online presence before choosing tools or publishing platforms.

Each step produces source files that a person or AI agent can read later. Source files are the plain planning notes, prompts, and page drafts that explain what the website should say before the website is built.

Get Established Workspace is the public-friendly way to describe this AI-ready folder of organized files. Get Established Repository is the technical source-of-truth name when the work needs GitHub history, file paths, and agent instructions.

## 1. Plan

Clarify the identity, audience, offer direction, proof, and first pages. The practical first action is to use the discovery prompt or setup guide so the foundation is captured before the website build begins.

After basic discovery, add a short positioning conversation. This helps decide what the online presence should make clear first before AI drafts deeper website copy, business plan notes, or a future one-page website output.

Keep the plan short enough to use. Pricing, packaging, public call-to-action wording, and platform decisions can remain open until they are needed.

## 2. Write

Draft source content in plain Markdown, a simple text format for readable page drafts. Start with the pages that help a visitor understand the project quickly.

## 3. Organize

Use predictable folders for plans, prompts, setup notes, content, and future automation. The workspace keeps the work understandable; the repository is the source of truth where the current files, decisions, and history live.

## 4. Review

Check whether the message is clear, the offer direction is practical, and the drafts avoid unsupported claims.

## 5. Build

Choose the simplest website approach that fits the content and publishing needs. This keeps the early drafts framework-neutral, meaning they do not depend on a website platform yet.

## 6. Publish

Deploy only when the site has enough content to be useful and the build path is easy to maintain.

## 7. Improve

Use feedback, Git history, and focused prompts to make small improvements over time.

## Why This Method Works

The workflow keeps planning and content visible. It helps users avoid the common trap of choosing tools before they know what they need to say.

## Simple Example

A consultant might start with a few notes about who they help and what service they provide. The method turns those notes into an identity statement, a target audience summary, a homepage draft, an offers page draft, and a small backlog. Only after that content is clear does the project need to choose how the website will be built and published.

Guided setup is the draft-stage primary offer because it matches this sequence. It helps the user create the foundation before final business model details, pricing, or platform decisions are required.

For Get Established On The Web, the public website explains the method and offer. For a future user, the same method can support a separate one-page business website draft after real business inputs are approved.

## Link Intent

- Link `plan` and `write` steps to `StartHere.md`.
- Link artificial intelligence workflow details to `AIWorkflow.md`.
- Link repository workflow details to `GitHubWorkflow.md`.
- Link offer direction to `Offers.md`.

## Draft Status

This sequence can later become a visual flow or checklist, but the source content should stay readable without design. Do not choose a platform or framework from this page alone.
