We've moved discussions to Discord

Variant of Jumpstart Pro template without teams

Dan Weaver
I realize it's easier to have team support integrated at the start than to add it later. But that's assuming you might want to add it later.

I'm very confident that I won't ever want to use teams for my applications. The existing teams code add some overhead when reasoning through the current code and thinking how to add my own features.

I'd love to see a variant of the Pro template without any team support.
John Chambers
I have a similar project that has no need for teams as it's just for my sports club. So I've just hidden the Team functionality from my views and created all my models without team:references. It seems to be working fine and doesn't get in my way.

I think jumpstartrails.com is probably built this way too.

An added bonus is that later if I want to turn my application into a SaaS product for multiple clubs I can just add the team references to my models. But no plans for that yet!






Brandon B.
: I think this is the correct way to approach this.  I have built apps where I didn't want object-type (companies, regions, branches, parent companies) type organizations from the beginning when I built it, and then after 2 or 3 huge clients we had to add that functionality later, and it was a nightmare.  I will go with hiding it 30 times, rather than implementing it after-the-fact only one time.  A person does not realize how arduous the implementation on all models that are needed is, until they actually have to do it in a production environment, for a client needing the functionality.

Dan Weaver
Yes, same here. Just removing it from views and ignoring it in code. There's still a cognitive overhead with it though.

Building apps for clients always goes like this. But in my case I'm building my own apps, all with intentionally limited functionality and I'm 100% confident that teams will not be required.

If there was a team-less variant of the template it would simply be a case of caveat emptor and the developer could then choose which template to use in each project.
Dan Weaver
I realize it's easier to have team support integrated at the start than to add it later. But that's assuming you might want to add it later.

I'm very confident that I won't ever want to use teams for my applications. The existing teams code add some overhead when reasoning through the current code and thinking how to add my own features.

I'd love to see a variant of the Pro template without any team support.
John Chambers
I have a similar project that has no need for teams as it's just for my sports club. So I've just hidden the Team functionality from my views and created all my models without team:references. It seems to be working fine and doesn't get in my way.

I think jumpstartrails.com is probably built this way too.

An added bonus is that later if I want to turn my application into a SaaS product for multiple clubs I can just add the team references to my models. But no plans for that yet!






Brandon B.
: I think this is the correct way to approach this.  I have built apps where I didn't want object-type (companies, regions, branches, parent companies) type organizations from the beginning when I built it, and then after 2 or 3 huge clients we had to add that functionality later, and it was a nightmare.  I will go with hiding it 30 times, rather than implementing it after-the-fact only one time.  A person does not realize how arduous the implementation on all models that are needed is, until they actually have to do it in a production environment, for a client needing the functionality.

Dan Weaver
Yes, same here. Just removing it from views and ignoring it in code. There's still a cognitive overhead with it though.

Building apps for clients always goes like this. But in my case I'm building my own apps, all with intentionally limited functionality and I'm 100% confident that teams will not be required.

If there was a team-less variant of the template it would simply be a case of caveat emptor and the developer could then choose which template to use in each project.
Notifications
You’re not receiving notifications from this thread.
© 2023 Jumpstart Pro by GoRails, LLC