Creating Documents
How to create new documents in ArchDoc
Creating Documents
Learn how to create new technical documents in ArchDoc.
Quick Start
- Navigate to Dashboard > Documents
- Click the New Document button
- Fill in the document details
- Click Create
Document Creation Form
Document Title
Enter a clear, descriptive title for your document.
Good examples:
- "Use PostgreSQL as Primary Database"
- "RFC: Implement User Notifications"
- "Design Doc: Payment System Architecture"
Avoid:
- "Untitled"
- "New ADR"
- "Document 1"
Document Type
Select the appropriate type:
| Type | Use For |
|---|---|
| ADR | Single architectural decisions |
| RFC | Proposals for team discussion |
| Design Doc | Detailed technical designs |
See Document Types for guidance on choosing.
Initial Content (Built-in Templates)
When you select a document type, the editor is pre-populated with a starter template tailored to that type:
| Type | Template Sections |
|---|---|
| ADR | Status, Context, Decision, Consequences, Alternatives Considered, Notes |
| RFC | Summary, Motivation, Proposed Solution, Implementation, Risks and Drawbacks, Alternatives, Unresolved Questions |
| Design Doc | Overview, Goals, Non-Goals, Background, Design, Implementation, Security Considerations, Testing Plan, Future Work |
You can edit or clear the template before saving.
After Creating
Once created, you'll be taken to the document editor where you can:
- Write content using the rich text editor
- Add diagrams with Excalidraw or Mermaid
- Format text with headings, lists, code blocks
- Save changes manually or auto-save
Document Slug
Each document gets a unique slug based on its title:
- Title: "Use PostgreSQL Database"
- Slug:
use-postgresql-database
The slug is used in the document URL:
/dashboard/documents/use-postgresql-databaseSlugs are auto-generated but can be customized if needed. They must be unique within your organization.
Document Categories
New documents start as In Progress. You can change the category as the document evolves:
| Category | Meaning |
|---|---|
| In Progress | Being drafted, open for edits |
| Accepted | Approved, ready for implementation |
| Closed | No longer active |
Best Practices
Start with a Clear Title
- The title should explain what the document is about
- Include the document type if helpful (e.g., "RFC: ...")
Choose the Right Type
- Don't use Design Doc for a simple decision (use ADR)
- Don't use ADR for a proposal needing discussion (use RFC)
Draft First, Format Later
- Get your ideas down first
- Polish formatting afterward
Save Regularly
- Auto-save helps, but manual saves ensure nothing is lost
- The editor caches content locally as backup
Document Limits
Your plan determines how many documents you can create:
| Plan | Document Limit |
|---|---|
| Free | 5 |
| Base | 15 + (2 × additional seats) |
| Premium | Unlimited |
If you reach your limit:
- Archive or delete old documents
- Upgrade your plan
Permissions
Who can create documents:
| Role | Can Create |
|---|---|
| Admin | ✅ Yes |
| Member | ✅ Yes |
All authenticated users in your organization can create documents.
Next Steps
After creating a document: