Guides
Setting Up Your Project
A complete walkthrough for configuring your EpicContext project with the right sections, block types, and team settings.
This guide covers how to configure your EpicContext project after initial creation, including customizing sections, inviting team members, and setting up exports.
Choosing Your Sections
Every project starts with a default set of sections. You can customize which sections appear based on your needs.
Default Sections
When you create a project, EpicContext initializes these sections:
- Brand — Visual identity, tone of voice, messaging framework
- Product — Product overview, features, strategy canvas
- Users — Personas, jobs to be done, journey maps
- Research — Competitors, user research data
- Technical — Tech stack, architecture, API specs, data models
- Development — Epics, user stories, tasks, roadmap
- Decisions — Architecture decision records, meeting notes
Enabling Additional Sections
Depending on your project, you may want to enable:
| Section | Best For |
|---|---|
| Design System | Teams with a component library or Figma files |
| Information Architecture | Content-heavy products with complex navigation |
| Metrics | Data-driven teams tracking KPIs and analytics events |
| Marketing | Teams planning campaigns and SEO content |
| Environments | Teams managing multiple deployment environments |
Navigate to Settings > General to toggle sections on or off.
Organizing Your Content
Start with the Foundation
We recommend filling in content in this order:
Brand & Product basics
Start with your brand positioning and product overview. These provide the foundation that AI agents need to understand your product.
Users & Personas
Define who you're building for. Personas are referenced by many other block types, so having them early makes everything else easier.
Technical stack
Document your tech stack and architectural constraints. This helps AI coding agents make appropriate technology choices.
Features & Development
Add your features, epics, and user stories. These connect back to your personas and technical constraints.
Block Naming Conventions
Use clear, descriptive keys for your blocks:
- Good:
primary-user-persona,checkout-flow-feature,react-framework-decision - Avoid:
persona-1,feature-new,decision-latest
Block keys become part of your file names when exporting to a CONTEXT folder. Clear naming makes it easier for AI agents to find relevant content.
Configuring Exports
CONTEXT Folder Setup
To sync your project to a local CONTEXT folder:
- Go to Settings > Export/Import
- Click Export to CONTEXT Folder
- Choose your export location (typically your project root)
- Add
CONTEXT/to your.gitignoreif you don't want it in version control
API Key Setup
For programmatic access via the REST API:
- Go to Settings > General
- Scroll to API Keys
- Click Generate API Key
- Store the key securely — it won't be shown again
# Test your API key
curl -H "X-API-Key: your-api-key" \
https://epiccontext.com/api/v1/projects/YOUR_PROJECT_ID/blocks
Next Steps
- Read about writing content optimized for AI agents
- Set up team collaboration
- Explore available block types
Last updated: 2026-02-21