saas-express-starter-kit VS node-express-realworld-example-app

So I have been working on a SaaS starter kit - a boilerplate code for a SaaS app, using node and express. Now that it has become useful to some people and the code is growing, I want to make sure thag the developer experience is not lost in an attempt to add more features. I thought having a clear project goals with principles(e.g. no opinion about styling) to follow will help with this. So here I have written down the goals and the principles that will make DevX better, need your feedback what other principles should I add? TIA

Best comment on how to structure your web app. There's a GitHub repo with boilerplate to follow this pattern

Agree. And that's where express boilerplate such as saas-express-starter-kit can become handy.

How will we do it within a week? We will use this starter kit template to start with common things structured and built out of the box (e.g. auth, email, events, etc.)

I choose Express, always. To speed up further, use the boilerplate - https://github.com/makeitcount/saas-express-starter-kit

It won't be a small discussion. Let's discuss this on the GitHub repo issues

Realworld express. Whenever I need an implementation in a new language, I always check to see if there's a realworld repo.

check this out https://github.com/gothinkster/node-express-realworld-example-app

I've always thought this was a pretty good place to see how frameworks look in a 'real-world' way. https://github.com/gothinkster/realworld Since each repo is a clone of Medium.com you can see how expressjs compares to NestJS, or Laravel or Spring, etc.