Exactly that! The Plugin Library method is v. lightweight. No problem adding dozens.
Plugins themselves can be composed of tiddlers that are plugin libraries (I think, guess I should try this). So if each plugin library included a plugin that referenced other libraries, a person starting from just one library might eventually discover all the other libraries, including ones that don’t make it to this list.
1 Like
Yay - a super library! Should the plugin be titled MOAL or Alexandria? 
Folks,
Arriving late to this conversation, existing as I do in the Australian time zone, with a fresh mind after a good nights sleep, I gave this topic a quick scan.
As a result I created plugins.tiddlyhost.com as “libraries” was not available. This is a hub listed public wiki where I intend to develop some plugin resources including collected plugin library resources. This will be about plugins and libraries rather than the plugins themselves.
I will soon start an appropriate discussion for people to discuss and contribute to plugins.tiddlyhost.com but we can use this one for now as it is On topic, for now.
I have a range of ideas to make this a useful and informative site. Feel free to make suggestions.
2 Likes
Bingo! Nice one! A snap to use. I’ll comment more later.
Meanwhile … some other plugin libraries to add (also for @Mohammad to note) …
TT
2 Likes
I added those two thanks @TiddlyTitch
I wonder if there is a way to allow use to search the contents of libraries, even if we need to generate an index? The two you gave me and the relink one currently contain only one plugin.
Right.
SoundCite is just one.
Andrew Harrison is 14.
TT
@TW_Tones, well I dunno. Yes, IF it were easy for you.
I’d say that IF Plugin Library use got more uptake that summary data on each library might be useful?
One of those summary items being “no of plugins” (For instance SoundCite has 1 and the CPL currently has 303 — that is some kind of difference! 
)
TT
@TW_Tones, great stuff!
I like that, up front, on load, you can see the available Plugin Libraries and, via the tag mechanism, add them ALL to a TiddlyWiki at once …
I have a few suggests. (As usual, not being the person who can do it, I feel slightly weird suggesting what I can’t myself do.)
-
Information. I think as the number of Plugin Libraries increases it will be an issue knowing what is in them. How many items? What do they do?
-
I don’t know how you’d do it in an automated way but showing a count of the number of plugins in a library would likely be v. useful?
-
Maybe the descriptive text field of each library could be put next to it using a
<details>thing? Sorta like this …
Best, TT
1 Like
- Totally agree
- Could do this like a curator but ideally seek a summary from the Library owners.
- There maybe a way to programmatically extract contents and make that searchable.
- Agreed a manual count will be a good start
- Sure
Yes, I have an idea here that you need not install the library in a wiki but extract a plugin on this wiki and move the plugin. However the libraries have the advantage of detecting updates.
- With the local storage active it would retain a set of plugins commonly used by you. A kind of holding bay.
More to come.
[Edited] Some suggestions manually applied ! see https://plugins.tiddlyhost.com/#
1 Like
Good you willing to do that and did it for Plugins For TiddlyWiki
I think it might be worth asking on Github that the Plugin Library authors fill in a “number-of-items” field? You get the idea?
TT
Right.
IMO it is far better that the AUTHORS write the summaries.
Why? Because curation, though actually better, is difficult to maintain unless we had a person who loves that kind of thing. Curating software (ongoing) that changes is a somewhat thankless task 
?
The Chinese library is a good case to think about since it references over 300 sources. HOW would one document that???
TT
@TW_Tones IF you are willing to maintain the TW Plugin Libraries wiki long term then I’d ask under “meta” here to get it added something like … …
A thought, TT
I do, but they can already include details in the library tiddler, however I think the library tiddler is not updated “over the wire”, like the plugins.
I am willing, since libraries themselves don’t change or new ones don’t appear too often, at least up to now. The Content of the library and plugins remain in the control of the publisher.
- I would raise a ongoing discussion that would allow users to submit libraries via talk.tiddlywiki
I believe as soon as we build a way to publish plugin libraries from a single file wiki there could be a boom in libraries.
- Especially to also share macros - I have already secured macros.tiddlyhost.com for some ideas there, not even started yet.
1 Like
Right.
The OP basically listed plugin libraries and what you have done is added to that in creating a permanent TW Plugin Library of Libraries.
I think. over time, it will be widely used.
From my point of view the mechanism of it is lightweight. It works well.
It is maybe not as known yet as it might be.
IMO it solves a bunch of issues that TW has on being informationally fragmented on how to enhance it.
In short, what you have done is a definite step in a good direction!
Opinion, TT
@TW_Tones is willing to maintain a resource of Plugin Libraries …
It is good! Useful. Very.
I hope it will spark interest in them and increase their use and creation.
TT