Project goals

Goal

Boilerplate code to speed up development of a new SaaS app

Principles

Broadly, we can follow these principles to make the project useful with a good developer experience

1. Must have some Complete Features: These features are ready to use (these features do not expect much different implementations in different use cases e.g. auth)
2. Must have some Abstract APIs: These APIs(functions/services) help in building some of the most frequently used features in SaaS (where implementation vary a lot based on the use case e.g. email service, user roles, etc.)
3. Changes should be easy
   • Changes in Complete Features should be driven by configuration changes (e.g. replacing email/password login with passwordless login)
   • Changes in Abstract APIs should be driven by changing or extending the code
   • Abstract APIs should be documented
   • No styling opinion, a frontend without styling
   • Code Smells - If a dev needs to remove code or change the code structure in order to build their use case
   • Keep it lean

Agree? Give it a thumbs up 👍
Have feedback for goal/principles? Comment your thoughts

This is a project-goals discussion rather than a scoped code task, and it names no files, tests, or entry points. Start by reviewing the repository against the proposed complete features, abstract APIs, configuration approach, documentation expectations, and styling principles; done requires agreed goals and principles before implementation work is defined.