How to Use These Docs
Quick guide to finding what you need without getting lost.
πΊοΈ What's Hereβ
The docs are organized into eight sections:
| Section | What's Inside |
|---|---|
| Introduction | Who we are, why we're here, how these docs work |
| Tech Stack | Guides for the tools and frameworks we use |
| Best Practices | Our standards for code, architecture, and workflows |
| Projects | Documentation for specific projects we're working on |
| Guides & Tutorials | Step-by-step walkthroughs for common tasks |
| FAQ & Troubleshooting | Answers to questions we keep getting asked |
| Architecture & Patterns | Design decisions and the reasoning behind them |
| Install & Setup | How to get your dev environment running |
π― I Need...β
Quick paths based on what you're looking for:
- "I just joined β where do I start?" β Start with What is EndToEndLabCR, then Install & Setup
- "How do I set up my environment?" β Jump to Install & Setup
- "What tech stack do we use?" β Head to Tech Stack
- "How do we structure our code?" β Check Architecture & Patterns
- "I'm stuck on something" β Try FAQ & Troubleshooting first, then ask on Discord
- "I want to contribute" β Read on β the section below is for you
π‘ Tips for Getting the Most Out of These Docsβ
- Use the search bar β It's fast and usually finds what you need
- Bookmark sections you use often β You'll be back
- Cross-links are your friend β We link related topics so you don't have to hunt
- Check the date β If something feels outdated, it probably is. Update it or flag it
π€ Contributingβ
These docs are a team effort. Here's how to pitch in:
- Spot a gap? β Write about it. A rough draft is better than no draft
- Found an error? β Fix it. Don't wait for someone else
- Have a better way? β Update the doc and explain why in your PR
- Not sure where something goes? β Put it somewhere reasonable and we'll sort it out in review
Style Quick Guideβ
When writing or editing:
- Be direct β Write like you're explaining to a teammate
- Show, don't tell β Use code examples, not just descriptions
- Keep it current β Outdated docs mislead. Update or archive them
- Link liberally β Connect related topics so readers can explore
π¬ Feedbackβ
Something unclear? Missing info? Have a suggestion?
- Quick fix β Edit the doc directly and submit a PR
- Bigger idea β Open an issue with your suggestion
- Want to talk it through? β Drop by Discord or ask at office hours
Ready to build? Head to Tech Stack to see what we're working with β