I may recommend to ignore quotes when it is possible (e.g <<mymac par1>> instead of <<mymac "par1">>)
decide to use single/double consistently ( I use " for strings and ' when a string with " is passed)
Widget parameters
when pass another widget as a parameter, use single quote. See below example
A fun example
Write a toggle button in three lines to switch the text of My Tiddler between two values: show/hide and properly show the button caption based on those values.
The reason for my suggestion is that I disagree with the first suggestion to remove the quotes from a single word parameter.
I may recommend to ignore quotes when it is possible (e.g <<mymac par1>> instead of <<mymac "par1">>)
There is a reason, why the TW core consistently uses quotes even for single word params, because they are much more robust for new users, if they make changes and insert spaces to the params.
So it highly depends, if you use the wiki yourself only or if you prepare wikis for others. There’s a difference in the best practice “rule set”
I prefer this text='<$action value="this"/>' to this text="""<$action value="this"/>"""
because quotes bloat terribly in the written file. Each one becomes \\\" while single quotes remain '.
That means """this""" contains 22 more bytes than necessary, so I reserve triple quotes strictly for encapsulating $placeholders$.
Yea, this may be true for the core, but for normal users I personally like 3 double quotes “”" more like the single quote ’ … From my point of view they are much more visible and indicate, that something special is going on. …
From the “number of bytes” point of view, you are right. We have about 1500 occurrences of “triple double quotes” in the TW repo / tiddlers. So we may be able to save close to 30kByte … Which would be a minified 3rd party library