[EPIC] Rework of the ContentApp
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 86
Description
Is your feature request related to a problem? Please describe.
The ContentApp has accumulated some feature requests which it's current design was not originally meant to accommodate.
I'm creating this issue after discussion on pulpcore meeting and pulp-meeting (Aug 25, 2026) to link toghether some of those issues and to gather discussion around it.
Describe the solution you'd like
A design-level approach that can accommodate newer content-app requirements while maintaining code quality.
Describe alternatives you've considered
Accepting changes without a re-design. Initially rejected because it creates meaningful technical debt.
Additional context
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 reading the linked issues #7887 and #8006, then review the ContentApp discussion referenced in this issue. Done means producing a design-level approach that accommodates the newer ContentApp requirements while maintaining code quality and avoiding the stated technical debt.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100