Details
-
Type:
Story
-
Status: Closed (View Workflow)
-
Priority:
P3
-
Resolution: Done
-
Affects Version/s: None
-
Labels:None
-
Template:customfield_11100 18574
-
Sprint:eHoldings Sprint 44
-
Story Points:8
Description
As a developer who will own eholdings app after September 1st
I need a document that outlines the eholdings app architecture
So that I have a sound understanding of how the system works.
Document should cover
- Component Architecture: eholdings routing components reference guide
- Must answer this question - why are the components organized the way they are?
- communicates E2E overall navigation/pattern
- Include diagram of data layer's role in routing
Buddy: Charles