Remove Home tab from navigation in Volto

What's the right way to hide the home tab with Volto?

1 Like

Like in Plone Classic, remove it from the actions.

<?xml version="1.0" encoding="utf-8"?>
<object xmlns:i18n="http://xml.zope.org/namespaces/i18n"
        meta_type="Plone Actions Tool"
        name="portal_actions"
>
  <action-provider name="portal_actions" />
  <object meta_type="CMF Action Category"
          name="portal_tabs"
  >
    <object meta_type="CMF Action"
            name="index_html"
            i18n:domain="plone"
    >
      <property name="visible">False</property>
    </object>
  </object>

Fair enough!
because

#navigation > div > ul > li:nth-child(1) > button {
    display: none;
}

wasn't feeling right.

2 Likes

In the forum a hint on the location where the snippet has to go (not in Volto but into the backend!) a link to the docs may help others.

Using Generic Setup XML is not covered in Plone 6 docs only actions here
Portal Actions — Plone Documentation v6 (ZMI or ClassicUI)
Portal Actions — Plone Documentation v6 (API)

For Plone 5 you find
https://5.docs.plone.org/develop/plone/functionality/actions.html
And the Generic Setup syntax:
https://5.docs.plone.org/develop/addons/components/genericsetup.html#actions-xml

So until then ClassicUI is a valid option if you can reach it. Not just "like" but it is obvious not in the filesystem code.

I opened a Docs ticket #1896 to at least add Generic Setup to the Glossary as starting point, until more docs are updated.

Should it be made clearer that GenericSetup is the preferred way to customize policies when creating a theme package? And also that you can import/export the XML with all your customizations in the ZMI and use it to populate the various profile settings?

For us this is maybe obvious. But for our new Volto only audiences this is buried in the backend and in Docs <= Version 5. We need to lift that to Plone 6 backend without too much overhead.

Actions is a good starting point without postponing it until we have all the bells an whistles (and then it may confuse) What I actually did not search was the training section. But we need this as reference docs.

1 Like

@stevepiercy pointed to an existing stalled ticket related to the state of the Generic Setup docs. Port GenericSetup docs · Issue #1754 · plone/documentation · GitHub it is already converted to MyST and needs backend love…