-
Notifications
You must be signed in to change notification settings - Fork 10
Admin panel structure
Currently, we are using the Django Admin Interface to enter and edit supplemental content for eRegulations. This page details the information architecture of this interface, which we call the admin panel, for shared understanding.
The main forms of content (called "models" according to Django documentation) involve meta-content (groups and users of the admin panel) and the eRegulations-specific content (regulation sections, supplemental content, and categories of supplemental content). Essentially, the admin panel consists of tables of content, which are added through forms.
ID | Page name | Page type | URL |
---|---|---|---|
1.0 | Site administration | home | /admin/ |
1.1 | Authentication and authorization administration | table | /admin/auth/ |
1.1.1 | Select group to change | table | /admin/auth/group/ |
1.1.1.1 | Add group | form | /admin/auth/group/add/ |
1.1.2 | Select user to change | table | /admin/auth/user/ |
1.1.2.1 | Add user | form | /admin/auth/user/add/ |
1.2 | Supplementary content for regulations administration | table | /admin/supplementary_content/ |
1.2.1 | Select category to change | table | /admin/supplementary_content/category/ |
1.2.1.1 | Add category | form | /admin/supplementary_content/category/add/ |
1.2.2 | Select regulation section to change | table | /admin/supplementary_content/regulationsection/ |
1.2.2.1 | Add reg section | form | /admin/supplementary_content/regulationsection/add/ |
1.2.3 | Select supplementary content to change | table | /admin/supplementary_content/supplementarycontent/ |
1.2.3.1 | Add suppl. content | form | /admin/supplementary_content/supplementarycontent/add/ |
https://www.figma.com/file/MNtM37y3t0ZQ4onICxNDZm/eRegs-Admin-panel-sitemap?node-id=0%3A1
Please note that all pages on this GitHub wiki are draft working documents, not complete or polished.
Our software team puts non-sensitive technical documentation on this wiki to help us maintain a shared understanding of our work, including what we've done and why. As an open source project, this documentation is public in case anything in here is helpful to other teams, including anyone who may be interested in reusing our code for other projects.
For context, see the HHS Open Source Software plan (2016) and CMS Technical Reference Architecture section about Open Source Software, including Business Rule BR-OSS-13: "CMS-Released OSS Code Must Include Documentation Accessible to the Open Source Community".
For CMS staff and contractors: internal documentation on Enterprise Confluence (requires login).
- Federal policy structured data options
- Regulations
- Resources
- Statute
- Citation formats
- Export data
- Site homepage
- Content authoring
- Search
- Timeline
- Not built
- 2021
- Reg content sources
- Default content view
- System last updated behavior
- Paragraph indenting
- Content authoring workflow
- Browser support
- Focus in left nav submenu
- Multiple content views
- Content review workflow
- Wayfinding while reading content
- Display of rules and NPRMs in sidebar
- Empty states for supplemental content
- 2022
- 2023
- 2024
- Medicaid and CHIP regulations user experience
- Initial pilot research outline
- Comparative analysis
- Statute research
- Usability study SOP
- 2021
- 2022
- 2023-2024: 🔒 Dovetail (requires login)
- 🔒 Overview (requires login)
- Authentication and authorization
- Frontend caching
- Validation checklist
- Search
- Security tools
- Tests and linting
- Archive