Anonymous user
This wiki has been automatically closed because there have been no edits or log actions made within the last 60 days. If you are a user (who is not the bureaucrat) that wishes for this wiki to be reopened, please request that at Requests for reopening wikis. If this wiki is not reopened within 6 months it may be deleted. Note: If you are a bureaucrat on this wiki, you can go to Special:ManageWiki and uncheck the "Closed" box to reopen it.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 m (Typo fix and replace my manual list with the category I'm using to track templates and pages that use other extensions.) |
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).) |
||
| (16 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==
==Examples==
The logic to rejigging the examples, is to cater to different audiences and '''entry points''' to the information:
Line 20 ⟶ 34:
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.
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.
<pre>
<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 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.
Line 31 ⟶ 56:
}}
* [[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
| |||