# Content

## Purpose

Content holds project-specific publishable website, product, and publishing source material. For GetEstablished, this includes source drafts and structured copy that may later become public website or product-facing content.

Content is not Workspace. It should contain material intended for eventual publishing or product use, not private scratch notes, owner inbox material, or temporary working files.

## What Belongs Here

- Framework-neutral website content drafts.
- Product, offer, page, and publishing source content.
- Content blocks, copy drafts, page source files, and publishing inputs.
- Content that should remain easy to inspect before any build or publishing step.

## What Does Not Belong Here

- Project planning documents, audits, or backlog notes. Use `Plans`.
- Owner-specific scratch work, inbox material, raw references, or private drafts. Use `Workspace`.
- Reusable prompts or workflows. Use `Capabilities`, `Plans`, or future `Skills` depending on role.
- Website framework files or generated output before a build approach is chosen.
- Automation scripts. Use `Automation`.

## Important Folders

- `Website` - source content for the public website.
- `OnePageBusinessWebsite` - source content and inputs for the one-page business website direction.

## Reuse Boundary

Old project Content should not be reused unchanged when creating a new project unless the owner intentionally adapts it. Treat Content as project-specific by default, even when the structure or approach may inspire reusable capability guidance later.

## Agent Notes

Keep content plain and framework-neutral unless the user explicitly asks for a website build phase. Promote reusable content patterns into `Capabilities` or `Standards` only after the project-specific content is stable.
