# AudienceFocus Pipeline

This folder contains all source archives, analysis, generated microsites, and deployment records for the end-to-end workflow.

## Workflow

### 1. Extract website content to Markdown

- Discover meaningful pages using sitemaps, rendered navigation, and CMS APIs where available.
- Extract readable content while preserving headings, links, images, and source URLs.
- Remove repeated navigation/footer content, scripts, cookie UI, and duplicate pages.
- Save the verified archive under `01-source/`.
- Record extraction scope, page counts, exclusions, and failures.

### 2. Create audience-focused microsites

#### Step 1 — Analyze all content

Create a faithful company summary and inventory offerings, claims, proof points, CTAs, case studies, and missing information.

#### Step 2 — Find offerings and target audiences

Create a compact approval map containing:

- proposed offering or microsite;
- exact target audience;
- one-sentence promise;
- source-backed proof points.

Each microsite must focus on exactly one audience. Do not invent claims, metrics, customers, certifications, or case studies. Mark unsupported details as `needs human verification`.

#### Step 3 — Re-analyze content for each microsite

For every approved audience, select only relevant source material and document:

- audience and problem;
- resonant message;
- relevant offering;
- benefits;
- proof points;
- objections and FAQs;
- missing information.

Save analysis and content drafts under `02-analysis/` and `03-content/`.

#### Step 4 — Create microsites

Build one connected static site under `04-site/`:

```text
04-site/
├── index.html
├── styles.css
├── audience-one/index.html
├── audience-two/index.html
└── audience-three/index.html
```

Use one common domain, root-relative links, shared styling, semantic HTML, responsive layouts, and accessible navigation. Serve locally and verify the homepage, every subpage, and all shared assets before deployment.

### 3. Deploy to Cloudflare Pages

Use one Cloudflare Pages project for the homepage and related microsites:

```bash
npx wrangler whoami
npx wrangler pages deploy 04-site \
  --project-name <project-name> \
  --branch production
```

After deployment, verify the stable production hostname in a browser and confirm HTTP 200, correct titles/headings, working navigation, styles, and assets. Save deployment details under `05-deployment/`.

## Folder layout

```text
AudienceFocus-Pipeline/
├── README.md
├── 01-source/
├── 02-analysis/
├── 03-content/
├── 04-site/
└── 05-deployment/
```

## Quality gates

1. Source archive is complete for its declared scope and read back successfully.
2. Audience/offer map receives human approval before detailed page generation.
3. Every claim in each microsite is traceable to source content or marked for verification.
4. Local site passes content, navigation, responsive, accessibility, and visual checks.
5. Production Cloudflare URL is independently checked after upload.