Anonymous user
User:FrozenPlum: Difference between revisions
m
no edit summary
imported>FrozenPlum mNo edit summary |
imported>FrozenPlum mNo edit summary |
||
Line 3:
==Self Reminders==
==Examples==
It would be good to have examples in-line, in the parameter's page section, that display a full selection of examples specific to a given parameter. Ideally, these should be named with parameter name first (this allows examples to also be quickly-skimmable for what user want, from different entry points, and makes the reader do less work) followed by "example" or "(Example)".
The logic is to cater to different '''entry points''' to the information:
# '''Comprehensive''' - From in-line, linking to "more" or a larger selection of examples for that parameter and different use cases).
# '''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).
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.
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.
===Templates using Variables and Loops==
The following use Variables (also some use Loops, plus string functions enabled in ManageWiki for parser functions), which will perhaps need simplification and replacement later:
# {{tl|DPL parameter}} – for linking to a parameter (also linked to current DPL syntax template, where the global vars are declared).
# {{tl|DPL syntax}} – for displaying variations on <code>mode=<i>modename</i></code>
#* Am considering replacing with <code><nowiki>{{syntax|text{{=}}value}}</nowiki></code>
# {{tl|And}} – Possibly never would have found this if I hadn't been going through
# {{tl|Key}} - Not sure this template complexity is really necessary at all.
|