Skip to content

Commit 176fb88

Browse files
Merge pull request #9 from sturdy-barnacle/2025-12-28
mostly documentation updates
2 parents 148ddd6 + d11456e commit 176fb88

78 files changed

Lines changed: 3634 additions & 1482 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

.cursorrules

Lines changed: 43 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,13 +2,13 @@
22

33
**IMPORTANT:** This file, `claude.md`, and `AGENTS.md` must stay in sync. See "Sync Instructions" at bottom.
44

5-
**For universal development standards applicable to any project, see:** `DEVELOPMENT-STANDARDS.md`
5+
**For universal development standards applicable to any project, see:** `docs/guides/DEVELOPMENT-STANDARDS.md`
66

77
---
88

99
## Universal Standards (Apply to All Projects)
1010

11-
See `DEVELOPMENT-STANDARDS.md` for complete details on:
11+
See `docs/guides/DEVELOPMENT-STANDARDS.md` for complete details on:
1212
- Code style (TypeScript strict, Prettier, ESLint, 2-space indentation)
1313
- Testing strategy (unit/integration/E2E pyramid, Jest, ≥70% coverage)
1414
- Accessibility (WCAG 2.1 Level AA minimum)
@@ -67,7 +67,7 @@ npm run format # Auto-format with Prettier
6767
Every PR must include:
6868
1. **Progress log:** Create `docs/progress/YYYY_MM_DD.md` with work summary, blockers, next steps
6969
2. **Changelog:** Update `CHANGELOG.md` under `[Unreleased]` section
70-
3. **ADL entry:** If major architectural decision, create entry in `docs/ARCHITECTURE-DECISIONS.md`
70+
3. **ADL entry:** If major architectural decision, create entry in `docs/guides/ARCHITECTURE-DECISIONS.md`
7171
4. **User docs:** Update `user-docs/` if UI/behavior changed
7272
5. **Developer docs:** Update `docs/` if architecture/structure changed
7373

@@ -107,6 +107,44 @@ Every PR must include:
107107

108108
---
109109

110+
## Documentation Maintenance
111+
112+
**Keep all documentation up to date and well-organized.**
113+
114+
### Organization Standards
115+
- **Dev docs** (`dev-docs/`): ALL CAPS for technical docs, Title Case for user guides
116+
- **Example docs** (`docs/examples/`): kebab-case (e.g., `getting-started.md`)
117+
118+
**Directory Structure:**
119+
- `dev-docs/specs/` - Technical specifications
120+
- `dev-docs/guides/` - Development guides
121+
- `dev-docs/planning/` - Phase plans
122+
- `dev-docs/progress/` - Daily logs (YYYY_MM_DD.md)
123+
- `dev-docs/` (root) - User guides and project docs
124+
- `docs/examples/` - Example documentation files
125+
126+
### Update When
127+
- Adding/changing features → update relevant docs
128+
- Architectural decisions → create ADL entry
129+
- Setup/deployment changes → update user-docs/
130+
- Structure changes → update `DOCUMENTATION.md`
131+
- Daily work → create/update progress log
132+
133+
### Quality Checklist
134+
- [ ] All file paths/references accurate
135+
- [ ] Cross-references updated
136+
- [ ] Naming conventions followed
137+
- [ ] `DOCUMENTATION.md` updated if structure changed
138+
- [ ] No broken links
139+
- [ ] Code examples tested
140+
141+
### Cross-Reference Maintenance
142+
- Use relative paths: `docs/specs/EMBERDOCS-TECHNICAL-SPEC.md`
143+
- When moving files, update ALL references (use `grep` to find)
144+
- Update: README.md, DOCUMENTATION.md, planning docs, progress logs
145+
146+
---
147+
110148
## Sync Instructions
111149

112150
**These three files must always be in sync:**
@@ -116,7 +154,7 @@ Every PR must include:
116154

117155
**When updating standards:**
118156
- [ ] Update all three files with consistent changes
119-
- [ ] Keep universal rules (DEVELOPMENT-STANDARDS.md section) identical across all three
157+
- [ ] Keep universal rules (docs/guides/DEVELOPMENT-STANDARDS.md section) identical across all three
120158
- [ ] Project-specific overrides can be formatted differently per file
121159
- [ ] Include "Sync Instructions" section in each file
122160

@@ -126,3 +164,4 @@ Every PR must include:
126164
- New documentation requirement → add to all three
127165
- Architecture decision locked → add to ADL + all three files
128166
- Phase plan updated → reflect in guidelines
167+
- Documentation structure/organization changed → update all three + DOCUMENTATION.md

.env.example

Lines changed: 44 additions & 55 deletions
Original file line numberDiff line numberDiff line change
@@ -1,66 +1,55 @@
1-
# ============================================
21
# EmberDocs Configuration
3-
# ============================================
4-
# Copy this file to .env.local and fill in your values
5-
# Never commit .env.local to version control
2+
# Copy this file to .env.local and customize as needed
3+
# All variables are optional - EmberDocs works with sensible defaults
64

7-
# ============================================
8-
# Content Configuration (Optional)
9-
# ============================================
10-
# Directory where markdown documentation files are stored
11-
# Default: docs/examples
12-
# Examples:
13-
# EMBERDOCS_CONTENT_DIR=docs/content # Files in docs/content/ folder
14-
# EMBERDOCS_CONTENT_DIR=content # Files in content/ folder
15-
# EMBERDOCS_CONTENT_DIR=pages # Files in pages/ folder
16-
EMBERDOCS_CONTENT_DIR=docs/examples
5+
# Branding (optional)
6+
# Default product name is "EmberDocs"
7+
EMBERDOCS_PRODUCT_NAME="EmberDocs"
178

18-
# URL route prefix for documentation pages
19-
# Default: /docs
20-
# Examples:
21-
# EMBERDOCS_BASE_ROUTE=/documentation # URLs: /documentation/getting-started/intro
22-
# EMBERDOCS_BASE_ROUTE=/help # URLs: /help/getting-started/intro
23-
# EMBERDOCS_BASE_ROUTE=/guides # URLs: /guides/getting-started/intro
24-
EMBERDOCS_BASE_ROUTE=/docs
9+
# Company or organization name (used in headers, metadata, and page titles)
10+
# If set, page titles will be formatted as: {PRODUCT_NAME} - {COMPANY_NAME} Documentation
11+
EMBERDOCS_COMPANY_NAME="Your Company Name"
2512

26-
# Show marketing landing page on root route (/)
27-
# Default: false (root route redirects to documentation index)
28-
# Set to 'true' to show the EmberDocs framework marketing landing page
29-
# Only needed for the EmberDocs framework repository itself
30-
# EMBERDOCS_SHOW_LANDING=true
13+
# Default author name (used when document frontmatter doesn't specify an author)
14+
EMBERDOCS_DEFAULT_AUTHOR="Your Name"
3115

32-
# ============================================
33-
# Branding & Metadata
34-
# ============================================
35-
# Default author name for documents
36-
# Used when a document's frontmatter doesn't specify an author
37-
# If not set, author metadata will only appear if specified in document frontmatter
38-
# EMBERDOCS_DEFAULT_AUTHOR=Your Company Name
16+
# Primary URL for your company/product (used in links and metadata)
17+
EMBERDOCS_PRIMARY_URL=https://your-url.com
3918

40-
# Company or organization name
41-
# Used in headers, metadata, and page titles
42-
# If not set, product name will be used alone
43-
# EMBERDOCS_COMPANY_NAME=Your Company, Inc.
44-
45-
# Product name
46-
# Used in headers, metadata, and page titles
47-
# Default: EmberDocs
48-
# EMBERDOCS_PRODUCT_NAME=Your Product Name
49-
50-
# Primary URL for the company/product
51-
# Used in links, metadata, and footer
52-
# EMBERDOCS_PRIMARY_URL=https://example.com
53-
54-
# Logo path (relative to /public directory)
19+
# Logo Configuration (optional)
20+
# Path to your logo image (relative to /public directory)
5521
# Supported formats: PNG, SVG, JPG
56-
# Example: /logos/my-logo.png
22+
# Example: /logos/your-logo.png
5723
# EMBERDOCS_LOGO_PATH=/logos/your-logo.png
5824

25+
# Navigation Links (optional)
26+
# Header navigation links as JSON object
27+
# Format: {"Label": "URL", "Another Label": "Another URL"}
28+
# External links must start with http:// or https://
29+
# Internal links start with /
30+
# EMBERDOCS_HEADER_LINKS={"Docs": "/docs", "Features": "/#features", "GitHub": "https://github.com/yourorg"}
31+
32+
# Footer Configuration (optional)
5933
# Footer text content (e.g., copyright notice)
60-
# Example: "Your Company © 2025"
61-
# EMBERDOCS_FOOTER_TEXT=Your Company © 2025
34+
# EMBERDOCS_FOOTER_TEXT="Your Company © 2025"
6235

63-
# Footer links as JSON object
64-
# Format: {"Label": "URL", "Another Label": "Another URL"}
65-
# Example: {"Privacy": "/privacy", "Terms": "/terms", "Contact": "/contact"}
66-
# EMBERDOCS_FOOTER_LINKS={"Privacy": "/privacy", "Terms": "/terms"}
36+
# Footer links as JSON object (same format as header links)
37+
# EMBERDOCS_FOOTER_LINKS={"Privacy": "/privacy", "Terms": "/terms", "Contact": "/contact"}
38+
39+
# Content Configuration (optional)
40+
# Custom documentation content directory (default: docs/examples)
41+
# EMBERDOCS_CONTENT_DIR=docs/examples
42+
43+
# Custom documentation base route (default: /docs)
44+
# URLs will be served at this path instead of /docs/*
45+
# EMBERDOCS_BASE_ROUTE=/docs
46+
47+
# Framework Mode (only for EmberDocs framework repository)
48+
# Set to true to show the EmberDocs marketing landing page at root (/)
49+
# Default: false (root redirects to /docs/index)
50+
# EMBERDOCS_SHOW_LANDING=false
51+
52+
# Theme Selection
53+
# Choose the theme for both landing page and documentation pages
54+
# Options: dark (default), light, monochrome
55+
# EMBERDOCS_THEME=monochrome

.github/PULL_REQUEST_TEMPLATE.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ All tests must pass locally before submitting. Use the checklist below:
3636
Documentation is required for most PRs. Check the boxes that apply:
3737

3838
### Progress Log (Required for all PRs)
39-
- [ ] Daily progress log created in `docs/progress/YYYY_MM_DD_progress.md`
39+
- [ ] Daily progress log created in `dev-docs/progress/YYYY_MM_DD_progress.md`
4040
- Include: work summary, related PRs, any blockers, next steps
4141

4242
**Example:**
@@ -55,17 +55,17 @@ Documentation is required for most PRs. Check the boxes that apply:
5555
```
5656

5757
### Phase Plan Updates (If scope changed)
58-
- [ ] `docs/planning/mvp_phase01of02.md` updated with deliverable changes (if applicable)
59-
- [ ] `docs/planning/mvp_phase02of02.md` updated (if applicable)
58+
- [ ] `dev-docs/planning/mvp_phase01of02.md` updated with deliverable changes (if applicable)
59+
- [ ] `dev-docs/planning/mvp_phase02of02.md` updated (if applicable)
6060
- [ ] Exit criteria reviewed for go/no-go status
6161

6262
**Example:** "Updated D1.3 acceptance criteria per feedback in #42"
6363

6464
### User-Facing Documentation (If UI/behavior changed)
65-
- [ ] `user-docs/Setup.md` updated (setup/installation changes)
66-
- [ ] `user-docs/Deployment.md` updated (deployment steps changed)
67-
- [ ] `user-docs/Configuration.md` updated (new config options)
68-
- [ ] `user-docs/Troubleshooting.md` updated (new error cases documented)
65+
- [ ] `dev-docs/Setup.md` updated (setup/installation changes)
66+
- [ ] `dev-docs/Deployment.md` updated (deployment steps changed)
67+
- [ ] `dev-docs/Configuration.md` updated (new config options)
68+
- [ ] `dev-docs/Troubleshooting.md` updated (new error cases documented)
6969
- [ ] `CHANGELOG.md` updated under `[Unreleased]` section
7070

7171
### Developer Documentation (If architecture/code structure changed)
@@ -98,7 +98,7 @@ Alternatively, link to a Vercel preview: `https://emberdocs-pr-XX.vercel.app/`
9898
- [ ] All tests pass locally (`npm run check`)
9999
- [ ] No console errors/warnings in dev mode
100100
- [ ] Commit messages are clear and imperative (e.g., "Add error handling module")
101-
- [ ] Progress log created in `docs/progress/`
101+
- [ ] Progress log created in `dev-docs/progress/`
102102
- [ ] Relevant docs updated (user or developer)
103103
- [ ] Changelog updated under `[Unreleased]`
104104
- [ ] No unrelated changes (scope-focused)

0 commit comments

Comments
 (0)