Anonymous user
User:FrozenPlum: Difference between revisions
A few updates to my list for when I have the time and energy to go back and do more (not right now, for now was just fixing things to make stuff usable in the meantime).
imported>FrozenPlum mNo edit summary |
imported>FrozenPlum (A few updates to my list for when I have the time and energy to go back and do more (not right now, for now was just fixing things to make stuff usable in the meantime).) |
||
(25 intermediate revisions by the same user not shown) | |||
Line 1:
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 [[User talk:FrozenPlum|Talk]] page.
==Taking breaks==
Hobby (slow) is about all I can manage, edit speed-wise.
==Self Reminders==
* Still need to 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 {{tl|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.
-------
* Still need to work though [[Special:WantedPages]] to fix or change any of these that should or should not be there.
* 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.
* 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.
* '''Note:''' I still 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|Examples]] for more info.
* {{DPL|imagecontainer}} states that the required settings is <code>|openreferences=true</code>.
* {{DPL|linksfrom}} states to use <code>|openreferences=yes</code>.
* {{DPL|openreferences}} states the syntax is <code>|openreferences=yes</code>.
* <code>|openreferences=missing</code> that needs to be added to docs (later). It too currently kicks fatal error with imagecontainer, logged on GitHub.
* I'm tracking {{tl|note}} use at [[:Category:Development]].
==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.
==Examples==
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'''
An idea (that might not work), is that individual examples from "More Examples" ''may'' need their own pages
▲The logic is to cater to different '''entry points''' to the information:
▲# '''Task-based''' - When familiar with DPL3 but looking for a specific starting point to quick copy/paste without having to sift though the pages, TOCs and their corresponding docs sections--A problem with the current Gamepedia DPL3 Manual).
From [[mw:Manual:Creating pages with preloaded text#Loading the preload file|Creating pages with preloaded text]] for sandbox test links, from example pages. "default=Special:Mypage/parametername test" loads "User:Username/parametername test" (a reminder that if already existing, the preload won't work, and to enter a distinct name other than "test" might work.
▲Examples ''may'' need their own pages, perhaps, so they can be categorized per parameter use, and then transcluded into the other pages I mention ^ above. I'm still thinking about a system of sorts for this, it may take some time to hatch a solid plan.
<pre>
The DPL2 site had an ''Examples'' category, but the examples had generic names like "Example 02" which made the task-based approach not feasible because you'd either have to click every one, or users had to sift though manual sections like the Gamepedia Manual. Also, too many in-line can cause issues, so started linking to external pages with a "see example". Some titles are a little strange, like "Example:_Display_images_used" but a good idea for when users want to display images! '''Relevant examples just need to be ''way'' easier to find,''' which is why I'd need some time to think about approaching this in a systematic way. ▼
<inputbox>
type=comment
default=Special:Mypage/inputbox test
type=create
preload=Log
</inputbox>
</pre>
▲The DPL2 site had an ''Examples'' category, but the examples had generic names like "Example
===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:
{{#dpl:
|category=Templates to simplify or eliminate
|count=100
}}▼
'''Note:''' I still need to go back through to determine which requires string functions to be enabled for Parser Functions extension. Once determined, should make sure it is also noted where pertinent.
* [[mw:Extension:StringFunctions#Functions|Merged]] with string functions and need it enabled:
::len, pos, rpos, sub, replace, explode
* [[mw:Extension:StringFunctions#Functions|Not merged]], need to make sure not used:
::pad, urlencode, and urldecode
▲}
|