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
m
Add the infobox sample reminder for when I get to this portion
imported>FrozenPlum mNo edit summary |
imported>FrozenPlum m (Add the infobox sample reminder for when I get to this portion) |
||
Line 11:
==DPL3 Code Demos==
I'm aware almost all use examples are currently broken, this is intentional until they can be replaced because this resource is in development. It is not ideal to have manual pages manifest inside the manual itself (this adds a level of unnecessary complexity for new users). Ideally, it would be optimal to have different example categories to draw from (e.g., fruit, pastries,
==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. <s>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</s> (there are practical reasons for this as-is).
The logic to rejigging the examples, is to cater to different audiences and '''entry points''' to the information:
Line 21:
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.
| |||