User:FrozenPlum: Difference between revisions

It would be good to have "more examples" '''links''' in-line, in theeach 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 followed by "example" or "(Example)" (this allows examples to also be quickly-skimmable forfrom whatdifferent userentry wantpoints, fromlike differentthe entry[[Examples]] pointspage, andwhere makesit thewould readermake readers do less work) followedto byfind "example"what orthey "(Examplewant)".

The logic is to cater to different audiences and '''entry points''' to the information:

# '''Comprehensive''' – Audience: Average or infrequent visitors, needing to re-read parameter sections – Examples still Fromsay in-line, just also linking to "more examples" orfor a larger selection of examples for that parameter and different use cases)/examples for that parameter.

# '''Task-based''' -– WhenAudience: familiarAdvanced withor DPL3frequent visitors, ''already'' having read the parameter sections. but looking– forAllows a specificfast starting point/reference, toor quick copy/paste of example code to adapt, without having to sift though the longer pages, TOCs andor their correspondingTOCs docs sections--(A problem with the current Gamepedia DPL3 Manual).

Individual examples for "More Examples" ''may'' need their own pages, perhaps, so they can be categorized perby parameter use, and then transcluded or DPL3 included, into the other pages I mentionmentioned ^ 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 02002" 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 currently. Also, too many in-line examlpes 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 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 in a systematic waysystematically.