hackforla / hackforla/tdm-calculator
Create a walkthrough for LADOT admins & security amins
- Dominant language
- JavaScript
- Stars
- 68
- Forks
- 47
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 25
Description
### Dependency
- When we finish the Admin features (must haves) - See the following labels for status of issues
- [x] [p-feature: My Project Page-Admin view](https://github.com/hackforla/tdm-calculator/labels/p-feature%3A%20My%20Project%20Page-Admin%20view)
- [ ] [p-feature: Admin Tools](https://github.com/hackforla/tdm-calculator/labels/p-feature%3A%20Admin%20Tools)
### Overview
In order to allow for internal hand off between LADOT users, we should have a walk through going over setting up admin roles, as well as anything else unclear
### Action Items
- [ ] Determine best way to write walk through
- possibly PDF with screenshots
- [ ] Write walkthrough
- [ ] Share with LADOT
### Resources/Instructions
#### Slides
- [Staging Deck](https://docs.google.com/presentation/d/1crZ3IxqA4hAu3qzD7ns93Ieuqjwh6wyEtuX_46cP-fg)
- [Staging Deck, slide 475](https://docs.google.com/presentation/d/1crZ3IxqA4hAu3qzD7ns93Ieuqjwh6wyEtuX_46cP-fg/edit#slide=id.g3389954eb7d_35_18)
- Release Deck
- [YYYY-MM-DD Release Deck, slide 475]
Contributor guide
Research direction
Start by reviewing the Staging Deck, especially slide 475, and confirm the status of the Admin Tools and My Project Page admin features listed under Dependencies. Determine the walkthrough format and document setting up admin roles and other unclear handoff steps; done means the walkthrough is written and shared with LADOT.
Written by the indexing model from the issue text.
Assessment
- Domain
- authorization, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100