Change Details

This Sections epic has 2 goals 1. As a user, I'd like to have easy access to pre-parsed sections: headings and plain text below 2. As a user, I'd like to have the above pre-parsed sections enriched: include paragraphs, links and references Dependencies [] Credibility work might need parsed out references, figure out the needs first to join efforts, see ticket: https://phabricator.wikimedia.org/T346040 Checklist [] Review existing plain text PoC, sync with Ruairi [] Review existing Section PoC, see code in documentation folder MR POC [] Decide wether to include the first version of list and table parser as part of this effort [] Investigate schema options (schema.org (hasparts), options, bring back to team) [] document approach and implementation suggestions + 2 examples/approach for pm [] bring outcomes back to team and decide approach [] other engineer to test [] add to Structured Contents dev [] pm sign off [] add to Structured Contents prod Notes [] rtl languages might use opposite section order (may require own investigation)

> OKR 4.3 This Sections epic has 2 goals 1. As a user, I'd like to have easy access to pre-parsed sections: headings and plain text below 2. As a user, I'd like to have the above pre-parsed sections enriched: include paragraphs, links and references Dependencies [] Credibility work might need parsed out references, figure out the needs first to join efforts, see ticket: https://phabricator.wikimedia.org/T346040 Checklist [] Review existing plain text PoC, sync with Ruairi [] Review existing Section PoC, see code in documentation folder MR POC [] Decide wether to include the first version of list and table parser as part of this effort [] Investigate schema options (schema.org (hasparts), options, bring back to team) [] document approach and implementation suggestions + 2 examples/approach for pm [] bring outcomes back to team and decide approach [] other engineer to test [] add to Structured Contents dev [] pm sign off [] add to Structured Contents prod Notes [] rtl languages might use opposite section order (may require own investigation)

> OKR 4.3 This Sections epic has 2 goals 1. As a user, I'd like to have easy access to pre-parsed sections: headings and plain text below 2. As a user, I'd like to have the above pre-parsed sections enriched: include paragraphs, links and references Dependencies [] Credibility work might need parsed out references, figure out the needs first to join efforts, see ticket: https://phabricator.wikimedia.org/T346040 Checklist [] Review existing plain text PoC, sync with Ruairi [] Review existing Section PoC, see code in documentation folder MR POC [] Decide wether to include the first version of list and table parser as part of this effort [] Investigate schema options (schema.org (hasparts), options, bring back to team) [] document approach and implementation suggestions + 2 examples/approach for pm [] bring outcomes back to team and decide approach [] other engineer to test [] add to Structured Contents dev [] pm sign off [] add to Structured Contents prod Notes [] rtl languages might use opposite section order (may require own investigation)