Web Content Articles are localizable to whatever the instance is configured to, but Web Content folders are in a fixed state without any options to localize. Because the parent container cannot be localized, it seems like there is an inconsistency.
Steps to Reproduce
- Create a Web Content article
- Assert that there are localizable fields throughout the content creation process
- Create a Web Content folder
There is only one field without any localization for Web Content Folders.
The parent container (i.e. the web content folder) should be localizable to allow for a more seamless localized experience.