The organization is designed to reuse common software design patterns used in frontend and backend projects as templates after a new repository is created. At minimum, each template needs architecture for large scale projects and authentication because it's used entirely everywhere. Enhancements are welcomed for designing the best possible architecture, for example:
DDD: Domain Driven Design
CQRS: Command Query Responsibility Segregation
MVC: Model, View, Controller
FSD: Feature-Sliced Design| Stack | Architecture |
|---|---|
| Backend | Factory Pattern, DDD, CQRS, MVC |
| Frontend | Advanced File Based Routing / Pattern Matching, FSD, and State Management |
| Microservices | ... |
-
Playwright E2E Testing
- Page Object Model
- HTML Reporter to GitHub Pages using GitHub Actions
-
SvelteKit
- SvelteKit-FSD
- Feature-Sliced Design
- Shadcn
- SvelteKit-FSD
-
NextJS
- Dark Mode
- Shadcn UI Library
- File-Based Routing
- SPA
- Support .mdx file type
-
Flutter
- (To be implemented)
-
Telegram Mini App
- File-Based Routing
- API Integration
-
FastAPI Template
- Factory Pattern
- Authentication
-
Bun/NodeJS Template
- SOLID
- OpenAPI Specification
- Database Providers
-
Golang Template
- (To be implemented)
-
SpringBoot Template
- (To be implemented)
-
Laravel Template
- MVC Pattern
- Authentication
-
C# Template
- (To be implemented)
-
Rust Template
- Separation of concerns
- API server
-
LaTeX
- CI/CD pipeline
- DRY
-
Plotly Dash
- FastAPI server
- API setup
- TailwindCSS
-
Frontend Project
- Playwright E2E Template
- SvelteKit Template
- NextJS Template
- Flutter Template
- Telegram Mini App Template
-
Backend Project
- FastAPI Template
- Bun/NodeJS Template
- Golang Template
- SpringBoot Template
- Laravel Template
- C# Template
- Rust
-
Other
- LaTeX Template
- Plotly Dash
When striving to write clean code, it's often helpful to refer to established style guides and best practices. Here are some valuable resources worth checking out:
-
Airbnb Style Guides Airbnb provides comprehensive style guides for various programming languages, including JavaScript. These guides cover a wide range of topics, from syntax and formatting to architectural decisions.
-
Uber Style Guides Uber offers style guides tailored specifically for Go programming. These guides provide recommendations on code organization, naming conventions, error handling, and more, based on Uber's extensive experience with Go development.
By consulting these resources, you can gain insights into industry-standard practices and adopt conventions that promote readability, maintainability, and consistency in your codebase.
| Company | Description | Needs | Goal |
|---|---|---|---|
| Sole Developer | It's just you, you want to have fun and not get burned out by GitHub requests | Keep it Simple! Scale may not be the top priority, but avoiding spaghetti is. | Modular Monolith |
| Small Startup | You're just getting going and don't have many customers yet | Keep costs low. Keep it simple. Scale isn't a priority now, but you hope it will be. Telemetry. | Modular Monolith |
| Rapidly Expanding | You've got customers and need to scale to fit demand. | Telemetry, understand the pain points. Code that supports adding developers. | Modular Monolith that can be divided |
| Webscale! | You've made it! You're supporting Google-style load, and heating data-centers around the world. | Telemetry, Manageability, Supporting Diverse Teams | Readily divided services |
Distributed under the Apache 2.0 License. See LICENSE.txt for more information.