Frontend Contribution Guide
This section is for contributors working on the Angular frontend workspace behind FLNet.
Most frontend changes come down to four questions:
- which app owns the feature:
local-apporglobal-app - whether the change belongs in
shared-libinstead of an app folder - which brand and environment configuration your change must respect
- which checks prove the change is safe before review
Start here
| If you need to... | Read this page |
|---|---|
| boot the right frontend variant locally | Local setup |
| understand the workspace layout | Workspace map |
| decide which folder should own the change | Where to change what |
| avoid wiring mistakes around builds and brands | Builds and environments |
| follow implementation and UI guardrails | Implementation guidelines |
| jump straight to a feature area | Systems overview |
Mental model
The rule that matters most is simple: both apps depend on the same shared library, so a change in shared-lib can help both apps or break both apps.
Operating assumptions
Read this section as engineering guidance, not as product documentation. The pages here focus on:
- which folder owns what
- which scripts actually start the app you need
- which environment files get swapped during builds
- which checks are worth running before you hand off a change
When in doubt, start with the narrowest change that fixes the problem, then widen the scope only if both apps or multiple brands genuinely need the same solution.