I need to create mini-site within existing website. I have new content type called Events.

Single event will be number of pages related to that event. Some of the pages that will be under single event are:

  • Registration
  • Scheadule
  • Sessions
  • Resources
  • Travel

All of this pages needs to be on their unique url like mysite.com/event-name/registration. My first guess is to create all these as different content types and create some relation to single Event.

So my question is: How to create a relation between these pages and a main event? Since this mini-site needs to have its own navigation menu, can I automatise this menu creation somehow or should I create a separate menu for every event.

  • And what about the permission to access those various pages? Eg: for somebody who is not registered for an event, do they have access to the resources? Aug 9, 2016 at 20:31
  • There are no restrictions at all, all register links are external, all Events and their subpages would be visible to anonymous users.
    – Alex
    Aug 9, 2016 at 20:34

1 Answer 1


Method 1.

I would create a content type to act as a parent node for each event.

Then for each other content type, add an Entity Reference field, with only that parent content type available. (If you need to restrict the available parent nodes to certain users, you can use a view to get the results of the entity reference field and only allow the node author to select that node).

You can then start adding views to that parent content type for things like "Child nodes" with a reverse relationship to act as an automatically generated menu.

Method 2.

Everything goes into one content type, but use the Field Group menu to create horizontal tabs, and place those fields in those tabs. This will make editing the pages easier as they are all in one place, but depending on the amount of content in each of these mini sites, might have a slow load. There could be a good SEO argument for this method, as your content count would be good for each mini site all on one page.

I would probably choose method 1, unless the "mini site" is small enough to manage with field groups. The benefit of Method 1, is that you can use Rules to automatically add the other pages, and fill in the Entity Reference fields once the initial "parent" node is created.

  • Method 2 is out of the question, as the requirement say that every subpage needs to be on its own url, with its own meta tags etc... But Method 1 is what i currently have, i just need to find best way to create that menu and also the url of the sub-page, i think it can be done with toknes but i will need to check on that...
    – Alex
    Aug 9, 2016 at 20:31
  • Yes it can, create the individual content types, and make sure they have the Entity Reference field, then use Pathauto to set a URL pattern for each type, and use the title of the "Parent" node to start the URL alias. e.g. /parent-node/resources
    – Collins
    Aug 10, 2016 at 6:45

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.