[Investigation] Front end code organization pattern

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

How should frontend code be organized?

Currently we:

• Don't have any documented standards
• Roughly follow a "feature-based" heirarchy, which discourages common code re-use
• Have lots of generic code holding locations for when utilities, helpers, and common code is added

I've opened RFC 115 to discuss this additionally.