adobe / adobe/aem-modernize-tools
[Enhancement] Support to move content from page to Experience fragment
- Dominant language
- Java
- Stars
- 62
- Forks
- 45
- PR merge metrics
- No merged PRs in 30d
Description
### Expected Behaviour
While migrating Static template to Editable template, we mostly leverage XF for header and footer.
It would be nice if we can have mechanism to automatically create required XF and also move content from existing source to this newly created XF.
### Actual Behaviour
### Reproduce Scenario (including but not limited to)
#### Steps to Reproduce
#### Platform and Version
#### Sample Code that illustrates the problem
#### Logs taken while reproducing problem
Contributor guide
Research direction
Start by reviewing the tool's Static-template to Editable-template migration flow and how Experience Fragments are represented. Done means the migration can automatically create the required Experience Fragment and move the existing source content into it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- content, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100