User:FrozenPlum: Difference between revisions

m
Update before copying out in case this site needs to be reset
imported>FrozenPlum
mNo edit summary
imported>FrozenPlum
m (Update before copying out in case this site needs to be reset)
Line 3:
==Self Reminders==
==Examples==
I think it would be bettergood to have example pages named after their parameter namesparameters if those examples pertain mostly to that parameter, and categorized appropriately. The logic for this, is so users can look for a parameter name they want examples for (in the examplesexample category) and actually '''find''' what they're looking for, lol. This was a big petAn peeveissue behind the otherformer sites, was needing to comb exhaustively though long pages, use the TOD repeatedly for multiple sections, click every example, or use find andin-browser thento look at whatfor the corresponding section itand wasthen foundexample. inThe DPL2 site had an examples category, tobut findthe somethingexamples relatinghad generic names like "Example 02". The DPL3 site had examples in-line (though too many probably would cause issues), so started linking to external pages with a specific"see DPLexample" paramstatement with no category and vague titles like (Example:_Display_images_used) which said little about which parameter was being employed (there are several ways to display images). Ideally, I'd like to categorize based on each param useduse regardless of example name, use clearer example names (if possible), so that lists can be generated for examples that uses x parameter, at least for the ones other than criteria for page selection, for example. I'll have to give that some more thought as to how this might work, or not work. '''Relevant examples just need to be ''way'' easier to find.'''
 
Perhaps also some different, carefully curated subcategories for certain things, examples using images, examples by namespace/notnamespace, examples based on template use, etc.
Anonymous user