Wow, @TiddlyTweeter … you’re really putting it through its paces
Great that performance-wise it works well
Yes, I really wanted that functionality since I have many tiddlers with documentation open (in my work-wiki) and I’m often in the situation where I need a specific documentation fast
I’m now trying to put together something like a documentation
Have a look at the demo page (here) and open the Ensemble “Documentation” … there you’ll find important css classes and you can show the elements on the page
My guess is long-term there could be a whole secondary level of developments to leverage MCL (Not necessarily by you! Don’t panic ! )
But I did want to comment on a couple of things I’m working on …
Adding a button to dynamically toggle the value of $:/config/story-river/horizontal/columns from 1 to 4.
Why? I found in practice, especially on making new wiki, activating “horizontal” in different ways increases utility.
Adding ability to HIDE a column.
In my use case I’m getting into the habit of using one column for the macro and css editing I need to do. But an end user never needs to see these so I’m working on hiding that column on startup.
Those are a couple of examples which I think pretty easy to achieve because the design of MCL lends itself to it !
When a tiddler is in fullscreen mode, if we try to open another tiddler from the sidebar search or using the command palette, the newly opened tiddler can be seen only if I come out of the fullscreen mode.
as I’ve seen on Screenshots you’ve posted before, you’re already documenting some classes and so on. These tiddlers would be very helpful and I’d integrate them in the Documentation-Ensemble