• 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?