[MGNLDEMO-12] Multisite example Created: 29/Apr/15  Updated: 02/Jun/15  Resolved: 01/Jun/15

Status: Closed
Project: Magnolia Demo Projects
Component/s: None
Affects Version/s: 0.5
Fix Version/s: 0.5

Type: New Feature Priority: Major
Reporter: Christopher Zimmermann Assignee: Christopher Zimmermann
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MGNLDEMO-46 RegExpVirtualURIMapping is not site a... Closed
depends upon MGNLRES-145 NonInstalledResourcesFilter incorrect... Closed
depends upon MULTISITE-41 Add migration for sites from new site... Closed
depends upon MULTISITE-43 Create site aware version of RegExpVi... Closed
is depended upon by MGNLDEMO-13 Marketing Tags Manager example Closed
is depended upon by MGNLDEMO-14 Personalization example Closed
relation
is related to MGNLDEMO-43 Remove navigation from sportstation w... Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

Provide a simple example of an additional website that shares some of the content & components with the travel website, but has a custom theme.

Provide a very simple adventure travel site with:

  • A home page listing the active tours.
  • Individual tour pages - which do not show tourTypes or Destinations
  • An about page.
  • A new theme providing simple color changes.
  • Navigation does not include tourTypes or Destinations.

Put bootstraps in mgnl-bootstrap instead of mgnl-bootstrap-samples with this reasongin - A user wants to install these samples - but does not want to install the samples of every single module.



 Comments   
Comment by Philip Mundt [ 19/May/15 ]
  • enabling / disabling navigation area by setting parameters is the wrong approach:
    • this should be done in the site definition of sportstation
    • Set enabled=false for both areas
    • navigation.ftl gets simpler again
  • MULTISITE-41 introduces migration for the site configuration
    • config.modules.multisite.config.sites.default.xml & config.modules.multisite.config.sites.travel.xml should go
    • config.modules.multisite.config.sites.travel.xml use it to configure travel-specific settings
    • Domain mapping for both sites travel & sportstation
  • Renaming the theme travel-demo-theme should be a separate commit
  • TravelDemoMultisiteModuleVersionHandler can go
  • home template (node) shoud not be renamed to main

Optional improvements:

  • showDestinations & showTourTypes via parameters...wouldn't it be nicer if the editor could choose (i.e. via dialog)?
  • Similar thoughts on tourType for tourList:
    • We could add a dialog where someone can choose the actual tourType
    • The model should only have one method getTourCategory()
    • Beneficial: We could test it
  • Theme node names travel-demo-theme/sportstation-theme introduce "redundancy" in name/path:
    • Keep it node-named "travel-demo", but add the property name=travel-demo-theme?
Comment by Christopher Zimmermann [ 19/May/15 ]

Sportstation navigation uses enabled=false on areas. Depend on multisite migration.

Comment by Christopher Zimmermann [ 01/Jun/15 ]

Fix on branch MGNLDEMO-12-b

Override tours virtualURIMapping with site aware mapping.
Adjust sportstation content to use "jumbotron" component, and "home" page template.
Adjust travel-demo multisite configuration to use 'travel-demo-theme' as theme name.

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