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.DynamicPageList3 Manual talk:Feedback: Difference between revisions
DynamicPageList3 Manual talk:Feedback (view source)
Revision as of 04:49, 18 April 2022
, 2 years agono edit summary
imported>FrozenPlum mNo edit summary |
|||
Line 119:
:Sorry [[User:Lens0021|Lens0021]], sounds interesting! Though I have given back my temporary reins (I'm having cognitive issues that are making things hard to manage and edit at the same time). CA should be able to see requests you make, though. Have fun and cheers! :) [[User:FrozenPlum|FrozenPlum]] ([[User talk:FrozenPlum|talk]]) 10:56, 17 April 2022 (UTC)
::I'll just add my personal opinion on using gadgets/js for the examples - having gone the gadget and JS route for other things before, I've seen both JS convention change and resource loader method change resulting in broken features and scripts often, sometimes every MW update. For us (users on different wikis) this causes extra maintenance items to be maintained that can have a cascading effect across the site. I'm still personally leaning towards what I mentioned before, keeping things as simple as possible, using built-in MediaWiki features wherever possible, to reduce any extra maintenance overhead. I have been converting templates away from third-party extensions not bundled with MediaWiki for this same reason (Variables extension was formerly relied on for a number of templates and all important links, but its future is uncertain, loops also used which has recently been limited for causing issues). I feel, if there's a way to do these things using built-in methods, or extensions packaged with MediaWiki itself that are expected to maintain long-term functionality without breaking changes on updates, this is the way I'd personally prefer to go over the js/gadget route, given, I've been down that route a number of times before (and contacted CA about some JS stuff before for the same reason).
==A few other notes==
I was intending to convert most examples to parser function syntax, given most want to be able to do more than the parser tag method allows (I have not run into one person yet who this hasn't been the case with). This was a common complaint with the old manual that I intended to rectify (that examples weren't usable because it didn't present content in the most-needed syntax). From a teaching/learning perspective, it's easier to learn the best-practice/flexible parser function syntax first, and then simplify from there if desired, than it is to learn the simple syntax and have to re-learn how to do things in parser function syntax, afterwards (easier to give a horse their head to run than it is to take it away). Also:
* I intentionally didn't add syntax highlighting to examples, since parser function sytax would make little to no use of this (and there is one part {{DPL|format|in the manual}} that explicitly states "you can also use HTML syntax for the tags, although this is discouraged", though I don't know the reason for that, I had planned asking CA if he knew why that was the case). If HTML tags should be removed, there'd be no sense to add this syntax highlighting, it would highlight nothing.
* More importantly, I also didn't add syntax highlighting to the examples because the examples are preloaded into source-edit sandbox sections, for users to manipulate, and I wanted them to be able to focus on the examples and not get caught up with extra unexplained formatting, divs, tags, classes tags etc (which is why I would recommend not adding anything other than a <code><nowiki><pre></pre></nowiki></code> around these (otherwise would need to be explained in the examples and could confuse the learning at hand, which is why I left it off intentionally--though I did initially consider it).
* I also wouldn't recommend placing the results of examples in blockquotes (or any other formatting) for appearance’s sake. I'm aware this would be nicer to look at, however since blockquotes are part of wiki syntax, and wiki syntax is used in examples (and pre-loaded to sandbox too)... it would cause a need to explain these again, each time that blockquotes are not part of the result, which would quickly become cumbersome and redundant (nor would doing in one place or once per page suffice, since few read manuals in their entirety, rather using them for reference). I had concerns about even doing this for a "pre" tag, but that's a bare necessary (that I still need to explain somewhere, but forgot to). This is the reason I'm keeping these as simple as is possible, unless the example itself is complex, in which case the focus of any learning complexity should (hopefully) only be the example content. Another of complaint with the old manual was that users couldn't coherently source-edit to see the contents of an example, and better understand what it was doing because there was too much either added/extra "stuff" going on, or unexplained stuff not explained/linked. Many gave up on the extension as a result. I'd like to (hopefully) avoid those same pitfalls.
Given I have cognitive and communication problems, it's very hard for me to stop and explain my rationale with each idea/suggestion. My working memory and multitasking ability is frankly terrible, stopping and starting to do so is very had for me (a personal flaw from my difficulties, that I wish I could change). I know the logic behind why I'm approaching things a certain way, unfortunately my ability to think about, synthesize, and communicate this coherently in writing is also impaired, it takes more time than I have to sit down and just edit a bit each day, since I also have problems doing that for length of time (or writing at all). It can take me longer than an hour or two to write a reply like this due to my neuro-thing, which is then hard for me to continue the other work. My apologies for not having the bandwidth (nor ability) to explain better and switch between tasks (I hadn't anticipated this need so early on this wiki, and maybe I should have). These are the reasons I'm needing to hit pause, it's better if CA or someone else oversees, and I can work on bits and pieces on my own wiki at my leisure. I can always copy things I'm working on over later if they look useful, and if the content hasn't substantively taken a different direction meanwhile. If it has, I can keep my version for my own (and my wiki's) personal use, so the effort is good either way. :) [[User:FrozenPlum|FrozenPlum]] ([[User talk:FrozenPlum|talk]]) 04:49, 18 April 2022 (UTC)
| |||