Jump to content
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

m
no edit summary
imported>FrozenPlum
m (Update my reminders to myself before my brain eats them lol.)
imported>FrozenPlum
mNo edit summary
Line 13:
 
==Examples==
It would be 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. Ideally, these should be named with parameter name first, followed by "example" or "(Example)"; (this allows examples to be quickly-skimmable from different entry points,. Entry points like the [[Examples]] page, whereand it[[:Category:Examples|Examples]] wouldcategory make(which will have different organization). Having the key words at the beginning of each page title makes readers do less work (not having to read past "Example:_" every time, to find what they want) (they can ignore the word "Example/example" if placed at the end.
 
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 – ExamplesBasic examples still saystay in-line, justbut alsoeach linkingparameter section links to a "more examples" page, for a larger selection of and different use cases/examples for thatthe given parameter.
# '''Task-based''' – Audience: Moderate to advanced and/or ''frequent'' visitors, ''already'' having read the parameter sections. – Allows a fast starting point/reference, or quick copy/paste of example code to adapt, without having to sift though the longerlong pages or their /TOCs (Aa problem with the current Gamepedia DPL3 Manual).
 
IndividualAn idea (that might not work), is that individual examples forfrom "More Examples" ''may'' need their own pages, so they can be categorized by parameter use,. andIf thencategorized transcludedby orparameter DPL3 includeduse, 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 hatchget each bit of code to go into a solidsandbox, with preloaded text, for someone to try planmanipulating.
 
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.
Anonymous user
Cookies help us deliver our services. By using our services, you agree to our use of cookies.