adopt a feature-based file/folder structure

[cameron]

instead of organizing code and assets according to type (stylesheet/script/template), organize it by feature (nav, chat, etc). this makes it WAY easier to navigate/grok as a new developer, or even as an existing one as the codebase grows.

e.g.

- modules/
  - browse/
    - browse.js
    - browse.html
    - browse.css
  - .../

[zzmp]

As we're used to our current structure, I won't try to pull this until our next standup.

[cameron]

erps—this is a "to consider" not a todo. i expect it will incur significant complexity outside of what i've mentioned here, and don't expect it will add much to the value of the final project artifact.

[zzmp]

Gotcha. Awesome advice, thanks.