First Big Feature

[Dishpit]

Given the nature of Slopify, by design it'll have at least a handful of different features.

But, with that in mind, we need to start somewhere with one feature. So the question is: what should that feature be?

[a-catgirl-dev]

i missed the memo. what exactly are we doing? something enterprise? are there any more specific goals?

[infernostars]

#433; read the root post

[a-catgirl-dev]

#433; read the root post

shayy-undertale.mp4

[infernostars]

Unfortunate.

[Dishpit]

shayy-undertale.mp4

That explains... so much.

[infernostars]

we could have a CMS? that'd be a good trial for the permissions system too since usually you have writers, editors, and a media manager role. also forces us to think about design a bit [do we want a central server and a client?]

[Dishpit]

My only concern is that a CMS is a fairly large feature in and of itself. That's not inherently a bad thing, but it could be cause for concern.

Not a bad idea though.

[infernostars]

if you worry about it being too large we can start off with just basic architectural work - how do we want to structure the project? server and clients makes the most sense to me, so maybe we should have two seperate repositories? or we can monorepo it and just have, like, a server and client folder. either works. ill make an issue about it

[Dishpit]

Actually? I'm dumb.

The actual "first big feature" has to be accounts and feature modules, because everything builds off from there. So registrations, logins, verifications, organizations, seats, subscriptions for the different features, etc.

[infernostars]

yeah i assumed you meant outside of that

[infernostars]

#439