Skip to content

Latest commit

 

History

History
123 lines (91 loc) · 5.74 KB

File metadata and controls

123 lines (91 loc) · 5.74 KB

Harvous Documentation

Complete documentation index for the Harvous Bible study notes application.

Quick Navigation

Getting Started

Architecture & Design

API & Development

Feature Documentation

Component Documentation

Design & Styling

Development Plans

Issue Tracking & Lessons

Specialized Guides

Documentation Categories

For Users

  • User guides and feature documentation
  • How-to guides and examples
  • Feature overviews

For Developers

  • Architecture and design documentation
  • API references
  • Component documentation
  • Development guides and best practices

For Contributors

  • Contributing guidelines
  • Development setup
  • Code style and patterns
  • Migration guides

Finding What You Need

Want to understand the system? → Start with ARCHITECTURE.md, then explore DATABASE.md and COMPONENTS.md

Want to know what runs in production?TECH_STACK.md and GETTING_STARTED.md — production is React SPA + Hono API; Astro is used for build tooling and optional dev only, not served in production.

Working on a feature? → Check FEATURES.md and related feature documentation

Building a component? → See COMPONENTS.md and REACT_ISLANDS_STRATEGY.md

Integrating with the API? → Reference API.md for complete endpoint documentation

Setting up development? → See the main README.md for setup instructions

Documentation Standards

  • All documentation uses Markdown format
  • Code examples include syntax highlighting
  • Diagrams use Mermaid syntax
  • Cross-references use relative paths
  • Keep documentation up-to-date with code changes

Contributing to Documentation

When adding or updating documentation:

  1. Place files in appropriate location

    • Architecture docs → docs/
    • User guides → docs/ (or root if primary)
    • Component docs → docs/
  2. Update this index when adding new documentation files

  3. Use clear, descriptive titles and organize with headers

  4. Include code examples where helpful

  5. Cross-reference related docs for easy navigation