Projects & Sections

EpicContext uses a three-level hierarchy to organize your product context: Organizations, Projects, and Sections containing Blocks.

Organizations

An organization is your team's top-level workspace. It maps to your company, department, or agency.

• Each organization can have multiple projects
• Team members are invited at the organization level
• Billing and access control are per-organization

Projects

A project represents a single product or application you're documenting. Each project gets its own set of sections and blocks.

When you create a project, EpicContext initializes it with default sections that cover the most common documentation needs.

Sections

Sections are thematic groupings of related content. EpicContext comes with these default sections:

Blocks

Blocks are the atomic units of content in EpicContext. Each block has:

• Type — defines the schema (fields and structure)
• Key — a unique identifier within its section
• Name — a human-readable display name
• Status — empty, draft, or complete
• Value — the actual content (structured JSON)

Block Status

EpicContext tracks the completion status of every block:

• Empty — no content has been entered yet
• Draft — some content exists but required fields may be incomplete
• Complete — all required fields are filled in

The project overview page shows completion percentages per section, calculated from block statuses.

Content Flow

Your content flows through EpicContext in multiple directions:

Web Editor (forms) → Database (JSON) → Exports
                                     ├── Markdown
                                     ├── llms.txt
                                     ├── JSON API
                                     └── CONTEXT folder

This means you write content once and it's available in every format your team and tools need.