I just installed a new Plone site instance onto my personal cloud service to host a website of mine, and all went well, fully installed and running great. Even starting from a systemd unit.
I've been playing around with content creation, and one thing that I find a bit annoying is let's take one of the example folders here "News". If I keep adding a lot of news articles, the pull-down menu at the top of the Plone Blicca interface for "News" then becomes populated with every single News post I create. To eventually remove them, I'd have to go into each of their settings and select not to show it in the navigation, but that feels sort of tedious to do over the span of a long running website.
Is there a way to say limit a single folder from showing any of it's sub-items in the navigation, while still allowing others to display their items? I know there is an option to limit the overall depth of the navigation, but this would effect all the folders, and not just a single one, or a couple of them. I do find this feature very useful for some content, but not content such as News, that I think should just be clickable and open into it's own page listing the summary of all the current News posts.
When using Blicca, I find it easiest to limit the types of content that are shown in Navigation to just "Folders" and "Collections". That's in the site configuration screen under "navigation". It does mean that you have to create subfolders or collections to have a multi-level menu, but that's a trade-off that I find very justifiable.
Thank you, that is a good suggestion that I may consider.
Looking at the Content Types, I can see that they can be edited, and when I create a new field, I can set a default. Unfortunately, with the exclude_from_nav it doesn't seem possible to change/set the default. As this would be the most ideal way, or perhaps if Zope had a side-wide option to select if items should appear in the Navigation by default or not. I feel there are a lot of good uses for it, and if the option does not exist, people will find hacks and workarounds, which technically aren't ideal. I feel like Plone should support such a feature for such use-cases where you want more tight control of the Navigation tree.
I don't mind finding the Dexterity schema for this behavior in the source code, and try to make a modification to make it default to True, but of course if I ever update this Python package, this default will just revert back.
You can not set a default because your content uses the plone.excludefromnavigation behavior. However, TTW, you can disable this behavior and add the field exclude_from_nav (Bool). You can now control this field.
If you want to reuse this strategy for other sites or for many types, it is best to create a custom exclude from navigation behavior in a Plone module and use it instead of the default.