[all] Coding practices and project layout

[NathanBland]

So we know that we already follow standard js and that's fine for guiding most of our code styling.

I'm opening this issue mostly to define project structure, as I believe we currently have a disconnect in file organization and workflow.

Let me know your thoughts here @crodeheaver @keawade

[keawade]

Probably could use a definition for route use and layout.

• When to create a new route file?
• When to add to an existing route?
• Single layer of route files (Like what we have at the moment) or deeper?

[crodeheaver]

I think this project structure works fine. I don't know this structure super well though.

I'm a bigger fan of the MVC style because it keeps everything clean and is a little more structured, imo.

I recommend a folder per controller.... er... route?

[keawade]

This is more or less what we have right now.

We've been adding on extra route files as we add on significantly separate functionality.

[NathanBland]

@crodeheaver I like what you are talking about, with one folder per "route/controller", though I also like the concept of a folder per feature set. Though I think route level works better aka.

• index :arrow_down:
  • dashboard :arrow_down:
  • requests
  • notifications
  • profile :arrow_down:
  • settings
  • details
  • etc

@keawade I think that works for basics, but I think once we start getting more complex, which we will quickly, that a more finely-detailed approach will help us stay sane.

[crodeheaver]

Well each controller is essentially a feature set, so I'd agree with that.

See https://github.com/crodeheaver/ucim for what I mean. It's pretty clean and keeps things separated when the project grows.

@NathanBland I'll pretty much advocate anything that's strong structure.