Enable content type JSON export to be imported without modification
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Parent Issue
No response
User Story
As a content architect, I want to be able to export a content type as JSON and import that same JSON file into another system without modification, so I can easily share content types among unconnected systems.
Acceptance Criteria
- Copy the Blog content type from the starter site to an empty dotCMS site. This should work:
a. Export the content type to JSON from an instance running the starter site.
b. Import the JSON file (with no modification) to the instance running the empty starter. - Content type JSON files which could be successfully imported in earlier versions must still be able to be imported.
Proposed Objective
Technical User Experience
Proposed Priority
Priority 3 - Average
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
Reproduce the Blog content type export/import workflow between a starter-site instance and an empty instance, using the unmodified JSON file. Trace the content type JSON export and import entry points, then verify that the current workflow succeeds and that JSON files from earlier versions remain importable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, content
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100