Dojo to Angular: Permissions System
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Value to Deliver
Provide a modern, maintainable, and consistent permission management experience with full REST API support and Angular-based UI, ensuring parity with the legacy system.
Problem / Pain
The current permission system is complex, inconsistent, and deeply tied to legacy Dojo code. It's difficult to maintain, extend, and integrate with modern modules.
Constraints / Requirements
- Replace legacy Dojo UI with Angular
- Deliver full feature parity (users, roles, sites, content types, folders, etc.)
- Expose a clean, versioned REST API
- Ensure performance and clarity in permission evaluation
- Include accessibility and UX improvements
- Document endpoints and flows
Inputs Provided
- REST API spec (to be produced by engineering)
- UX design (to be provided by design team)
- Legacy reference (existing permission screens and workflows)
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
The issue names no files, tests, or entry points. Start by locating the legacy Dojo permission screens and existing permission API code, then use the engineering API specification and UX design when provided. Done means Angular UI and versioned REST endpoints with feature parity, accessibility and UX improvements, performance, and documented endpoints and flows.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, java
- Domain
- api, authorization, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100