Rendering menus in TYPO3 

Menus as content elements 

You can use a content element to display a menu. In the example data "Page 1" contains a menu of subpages and page "Sitemap" a sitemap content element.

To adjust the templates of these content elements refer to chapter Overriding the default templates of content elements.

Menus within the page view 

A data processor (see also dataProcessing) can be used to provide the data for one or several menus.

For menus usually the menu data processor, which is provided by the TYPO3 Core, is used.

TypoScript configuration of the main menu 

We use TypoScript to configure these menus. The main menu is configured like this:

page {
    10 {
        dataProcessing {
            20 = menu
        }
    }
}

This menu defines that the variable with the default name menu should contain the information about the complete page tree of the current page.

System folders like the "Footer menu" from your example data, special page types and pages excluded from the navigation are excluded.

A complete reference of this menu can be found in the TypoScript Reference: menu data processor.

Fluid partial of the main menu 

In packages/my_site_package/Resources/Private/Templates/Partials/Navigation/Menu.fluid.html you can find the partial that renders the main menu.

A menu usually contains several menu entries. We use the f:for ViewHelper to iterate over all menu entries and render them in turn:

<ul class="navbar-nav me-auto mb-2 mb-lg-0">
    <f:for each="{menu}" as="menuItem">
        <li class="nav-item">
            <a class="nav-link {f:if(condition: menuItem.active, then:'active')}"
               href="{menuItem.link}"
               target="{menuItem.target}"
               title="{menuItem.title}"
            >
                {menuItem.title}
            </a>
        </li>
    </f:for>
</ul>

In each loop the current menu item is stored in variable {menuItem}.

You can use the f:debug ViewHelper to debug what kind of data the variable contains like this:

<ul class="navbar-nav mr-auto">
    <f:for each="{menu}" as="menuItem">
+       <f:debug>{menuItem}</f:debug>
        <li class="nav-item {f:if(condition: menuItem.active, then:'active')}">

The debug output on your page should now look like this:

array(8 items)
    data => array(78 items)
    title => 'My page' (22 chars)
    link => '/my-page' (26 chars)
    target => '' (0 chars)
    active => 0 (integer)
    current => 0 (integer)
    spacer => 0 (integer)
    hasSubpages => 1 (integer)

The following data is of interest:

{menuItem.data}:

Contains the raw data of the database record of the page for the menu item.

{menuItem.link}:

The actual link to the page. For external links it contains the URL.

{menuItem.target}:

This might contain "_blank" if the menu item represents an external link.

{menuItem.title}:

The title to be displayed in the menu. By default the navigation title if set, the title otherwise.

{menuItem.active}

Contains 1 if the page of the current menu item is in the rootline of the current page.

The construct {f:if(condition: menuItem.active, then: 'active')} output the string "active" if {menuItem.active} is set. The syntax might look confusing at first. It is an f:if ViewHelper displayed in the Fluid inline notation.

Preview the page and use the menu 

Whenever you change TypoScript files or Fluid templates, flush all caches:

ddev typo3 cache:flush

Different menu types 

We use the menu data processor to demonstrate different menu types:

• A breadcrumb configured in packages/my_site_package/Configuration/Sets/SitePackage/TypoScript/Navigation/breadcrumb.typoscript and rendered in packages/my_site_package/Resources/Private/Templates/Partials/Navigation/Breadcrumb.fluid.html.
• A footer menu consisting of pages within a selected folder configured in packages/my_site_package/Configuration/Sets/SitePackage/TypoScript/Navigation/footerMenu.typoscript and rendered in packages/my_site_package/Resources/Private/Templates/Partials/Navigation/FooterMenu.fluid.html.