Dojo to Angular: Permissions UI
Open
Nobody has claimed this yet.
stale
Team : Modernization
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Redesign the permissions UI from Dojo to Angular. Make permission effects visible and predictable — show inheritance, preview impact before saving, detect conflicts, and unify the UI across all entry points (content, folders, sites, workflows, roles). Requires design exploration.
Contributor guide
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 permissions UI across content, folders, sites, workflows, and roles, then compare the current Dojo experience with the intended Angular redesign. The issue calls for design exploration of inheritance visibility, impact previews, conflict detection, and unified entry points; done means those requirements have a defined, consistent design.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, java
- Domain
- authorization, design, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100