For the org model, all org model users will see a different home page than users see now. There is a sidebar view very similiar to the domain management pages and thus can be added now before design is complete. Adding a view now also gives us a place to start adding all the other tabs and the other features such as new filtering features.
Some considerations when adding this view is that we need to be able to route users to this page (more middleware interference). We also want to make sure the domains/domain request tables stay somewhat in sync with the non org view, ie if we change the widths or add a button to one, it would be great if we didn't have to remember to change it in both places.
The goal here is to create a starting base to build the org model view from, however, do not worry about all the database aspects not being ready. For instance, see the AC below that mentions just not showing anything about suborganizations, the org name etc, those will be added in later. Note, also that all the other tabs basically will do nothing at the moment.
No design review required as this will not be a finished product yet.
Acceptance criteria
[ ] when navigating to the home page and org model is turned on the org model view is shown (described in the ACs below)
[ ] side nav added with the options shown in the figma with the top of the sidebar (ignore the org name that shows at the top of the side nav)
[ ] have domains and Domain Requests be a clickable side nav that then shows the domains table and domain requests table.
[ ] Determine if the domain request and domains tables for org model should use a template that is shared between org and non org views or if it's better to have a separate template for the org model views
[ ] members/organization and senior official side nav links do nothing
[ ] wrap this feature with the Org model feature flag
Additional context
Example of what is made, though refer to the figma. In this picture the filters and export and suborganization should all be excluded.
Issue description
For the org model, all org model users will see a different home page than users see now. There is a sidebar view very similiar to the domain management pages and thus can be added now before design is complete. Adding a view now also gives us a place to start adding all the other tabs and the other features such as new filtering features.
Some considerations when adding this view is that we need to be able to route users to this page (more middleware interference). We also want to make sure the domains/domain request tables stay somewhat in sync with the non org view, ie if we change the widths or add a button to one, it would be great if we didn't have to remember to change it in both places.
The goal here is to create a starting base to build the org model view from, however, do not worry about all the database aspects not being ready. For instance, see the AC below that mentions just not showing anything about suborganizations, the org name etc, those will be added in later. Note, also that all the other tabs basically will do nothing at the moment.
No design review required as this will not be a finished product yet.
Acceptance criteria
Additional context
Example of what is made, though refer to the figma. In this picture the filters and export and suborganization should all be excluded.
Links to other issues
No response