Hi,

At present you can indicate that a module is displayed on that one page or on all pages.
I have a module I want to display on the current page AND all its child-pages, but not on any other page.

At the moment I then have to add/copy that module manually to every child-page. And when I have to change something, I may need to change it on all child-pages as well.

Question:
*    I am looking for a module-feature/option by which that module is automatically displayed on all child-pages as well, in about the same location/pane.

In fact that is a part of a 'master-child'-concept. So, a different view of this concept would be:
Question:
*    How to define some kind of 'master page', defined somewhere on the wite, and then per page can set the masterpage-property to the desired master-page?
   The master-page then can contain various modules and the whole lot automatically becomes part of that page
   (Similar to the master-child-page concept in ASP.NET 2.0)
   This more than 'just assign the page a page-skin'

Anybody who knows how to do this or has some answers on these questions??

Thanks,
Pieter

If it were too time-consuming or inconvenient to add or delete the module as needed per page, then I would create a custom page template and use that whenever a new page is added. Someone has a walkthrough for creating a page template so have a look around for that, but I gather it basically means exporting a portal template and then pulling just the one page out of it for re-use.

If you export a template and open it in a text editor you'll understand. Also, I can't be 100% sure, but I believe you may even be able to use the "Copy design to descendants" option to apply it to child pages automatically from the root page.

Rob