Mobile web & apps both have specific requirements for section identification:
(mobile web / app folks: Please add details to the above!)
Once we have a better understanding of the detailed use cases we should think about how we can support these well in Parsoid HTML.
In a nutshell
https://git.wikimedia.org/blob/mediawiki%2Fextensions%2FMobileFrontend.git/c6ef67a5a0b7bbef2e73ff2287545bc425ab15b9/includes%2FMobileFormatter.php explains all the customisations MobileFrontend does to the HTML from the Parser
headingTransform is the main function you'll want to look at. Essentially we find the top headings and then wrap each section in a div. In theory we could wrap all sections but since we are doing a regexp we simple do it on the top level.
This helps us use the DOM to identify where the lead section, support section collapsing (by identifying a single node that can be hidden or shown).
Is this something we could move along during the MediaWiki hackathon in Lyon? Is there anything actionable yet?
@Jhernandez At grooming the team wasn't sure what to do with this task. Since you were the last comment, can you describe what you think has to happen next to move it along?
I think this can be declined or merged into T78734. I've been working a lot on this in the building of https://trending.wmflabs.org/
There have been some developments related to section *editing* recently, which also triggered some thinking about the corresponding section retrieval APIs: T144104
Generally, I think key to making section retrieval APIs more useful will be to make progress on T114072: <section> tags for MediaWiki sections, which is about marking up semantic <section>s in line with the regular section edit semantics. I recently re-raised this with @ssastry, so it is on the Parsing-Team--ARCHIVED's radar.