How ottofeller/templates works
Main Components Identification
The system should be represented as a template engine architecture with the following main components:
a) Core Template Engine
• Located in src/common
• Handles shared functionality across all templates
• Includes common features like Git hooks, linting, GitHub workflows
b) Template Modules (Individual Project Types)
• Apollo Server Template (src/apollo-server)
• Backend Test Template (src/backend-test)
• CDK Template (src/cdk)
• NextJS Template (src/nextjs)
• Playwright Template (src/playwright)
• SST Template (src/sst)
Component Relationships
[Core Template Engine]
• [Common Services]
• Git Integration
• Docker Support
• Linting System
• GitHub Workflows
• Telemetry
• GraphQL Support
• [Template Modules]
• Apollo Server Template
• Backend Test Template
• CDK Template
• NextJS Template
• Playwright Template
• SST Template
Specific Implementation Details
For each template module, show:
• Input: Configuration options (from README)
• Output: Generated project structure
• Dependencies: Required packages and tools
• Integration points with common services
Architectural Patterns to Highlight
• Component-based architecture
• Inheritance and composition patterns
• Plugin system for features like Docker and GraphQL
• Configuration management system
Key Relationships
• How templates inherit from common components
• How configuration options affect template generation
• Integration points with external tools (Projen, JSII)
• Build and deployment workflows
Remember to include:
• Version control integration points
• Build and synthesis workflows
• Template customization mechanisms
• Integration with external tools and services
This will provide a clear understanding of how the template system works while maintaining the necessary level of detail for implementation and maintenance.