Describe the issue
We want to start adding .md files to plugin parent pages to help improve search. These will include the basics of using the plugin and some FAQs. Currently, some plugins, such as AWS, have a "How to use this plugin" section. That header is currently hardcoded as an H2 and does not include the plugin name. A couple of things:
- Can we pipe in the plugin name into the header, similar to what is done just below with the blueprints?
- Can we make this an H1 controllable within the
markdown-container rather than inserted onto the page without control from the plugin's repo (If so, we can forget point 1)? It'll be easier to modify if everything is controlled from the plugin's resources.
- Is it just parent plugin pages that have the capability for these markdown containers?
@vfanucci, is there anything else to add from the SEO perspective? Titles and descriptions we can already control from the plugin's resources, and fallbacks are in place in case there is no metadata.
Describe the issue
We want to start adding
.mdfiles to plugin parent pages to help improve search. These will include the basics of using the plugin and some FAQs. Currently, some plugins, such as AWS, have a "How to use this plugin" section. That header is currently hardcoded as an H2 and does not include the plugin name. A couple of things:markdown-containerrather than inserted onto the page without control from the plugin's repo (If so, we can forget point 1)? It'll be easier to modify if everything is controlled from the plugin's resources.@vfanucci, is there anything else to add from the SEO perspective? Titles and descriptions we can already control from the plugin's resources, and fallbacks are in place in case there is no metadata.