[EPIC]: Export Content API 2025
Open
Nobody has claimed this yet.
Team : Scout
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Parent Issue
No response
Task
Improve the export experience for content editors via API endpoint. Use the API to export large sets of contentlets, including relationships (no API endpoint currently available).
```[tasklist]
Export
Proposed Objective
Please Select
Proposed Priority
Please Select
Acceptance Criteria
No response
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
No response
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response
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 two linked sub-tasks, issues 30557 and 30559, and identify the existing content export API entry points they reference. The issue does not name files, tests, an endpoint, or acceptance criteria, so the scope and definition of done require clarification before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100