User:FrozenPlum: Difference between revisions

Content added Content deleted

Inline

Revision as of 23:57, 27 March 2022

This is not my wiki, I'm just a Miraheze user helping to get some content moved over. Feel free to reach me on my Talk page.

Self Reminders

Examples

I think it would be good to have example pages named after their parameters 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 example category) and find what they're looking for. An issue behind the former sites, was needing to comb though pages, use the TOD repeatedly for multiple sections, click every example, or use find in-browser to look at for the corresponding section and then example. The DPL2 site had an examples category, but the examples had 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 "see example" statement 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 param use 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.

=Templates using Variables and Loops

The following use Variables and Loops (plus string functions enabled in ManageWiki for parser functions), which will perhaps need replacing later:

{{DPL parameter}} – for linking to a parameter (also linked to current DPL syntax template where the global vars are declared).
{{DPL syntax}} – for displaying variations on mode=modename
- Am considering replacing with {{syntax|text{{=}}value}}
{{And}} – Possibly never would have found this if I hadn't been going through the pages and templates individually... there seems to be no tracking categories for some extensions.

@@ Line 3: / Line 3: @@
 ==Self Reminders==
 ==Examples==
-I think it would be better to have example pages named after their parameter names if those examples pertain mostly to that parameter, so users can look for a parameter name they want examples for (in the examples category) and actually '''find''' what they're looking for, lol. This was a big pet peeve behind the other sites, needing to comb exhaustively though long pages, click every example, or use find and then look at what corresponding section it was found in, to find something relating to a specific DPL param. Ideally, I'd like to categorize based on each param used regardless of example name, 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.'''
+I think it would be good to have example pages named after their parameters 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 example category) and '''find''' what they're looking for. An issue behind the former sites, was needing to comb though pages, use the TOD repeatedly for multiple sections, click every example, or use find in-browser to look at for the corresponding section and then example. The DPL2 site had an examples category, but the examples had 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 "see example" statement 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 param use 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.