Change Details

We should write an ADR ([[https://adr.github.io/|Architectural Decision Record]]) documenting the overall architecture of the Chart extension, and why we made those choices. This ADR could be a wiki page on mediawiki.org, or a Markdown file in the extension repo. [ ] Write an ADR that documents the architecture of the Chart system, including: [ ] The relationship between the extension and the CLI script [ ] Why we chose shelling out over other approaches [ ] The wikitext syntax and why we chose it (T368350) [ ] How and where data is loaded, and why [ ] How the graph SVG is delivered to the article (inlined vs loaded from a URL) and why

We should write an ADR ([[https://adr.github.io/|Architectural Decision Record]]) documenting the overall architecture of the Chart extension, and why we made those choices. This ADR could be a wiki page on mediawiki.org, or a Markdown file in the extension repo. [ ] Write an ADR (or multiple smaller ADRs) that documents the architecture of the Chart system, including: [ ] The relationship between the extension and the CLI script [ ] Why we chose shelling out over other approaches [ ] The wikitext syntax and why we chose it (T368350) [ ] How and where data is loaded, and why [ ] How the graph SVG is delivered to the article (inlined vs loaded from a URL) and why

We should write an ADR ([[https://adr.github.io/|Architectural Decision Record]]) documenting the overall architecture of the Chart extension, and why we made those choices. This ADR could be a wiki page on mediawiki.org, or a Markdown file in the extension repo. [ ] Write an ADR (or multiple smaller ADRs) that documents the architecture of the Chart system, including: [ ] The relationship between the extension and the CLI script [ ] Why we chose shelling out over other approaches [ ] The wikitext syntax and why we chose it (T368350) [ ] How and where data is loaded, and why [ ] How the graph SVG is delivered to the article (inlined vs loaded from a URL) and why