In most cases the level 1 header of the page (h1) would be defined by the page’s title. Thus, following the HTML specifications, there couldn’t be any other h1 following on the same level.
Grav allows level-1 titles in the content: is there some way to disable h1/# in the admin markdown editor? Or is there a technique to block/replace h1s in the template displaying the content?
For now, I simply used CSS to throw errors on unallowed headers in the content, but this technique is far from being optimal. A far better way would be to define a master/first level for the page content in the page.yaml and have both the editor and the parser use the value.