Talk:Meza/All sub pages

Latest comment: 8 months ago by GregRundlett in topic Update Documentation

Update Documentation

edit

What's the best way to create a plan and track the updating of the documentation here?

Updating this documentation is part of issues/3 at the freephile fork of meza.

I tried to subst the Special PrefixIndex listing. That doesn't work.

I copy/pasted the output (list of links) from the page - and that does create a static list, but then you can't easily turn it into a table where you could add columns for 'priority', 'doc category', 'defunct', 'status', 'assignee'. To do that I suppose we need to use off-site tools to create such a table; then paste it here - which just means it would be easier to use Google Sheets from start to finish.

In my mind, the baseline concept of tracking the update of content would be to create a table similar to what the {{Event }} creates, only with relevant columns for page freshness and importance.

There's a {{Status }} that could be useful But, hard to find any other useful templates, and we can't easily mass edit this collection (e.g. Special:ReplaceText) to initialize every page as 'status in progress'. Do you want to make 60 manual edits?

There's a similarly useful template {{Update }} that could be used to flag content as outdated, but does not adequately transform from "this is out of date" to "this was just updated" (no capability to show "freshness" as in food).

The {{As of }} template can be used to track temporal info... A better approach would be to track version compatibility like in Minty Docs or any other software documentation platform that shows documentation by version compatibility.

Best practices would encourage the use of Codex Icons for any iconography.

Greg Rundlett (talk) 15:39, 22 April 2024 (UTC)Reply

Return to "Meza/All sub pages" page.