A modular approach! * core (minimum essential tools) * themes * languages * plugins ** highlight.js ** katex ** codemirror
<https://miro.medium.com/max/1740/1*2uJmEEUimE1S0S0MfNNtFQ.png> url: https://medium.com/5000-things/learning-from-lego-a-step-forward-in-modular-web-design-d8ff953f45a8 On Friday, September 13, 2019 at 10:29:44 PM UTC+4:30, Mat wrote: > > Just a thing I've been reflecting over: > > *The easier it is to install plugins*, either permanently install them or > - perhaps even more importantly - to do a temporary use+delete install... > > *...the less the need and pressure to include functionality in the core / > std distro.* > > The coming "dynamic loading of plugins > <https://groups.google.com/forum/#!topic/tiddlywiki/Fdi955ap4a4>" is a > very welcome step in this direction. I can't tell if this is an > implementation of the request to Provide a mechanism to register plugins > after boot <https://github.com/Jermolene/TiddlyWiki5/issues/2547>. Another > addition was the implementation of making tag pills work for multi-tiddler > DnD imports. A more general idea would be a handle to DnD filtered lists > <https://github.com/Jermolene/TiddlyWiki5/issues/2843>. A further step > would be to Extend Download button to offer adding plugins > <https://github.com/Jermolene/TiddlyWiki5/issues/3952>. And eventually > we'll hopefully be able to solve the Big One, i.e a library that serves a > federated collection of plugins. > > Apropos this, if installing and removing plugins were totally painless, > would it be possible to excise features from the core / standard distro? > Just curious. > > <:-) > > > -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywikidev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/06c2d171-0304-4193-9587-bf50371908e9%40googlegroups.com.
