Not every module needs to be visible everywhere. The editor distinguishes between a simple assignment to all pages and displaying only on the home page, i.e., the homepage.
What you will learn
- Select one of the two supported display scopes.
- Verify a homepage module using sample page types.
- Understand the difference between the design preview and actual Joomla menu items.
- Recognize limitations when importing complex assignment rules.
What both options mean
All pages
The module is part of the global layout. It is suitable, for example, for the main menu, contact information in the footer, or a login form that should be accessible throughout the entire website.
Homepage only
The module should only appear on the home page. Typical examples include a large hero slideshow, seasonal offer, or a welcome block.
How to set up and check module assignment
- Select the module on the canvas or in the Layers tree.
- Open the right inspector using the small settings icon on the selected module and locate the assignment option.
- Choose either "all pages" or "homepage". The editor does not accept a third, custom option.
- In the top bar, switch the sample page type from the home page to another sample content type.
- Verify that the module designated for the homepage only disappears in other sample views. Then switch back to the home page sample view.
What the editor check does not do
The sample page switcher does not generate articles, products, or menu items, nor does it crawl the live website. It simply changes the inert sample content in the componentbox and hides modules configured for the homepage only accordingly.
After installing the exported template, Joomla works with its own home menu item. The editor writes a straightforward intent—"everywhere" or "home"—rather than a list of individual menu items. Therefore, before going live, it is recommended to verify assignment rules in live Joomla where actual navigation already exists.
Joomla itself allows for more complex combinations, such as displaying a module on selected sections only. The editor in its current form does not represent these granular combinations. An import reads supported values from the found record regardless of its published state, but it can only convert assignments set to "all pages" or "homepage".
Practical decisions
Start with a question: does the user need this element on every subpage visit? If so, choose all pages. If it is a prominent introductory element that would take up unnecessary space on subpages, use homepage only. Settings can be changed later, but during testing, also check whether hiding the module leaves an empty row behind.
Example: main navigation and primary contact information usually belong on all pages, as visitors would struggle to navigate subpages without them. Conversely, a large hero image with a banner slogan should be limited to the homepage. If both modules are in the same row, switch to a different sample page and inspect the result: the homepage module disappears, but the global navigation must remain fully functional. This helps identify rows that look empty or have awkward spacing after assignment changes.
Result
The module remains visible across all sample views if configured for all pages, or hides outside of the home sample view if set to homepage only. At the same time, you understand this is a design preview rather than a direct modification of live menu items.