rubyforgood / rubyforgood/endsideout
Establish CRUD patterns
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 11
- Forks
- 4
- Avg merge
- 20h 30m
- Merged PRs (30d)
- 19
Description
What
- Establish consistent partials and patterns for how we are managing the various CRUD screens for the admin. This should include considerations like:
- Clear breadcrumbs and navigation
- Consistent ways to manage entities and nested entities
Context
- We just cobbled together a proof of concept for the admin screens and as a result there are some inconsistencies and extra pages. We need to establish a clear navigation pattern to make sure that every page is easily navigable and finding the appropriate screens is easy for admin users
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing admin CRUD screens and comparing their navigation, breadcrumbs, partials, and handling of entities with nested entities. Identify the inconsistencies and extra pages described in the issue, then establish a consistent pattern across the screens. Done means admin users can navigate every page easily and the CRUD screens follow the same structure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100