Change Details

e.g. Template:Information could be documented at TemplateData:Information instead of inside the source code of Template:Information. Pros: 1. More standard use of ContentHandler for JSON across projects 2. Document templates without needing to make edits to templates that are potentially transcluded across large swaths of pages 3. Easier to implement custom editors for ContentHandler pages than for portions of wikitext pages. Cons: 1. Would need to have two separate systems - one for the JSON storage, then another to transclude the generated documentation onto template doc pages, e.g. with <templatedata /> or {{#templatedata}} or so (no params needed, because the TemplateData namespace page can be of the same name, like a talk page) 2. Would need to rework the existing editor (sorry, mooeypoo) to work with the new system -------------------------- **Version**: master **Severity**: enhancement **See Also**: https://bugzilla.wikimedia.org/show_bug.cgi?id=50512

e.g. Template:Information could be documented at TemplateData:Information instead of inside the source code of Template:Information. Pros: %%%1. More standard use of ContentHandler for JSON across projects 2. Document templates without needing to make edits to templates that are potentially transcluded across large swaths of pages 3. Easier to implement custom editors for ContentHandler pages than for portions of wikitext pages.%%% Cons: %%%1. Would need to have two separate systems - one for the JSON storage, then another to transclude the generated documentation onto template doc pages, e.g. with <templatedata /> or {{#templatedata}} or so (no params needed, because the TemplateData namespace page can be of the same name, like a talk page) 2. Would need to rework the existing editor (sorry, mooeypoo) to work with the new system%%% -------------------------- **Version**: master **Severity**: enhancement **See Also**: T52512

e.g. Template:Information could be documented at TemplateData:Information instead of inside the source code of Template:Information. Pros: %%%1. More standard use of ContentHandler for JSON across projects 2. Document templates without needing to make edits to templates that are potentially transcluded across large swaths of pages 3. Easier to implement custom editors for ContentHandler pages than for portions of wikitext pages.%%% Cons: %%%1. Would need to have two separate systems - one for the JSON storage, then another to transclude the generated documentation onto template doc pages, e.g. with <templatedata /> or {{#templatedata}} or so (no params needed, because the TemplateData namespace page can be of the same name, like a talk page) 2. Would need to rework the existing editor (sorry, mooeypoo) to work with the new system%%% -------------------------- **Version**: master **Severity**: enhancement **See Also**: https://bugzilla.wikimedia.org/show_bug.cgi?id=50512 T52512