- Restructure docs and examples directories - Add stdlib skill packs and language experts - Add CLI build/init/install commands - Add build and organization docs and quick references - Update docs index and project structure - Move session summaries under docs/sessions - Consolidate skills test fixtures under tests/skills - Remove obsolete examples and legacy docs
8.4 KiB
PCL Documentation Organization
Last Updated: 2026-01-19
Overview
This document describes the organization of PCL documentation to make it easy to find what you need.
Root Directory
The root directory contains only essential project files:
| File | Purpose |
|---|---|
README.md |
Project overview and quick start |
CHANGELOG.md |
Version history and changes |
CONTRIBUTING.md |
How to contribute to PCL |
SECURITY.md |
Security policy and vulnerability reporting |
LICENSE |
Apache 2.0 license |
package.json |
NPM package configuration |
.gitignore |
Git ignore rules |
.editorconfig |
Editor configuration |
.prettierrc |
Code formatting rules |
.eslintrc.json |
Linting configuration |
All other documentation is organized in the docs/ directory.
Documentation Structure
docs/
├── INDEX.md # Main documentation index (START HERE!)
├── ORGANIZATION.md # This file
│
├── phases/ # Phase completion documents
│ ├── PHASE-2.4-COMPLETE.md
│ ├── PHASE-2.5-2.7-PLAN.md
│ ├── PHASE-2.5-2.7-PROGRESS.md
│ ├── PHASE-2-COMPLETE.md
│ ├── PHASE-2-VALIDATION.md
│ └── SKILLS-CLI-COMPLETE.md
│
├── quickref/ # Quick reference guides
│ ├── QUICKSTART.md
│ ├── BUILD-QUICK-REF.md
│ └── SKILLS-CLI-QUICK-REF.md
│
├── sessions/ # Session summaries
│ ├── SESSION-2026-01-18-FINAL.md
│ └── SESSION-SUMMARY-DETAILED.md
│
├── guides/ # User guides and tutorials
│ ├── GETTING-STARTED.md
│ ├── GETTING-STARTED-CURRENT.md
│ ├── EVENT-SYSTEM.md
│ ├── REGISTRY-USAGE.md
│ └── ...
│
├── api/ # API reference documentation
│ ├── PARSER.md
│ ├── SEMANTIC.md
│ ├── CODEGEN.md
│ ├── REGISTRY-ARCHITECTURE.md
│ └── ...
│
├── skills/ # Skills ecosystem docs
│ ├── CLAUDE-CODE-COMPATIBILITY.md
│ ├── AGENT-SKILLS-COMPATIBILITY.md
│ └── CLI-USAGE.md
│
├── registry/ # Registry system docs
│ ├── REGISTRY-CHEATSHEET.md
│ ├── DATABASE-FREE-REGISTRY.md
│ └── TEST-RESULTS.md
│
├── reference/ # Language reference
│ ├── LANGUAGE.md
│ ├── SYNTAX.md
│ └── ERROR-CODES.md
│
└── changelog/ # Detailed changelogs
└── CHANGELOG-2026-01-18.md
Finding What You Need
I'm New to PCL
Start here in order:
- Root README - Project overview
- Quickstart Guide - Get started in 5 minutes
- Getting Started Guide - Full tutorial
- Documentation Index - Browse all documentation
I Want to Build Something
Build system resources:
- Build Quick Reference - Commands overview
- Build System Guide - Complete guide
- Phase 2.4 Complete - Build system details
I Want to Use Skills
Skills resources:
- Skills CLI Quick Reference - Commands overview
- Skills CLI Usage - Complete guide
- Claude Code Compatibility - Claude Code integration
- Agent Skills Compatibility - agentskills.io integration
I'm Using an IDE
IDE integration:
- VSCode Setup - VSCode extension setup
- Phase 2.1 Complete - LSP features
- Phase 2.5-2.7 Plan - JetBrains/Neovim plans
I Need API Documentation
API references:
- Parser API - Parsing PCL code
- Semantic API - Type checking
- Codegen API - Code generation
- Registry API - Registry system
I Want to Contribute
Contributing resources:
- Contributing Guide - How to contribute
- Project Structure - Codebase organization
- Phase Documentation - Current development status
I Found a Security Issue
Security resources:
- Security Policy - Vulnerability reporting
- Security Hardening - Best practices
- Security Bootstrap - Security setup
Documentation Categories
1. Quick References (quickref/)
Fast, actionable guides:
- Command syntax
- Common patterns
- Cheat sheets
- Quick examples
Best for: Daily development, looking up commands
2. Guides (guides/)
Step-by-step tutorials:
- Getting started
- Feature deep-dives
- Best practices
- Integration guides
Best for: Learning, onboarding, understanding features
3. API Documentation (api/)
Technical reference:
- Function signatures
- Class interfaces
- Return types
- Usage examples
Best for: Programming, integration, automation
4. Phase Documents (phases/)
Development tracking:
- Feature completion
- Implementation plans
- Progress updates
- Roadmap status
Best for: Understanding project status, contributing
5. Session Summaries (sessions/)
Development sessions:
- What was built
- Decisions made
- Problems solved
- Next steps
Best for: Understanding context, reviewing history
Documentation Standards
File Naming
- Use kebab-case:
my-document.md - Be descriptive:
BUILD-QUICK-REF.mdnotBUILD.md - Add prefixes for categories:
PHASE-2.4-COMPLETE.md
Headings
- Start with H1 (
#) for title - Use H2 (
##) for major sections - Use H3 (
###) for subsections - Include table of contents for long documents
Links
- Use relative paths:
../README.md - Link to specific sections:
#installation - Keep links up to date when reorganizing
Examples
- Include practical examples
- Show both good and bad patterns
- Provide context and explanation
- Keep examples focused and concise
Maintenance
Adding New Documentation
- Choose appropriate directory
- Follow naming conventions
- Update
INDEX.md - Update this file if adding new category
- Cross-link from related documents
Updating Documentation
- Update modification date
- Maintain backward compatibility of links
- Update cross-references
- Run link checker (if available)
Reorganizing
- Update all internal links
- Update
INDEX.md - Update this file
- Create redirects if needed (GitHub Pages)
- Announce in changelog
Search and Discovery
Documentation Index
The Documentation Index is the master catalog:
- Organized by topic
- Links to all documents
- Quick reference tables
- Statistics and metrics
Full-Text Search
Use GitHub's search:
- Navigate to repository
- Press
/to open search - Search within:
path:docs/ - Example:
path:docs/ quickstart
Directory Listing
Each category has its own folder:
ls docs/guides/- List all guidesls docs/api/- List all API docsls docs/phases/- List phase documents
Related Resources
External Documentation
- SPEC/: Language specification (formal grammar, type system)
- GOVERNANCE/: Governance and compliance docs
- .roadmap/: Project roadmap and planning
- examples/: Code examples
- test/: Test documentation
Repository Links
- Issues: https://github.com/personalayer/pcl/issues
- Discussions: https://github.com/personalayer/pcl/discussions
- Pull Requests: https://github.com/personalayer/pcl/pulls
Quick Links
| Documentation | Location |
|---|---|
| Main Index | docs/INDEX.md |
| Quickstart | docs/quickref/QUICKSTART.md |
| Getting Started | docs/guides/GETTING-STARTED-CURRENT.md |
| Build System | docs/BUILD-SYSTEM.md |
| Skills CLI | docs/skills/CLI-USAGE.md |
| API Reference | docs/api/ |
| Contributing | CONTRIBUTING.md |
Maintained by: PCL Team Questions: GitHub Discussions Issues: GitHub Issues