Thread:VisualEditor/Feedback/JavaScriptless experience/reply (4)

First, on editing templates: That's a weak point of VisualEditor: templates are still edited by hand in it. This process is not as fully visualised as it could be. I hope to see this process supported by proper API actions (parsoid probably already provides them, dunno) and workflow definitions.

For instance, imagine that draft submission works like this: submit is often replaced by reason1 and a ... on a talk page. This workflow needs to be defined somewhere. When loading a page, the server needs to pick up such workflow and add 'submit for review' 'approve' 'reject' buttons right on the template itself, and those should take folks to a form or a dialog where they can type in the necessary comments.

Another instance of common workflow is removal of items in the issues template. Some more so-called «interactive templates» (perhaps calling them template workflows is more intuitive) are documented here.

Now, you can see how this process can be useful to JavaScriptless users who would like to edit templates. :-)