A module is a regular page, differentiated from other pages by being inside a modules container. This approach makes it possible to use pages as modules without sacrificing regular subpages:

📄 Page
  📄 Subpage A
  📄 Subpage B
  🗂 Modules
    📄 Module A
    📄 Module B

You can also set up modular Kirby websites with a structure field or the builder plugin.

In comparison this approach offers some advantages:

• Separate file pools
• Better performance because of nesting
• Anchor links out of the box
• No issues with certain fields/plugins

This plugin assumes you're going to use a module. prefix for your module blueprints. For example site/pages/module.text.yml. In there you can do anything you want—it's just a regular page.

On the modular (mother) pages you iterate over the modules inside the modules container like this:

<?php
  foreach($page->find("modules")->children()->listed() as $module) {
    snippet('modules/' . $module->intendedTemplate(), ['page' => $module])
  } 
?>

As you can see, the modules don't have templates and simply live in for example site/snippets/modules/module.text.php or site/snippets/modules/module.images.php.

I put a simple example installation in a separate branch. Maybe this helps you getting started.

The modules section adds some features to the core pages section:

• Every blueprint starting with module. is available to create
• The module blueprint title is displayed in the info
• The parent is set to the modules container
• The link to the modules container in the headline is disabled
• Small style adjustments to differentiate it from pages

Using the modules section on a page will automatically trigger a built-in hook that creates the modules container page.

sections:
  modules:
    type: modules

To overwrite the module URL you'd have to add a page model for every single module. This plugin overwrites the URL of every module page from example.com/subpage-a/modules/text to example.com/subpage-a#text.

This plugin adds templates with a redirection to the modules container and all the single modules. This way nobody can access the pages directly, not even by guessing the URLs.

By adding extends: module/changeTemplate to the options of your module blueprints, every blueprint starting with module. is available to change to in the page options.

options:
  extends: module/changeTemplate

By default, the module.text blueprint will be the first option when adding a module. You can set it to another blueprint in your site/config/config.php:

return [
  'medienbaecker.modules' => [
      'default' => 'module.text'
  ]
];