Divide Fragment Creator and Express Mapping into 2 views allowing both streams to develop product & experiments quickly.
The fragment focused mapping (Demo/Acquisition stream) was segmented here:
css/fragment-mapping
js/sections-mapping
import-fragments.html
The Express mapping (whole site import) was segmented here:
css/free-mapping
js/free-mapping
import-express.html
Shared code was put in
js/shared
FRAGMENTS
I believe the Fragment capabilities have remained untouched. Naturally naming, etc. is always up for discussion.
EXPRESS
Anthony and I (and the team) have to fully agree on the approach. At the moment I consider the UI an experiment. I think it has merit and I hope to have VIP teams use it. Always look forward to XD suggestions.
Related Issue
Motivation and Context
This is more of a level set, dividing development streams.
How Has This Been Tested?
Manually.
Screenshots (if appropriate):
Types of changes
Code division (almost refactoring)
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
Description
Divide Fragment Creator and Express Mapping into 2 views allowing both streams to develop product & experiments quickly.
The fragment focused mapping (Demo/Acquisition stream) was segmented here:
The Express mapping (whole site import) was segmented here:
Shared code was put in
FRAGMENTS I believe the Fragment capabilities have remained untouched. Naturally naming, etc. is always up for discussion.
EXPRESS Anthony and I (and the team) have to fully agree on the approach. At the moment I consider the UI an experiment. I think it has merit and I hope to have VIP teams use it. Always look forward to XD suggestions.
Related Issue
Motivation and Context
This is more of a level set, dividing development streams.
How Has This Been Tested?
Manually.
Screenshots (if appropriate):
Types of changes
Code division (almost refactoring)
Checklist: