User:FrozenPlum

This is not my wiki, I'm just a Miraheze user helping to get some content moved over. Feel free to reach me on my Talk page.

Self Reminders

Taking breaks

Hobby (slow) is what I can manage, edit speed-wise.

DPL3 Code Demos

On MediaWiki.org. It is best practice to begin with the simplest examples possible to avoid ambiguity and any level of unnecessary complexity. This type of approach shifts the focus from the output to the learning at hand because the concepts used in the examples are highly intuitive and easily understood enough to mostly be ignored. It is best practice to use simple concepts in examples, and only add complexity to the learning itself (not the examples) as the complexity of the task increases.

ReplaceText / AWB

Individual example page headings need swapped to 3 levels === (h3), since the preload itself has a header field at 2nd level (h2). The example and result should ideally be under whatever the user chooses to name it.
- example pages source text now needs updated, the S that says User:Username/Sandbox to a lowercase s (User:Username/sandbox) as the link extension is configured.

This is the example preloaded for testing, press "Show Preview" to see the example working (at the bottom of the page). If you save this page, it saves as a new section at the bottom of your User:Username/Sandbox

Other

° Need some dark mode css at some point.

Go through and check consistency, clarity, style etc for text and examples.
Some language or descriptions that aren’t quite right yet in examples.
Controlling output volume has several temporary {{hr}} sections until the heading colors for H4 are changed (I'd suggest the same size as H3 but maybe dark blue, or some other deeper color, just something that sets these apart better and gives a visual break to separate the subsections so they don't run together visually.
The pages for submitting a bug report, installing, getting extension (its MW page, github), giving feedback etc., are not here yet and where this all goes might get juggled around depending on UO's feedback.
Still need to work though Special:WantedPages to fix or change any of these that should or should not be there.
There probably should be a page explaining how to enable DPL3 on Miraheze (or linking to MH ManageWiki docs and at least saying what tab the extension is found in).
Still need to add notes to areas where there's code but a non-working examples.
Add Creating pages with preloaded text to docs for {{ViewTest}} when it has docs.
Go back & determine which examples require string functions to be enabled for Parser Functions extension. Once determined, should make sure it is also noted where pertinent.
Merged with string functions and need it enabled:

len, pos, rpos, sub, replace, explode

Not merged, need to make sure not used:

pad, urlencode, and urldecode

Note: I need to go back through to determine which templates/page (if any) require string functions to be enabled for Parser Functions extension. Once determined, should make sure it is also noted everywhere pertinent (some examples may rely on this, it is not default turned on at MH). See Examples for more info.
imagecontainer states that the required settings is |openreferences=true.
linksfrom states to use |openreferences=yes.
openreferences states the syntax is |openreferences=yes.
|openreferences=missing that needs to be added to docs (later). It too currently kicks fatal error with imagecontainer, logged on GitHub.
I'm tracking {{note}} use at Category:Development.

Examples

Good to have "more examples" links in-line, in each parameter's page section, that display a full selection of examples specific to a given parameter?

The logic to rejigging the examples, is to cater to different audiences and entry points to the information:

Comprehensive – Audience: Average or infrequent visitors, needing to re-read parameter sections – Basic examples still stay in-line, but each parameter section links to a "more examples" page, for a larger selection of different use cases/examples for the given parameter.
Task-based – Audience: Moderate to advanced and/or frequent visitors, already having read the parameter sections. – Allows a fast starting point, or quick copy/paste of example code to adapt, without having to sift though long pages/TOCs (a problem with the current Gamepedia DPL3 Manual).

An idea (that might not work), is a quick-start guide or tutorial (essentials), but I'd have to do (r) task analysis to determine what all would be considered essentials.

An idea (that might not work), is that individual examples from "More Examples" may need their own pages, so they can be categorized by parameter use. If categorized by parameter use, these can be transcluded into the other pages mentioned ^ above. I'm still thinking about a system of sorts (and if this is even feasible) for this, it may take some time. Ideally, (also may not be feasible) I'd like a way to get each bit of code to go into a sandbox, with preloaded text, for someone to try manipulating.

The DPL2 site had an Examples category, but the examples had generic names like "Example 002" which made the task-based approach not feasible because you'd either have to click every one, or had to sift though manual sections like the Gamepedia Manual currently. Also, too many in-line examlpes can cause issues. Some titles are a little strange, like "Example:_Display_images_used" but that type of categorization and/or page might be a good idea for when users want to see different ways to display images! Relevant examples, to the task at hand, just need to be way easier to find, which is why I'd need some time to think about approaching this systematically.

Templates using Variables and Loops

The following were found to use other extensions, see Category:Templates to simplify or eliminate for which uses which. Variables extension's future is uncertain, so these templates may need to be simplified, adjusted, or eliminated: