Change Details

The cells of the table are both Wiki text and Structured data on comments. Values I would prioritize search data on comments since that is the more modern version. However, we need ways to work with wiki text also for backwards compatibility and legacy things. So we should give the user access to ways to read, edit, add. And review the wiki text. Stop one. Some of the functionalities I imagine is that you can see the wiki text of a row to verify everything is how you want Wish it would be. There should be the possibility to add a column. A custom column with a wiki text Templates basically where when creating the new column you would say what the wiki text would be and where the value goes and And then the cell in the column will be a text field where the user can enter a value and this value will be added to this wiki text and this tech wiki text will be automatically added to the final wiki text upon upload. Anotherity is that I would like when confirming which files you are going to upload. In this modal I would like the user to be able to verify both wiki text for each file and the structured data on commas for each file The goal here is to support Wikitexts to give control to the user By having by having a clear answer on which wiki text and which structure data on comments will be created. Both during the editing process per row and Also at the a publish stage the publish publish stage To review everything is as wished for, and in the publish state stage it should be able The user should be able to edit the wiki text by hand. to iron out any errors.

== Summary == Give the user direct visibility into and control over the **wikitext** for each file, alongside the structured data on Commons (SDC) the table edits today. The UI should let the user **read, edit, add, and review** wikitext — both per row during editing, and as a final sign-off step in the publish flow. == Background == Each row's data feeds two outputs at publish time: the file's wikitext page (legacy / human-readable) and SDC (modern / structured). SDC is the priority going forward, but the wikitext side still matters for backwards compatibility, legacy templates, and any cases SDC doesn't cover. Right now the user can't see the wikitext that will be generated, and can't customise it per row. == Requirements == **1. Per-row wikitext preview** * Each row exposes a way to view the wikitext that will be generated from its current values (e.g. an action in the per-row settings dropdown / detail panel). * Read-only is fine for v1; full inline edit can come later. **2. Custom wikitext-template columns** * User can add a **custom column** whose definition is a wikitext template (e.g. `{{Custom-template|param=__VALUE__}}`). * When defining the column: the user provides the template text and marks where the cell value goes (e.g. with a placeholder like `__VALUE__` or an explicit field name). * Each cell in that column is a free-text input; the entered value is substituted into the template, and the resulting wikitext is appended to the file's final wikitext at publish time. * The column behaves like other columns for sort / filter / required / column-defaults purposes. **3. Publish-stage review modal** * Extend the existing publish-confirmation modal so that for each file the user can preview **both** the final wikitext **and** the SDC payload before committing. * In the publish modal, the wikitext must be **editable by hand**, so the user can patch any last-minute issues. * The modal should make it obvious which file's wikitext / SDC is being shown when there are many files. == Out of scope == * A full wikitext WYSIWYG editor; a plain `<textarea>` with monospace styling is fine. * Server-side wikitext rendering; we're showing the source the tool will publish, not a rendered preview. == Acceptance == * Any row exposes an action to view its generated wikitext. * Adding a custom wikitext-template column results in published wikitext containing the template instantiations, one per row. * The publish modal shows per-file wikitext and SDC, with the wikitext editable; published files reflect the user's edits. == Source == User feedback session, 2026-05-10.

The cells of the table are both Wiki text and Structured data on comments.== Summary == Give the user direct visibility into and control over the **wikitext** for each file, alongside the structured data on Commons (SDC) the table edits today. The UI should let the user **read, edit, add, and review** wikitext — both per row during editing, and as a final sign-off step in the publish flow. == Background == Each row's data feeds two outputs at publish time: the file's wikitext page (legacy / human-readable) and SDC (modern / structured). SDC is the priority going forward, but the wikitext side still matters for backwards compatibility, legacy templates, and any cases SDC doesn't cover. Right now the user can't see the wikitext that will be generated, and can't customise it per row. == Requirements == **1. Per-row wikitext preview** * Each row exposes a way to view the wikitext that will be generated from its current values (e.g. an action in the per-row settings dropdown / detail panel). * Read-only is fine for v1; Values I would prioritize search data ofull inline edit can comments since that is the more modern versionme later. **2. However,Custom wikitext-template columns** * User can add a **custom column** whose definition is a wikitext template (e.g. we need ways to work with wiki text also for backwards compatibility and legacy things`{{Custom-template|param=__VALUE__}}`). * When defining the column: the user provides the template text and marks where the cell value goes (e.g. So we should give the user access to ways to read,with a placeholder like `__VALUE__` or an explicit field name). * Each cell in that column is a free-text input; editthe entered value is substituted into the template, addnd the resulting wikitext is appended to the file's final wikitext at publish time. * The column behaves like other columns for sort / filter / required / column-defaults purposes. **3. And review the wiki text.Publish-stage review modal** * Extend the existing publish-confirmation modal so that for each file the user can preview **both** the final wikitext **and** the SDC payload before committing. * In the publish modal, Stop one.the wikitext must be **editable by hand**, Some of the functionalities I imagine is that you can see the wiki text of a row to verify everything is how you want Wish it would be.so the user can patch any last-minute issues. * The modal should make it obvious which file's wikitext / SDC is being shown when there are many files. == Out of scope == * A full wikitext WYSIWYG editor; There should be the possibility to add a column.a plain `<textarea>` with monospace styling is fine. * Server-side wikitext rendering; A custom column with a wiki text Templates basically where when creating the new column you would say what the wiki text would be and where the value goes and And then the cell in the column will be a text field where the user can enter a value and this value will be added to this wiki text and this tech wiki text will be automatically added to the final wiki text upon upload.we're showing the source the tool will publish, Anotherity is that I would like when confirming which files you are going to upload.not a rendered preview. == Acceptance == * Any row exposes an action to view its generated wikitext. * Adding a custom wikitext-template column results in published wikitext containing the template instantiations, In this modal I would like the user to be able to verify both wiki text for each file and the structured data on commas for each file The goal here is to support Wikitexts to give control to the user By having by having a clear answer on which wiki text and which structure data on comments will be created.one per row. * The publish modal shows per-file wikitext and SDC, Both during the editing process per row and Also at the a publish stage the publish publish stage To review everything is as wished for,with the wikitext editable; and in the publish state stage it should be able Ted files reflect the user should be able to edit the wiki text by hand.'s edits. == Source == User feedback session, to iron out any errors2026-05-10.