Collaberate and listen

[expelledboy]

Hey! So I am developing a template, akin tocreate-react-app. But with abit more meat in it such as authentication, use of apollo-cache for local state, permissions/roles with feature flags in the frontend, backend with example of two datasource, schema migration, modular hooks/component/resolvers, wrapped in yarn workspaces, deployment through docker, etc etc etc

Strip out some of your integrations (re-add them as code generation targets) and I noticed that this repo is very very similar. Would you like to team up? 🙂

[DarkSmile92]

Hey @expelledboy , great idea! What is the goal of your repository? I'd be glad to support your efforts in your repo :)

[expelledboy]

Sweet!

Well the goal is a template, thats as simple as possible, but includes examples of common functionality. For example login / auth / permissions is literally in 95% of apps in the wild, so should be included in the template.

Secondly it should be build on the lastest best practices, but not those where you find alot of boilerplate, because that indicates that desired behavior evolved out of a yet to be standardized framework. So not quite bleeding edge, but what is most simple.

The use-case I was thinking best exercises most common functionality is;

• A website that paginates over movies from api.themoviedb.org
• Movies can be "liked" stored in the backend DB joined on the users table against the movie ID
• On the frontend there is a shopping cart to purchase these movies which utilizes a local datastore
• The cart gets posted as an order
• The frontend has feature flags based on the user roles; "User", "Admin", and "OrderAdmin"
• The admin can manage users
• The user can browse like and purchase movies
• The order admin can manage orders

One thought I had was after we finish with this stack (create-react-app, graphql with apollo and prisma, typescript, yarn) we could actually develop a complete code generation solution! You could modify a web-up.yml, and based on the config render complete templates. So for example, you could pick your unit test framework or choose not to include tests at all, pick OAuth2, vanilla webpack or create-react-app, hooks vs HOC, etc. And depending on the features you pick, it would generate a template which includes all the functionality needed in both the frontend and backend Something akin to todomvc but completely generated from config.

But that is definitely secondary to getting this template up and running. Once we have a more clear understanding of "the common functionality found in most apps" and the "framework maturity" we want to maintain then we can recruit more maintainers and tackle it. If we got that right though it would blow the socks off literally every single template repo out there! 😂