Andrey Tolpeev
Where it all starts
Every team starts with a blank repository, which feels like real freedom — until the sixth time you make the same structure, only slightly differently. The folders, architecture, workflows, scripts, features, and decisions are the same yet not identical, and that “not” is where inconsistency begins.
Perhaps a slightly different folder name, a missing lint rule, or a custom GitHub actions tweak someone forgot to document feels harmless at first. But over time, these small inconsistencies grow with every new project, increasing the cost of maintenance and ongoing support.
Templating is Your Friend
The main goal was to create an app with a strong foundation of features and best practices, making it easy to fork and build on. This way, we could start new projects quickly and have our standards and decisions built right into the code, so we didn’t have to rebuild everything each time. For us, reducing the time from starting a new app to being ready for development was key. A template repository seemed like the best way to do this, since decisions would be set in the template instead of being debated every time.
Read on Medium