[MGNLEE-742] Extract demo-webapp to own travel-demo project Created: 02/Jan/23  Updated: 21/Mar/23  Resolved: 21/Mar/23

Status: Closed
Project: Magnolia DX Core
Component/s: None
Affects Version/s: 6.3.0, 6.2.27
Fix Version/s: 6.3.0

Type: Task Priority: Neutral
Reporter: Mikaël Geljić Assignee: Michael Duerig
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Team: Foundation
Work Started:

 Description   
  • goal: be able to showcase new features independently from dx-core minor/patch updates and backward compatibility, e.g. content-editor V2 (i18n), simplifying dependencyManagement along the way.
  • implementation: move the CE & dx-core demo webapps to the demo-projects project itself

Pros

  • would make dx-core slimmer
  • would make catching CVEs, duplicate classes, etc. faster
  • Would also help to treat travel-demo as a "real" Magnolia project, based on the archetype, and aggregate demo-projects modules in the reactor.

Open questions

  • Consider if maintaining both CE+DX Core demo webapps still makes sense?

Generated at Mon Feb 12 05:32:53 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.