add-ons and Volto backends might provide fields via behaviors that we consider to be core-ish functionality (that we want out-of-the-box but not enabled by default necessarily)
extending Volto components (e.g. helmet) is possible but that’s a slippery slope that lead to lots of maintenance overhead in projects that customize main Volto components
proposal: document behaviors as an “interface” in Volto. Add-ons can fulfill those contracts and Volto will pick that up and gracefully fall back
Jakob will create a PR with the kitconcept.seo best practices
The new helmet component will use the page title for instance for the meta-title tag, if an add-on fulfills the contract it picks up the behavior attribute
we need:
PR with customized helmet component that provides the sharing tabs but and uses the seo add-on fields