Skip to content

Latest commit

 

History

History
123 lines (80 loc) · 5.88 KB

File metadata and controls

123 lines (80 loc) · 5.88 KB

Spotify Time Machine Documentation

Welcome to the comprehensive documentation for Jermaine's Spotify Time Machine. This documentation follows the Diátaxis framework for clear, organized technical documentation.

Documentation Structure

Our documentation is organized into four categories to help you find what you need:

Learning-oriented: Step-by-step lessons to help you get started

Coming soon: Getting started tutorials will be added as the project evolves.

Problem-oriented: Step-by-step guides to solve specific problems

Information-oriented: Technical descriptions and specifications

Understanding-oriented: Conceptual guides to deepen your knowledge

Architecture & Design

Infrastructure & DevOps

Migration Guides

Essential Root Documentation

  • README.md - Project overview and quick start guide
  • TODO.md - Feature implementation checklist and development priorities
  • CLAUDE.md - AI assistant context and development guidelines
  • LLM_CONTEXT.md - Large language model context for code generation

Quick Links

For New Contributors

  1. Start with the README for project overview
  2. Review CLAUDE.md for development patterns
  3. Check Command Reference for quick commands
  4. Read Developer Tools for tooling setup

For Developers

For Deployment

For Understanding the Codebase

Documentation Principles

This documentation follows the Diátaxis framework which organizes content into four distinct categories:

  1. Tutorials - Learning by doing (practical steps for beginners)
  2. How-To Guides - Achieving specific goals (recipes for experts)
  3. Reference - Technical information (accurate and complete specifications)
  4. Explanation - Understanding concepts (background and context)

For more information about this framework, visit diataxis.fr.

Contributing to Documentation

When adding new documentation:

  1. Identify the category: Is it a tutorial, how-to guide, reference, or explanation?
  2. Use kebab-case: Name files with lowercase and hyphens (e.g., token-management.md)
  3. Keep it focused: Each document should cover one topic thoroughly
  4. Cross-reference: Link to related documents in other categories
  5. Update this index: Add your new document to the appropriate section

Support

If you find gaps in the documentation or have suggestions for improvement:

  1. Check the TODO.md for planned improvements
  2. Review existing documentation for answers
  3. Consider contributing documentation improvements
  4. Follow the Diátaxis framework for new content

Last updated: October 2025 Documentation framework: Diátaxis