[Investigation] Front end code organization pattern
<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=421469) </details> <!--IssueSummary end--> 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](https://gitlab.com/gitlab-org/frontend/rfcs/-/issues/115) to discuss this additionally.
issue