This task is about defining the additional work that will need to be done before the discussion-specific-version of the new ToC can be deployed to production.
Work to be done
The requirements that are informing the questions/work to be done described in this section can be found in T303634.
Issue/Technical Need | Deployment Blocker (Y/N) | Potential solution | Next step(s) |
---|---|---|---|
Sometimes the new Vector TOC doesn't display at all | Yes | Already fixed (T305123) | – |
Metadata within ToC cannot be updated without reloading page | Yes | 1. Add ToC data to the action=parse action API output (or confirm that the existing action=parse&prop=sections output is sufficient) 2. Create a JavaScript API for updating the ToC based on this data, and add it to mediawiki.util | Editing + Web engineering to scope this work in T307251 and its sub-tasks (e.g.T307480) |
Improve how ToC is rendered to allow adding discussion enhancements | TBD | 1. Add a PHP hook in SkinComponentTableOfContents to allow DiscussionTools to add HTML fragments to each ToC line 2. Modify Vector to output this 3. Modify the JavaScript API from the previous item to also support this | Define necessity + agree on an approach. This work will happen in T307823. |
Open question(s)
- 1. What work would need to be done in order to adapt the ToC proof of concept @Jdlrobson implemented in T299246#7805640 so that the metadata presented within the ToC updates dynamically based on the state of the discussions present on the page which the ToC appears?
Background
Knowing the work that is required to make the ToC proof of concept functional, will help the Editing Team decide how to create prototypes for the designs created in T299814 for use in the usability testing that will happen in T293520.
Done
- Answers to all ===Open question(s) are documented on this ticket
- The technical work that will need to be done before the Editing Team can implement the requirements T303634 lists are documented in this task's === Work to be done section