Hi Odin I think I explained really badly, for trying not to sound too blunt.
The file size is less important than clean html, IMHO. If we add many CSS classes, in the future it will do more difficult do changes, in a landing page maybe is irrelevant but it breaks some "consistency". . As I said " I am sometime too purist/perfectionist" but the reason is avoid extra work in the future. El lunes, 26 de abril de 2021 a las 5:59:17 UTC+2, [email protected] escribió: > Really good work. I think that as we are now able to manage the Layout > dynamically, each layout should be aware of the $:/Storylist and render its > own story river, however that should look depending on the active layout. > > For example, an implementation of the Muuri view as a Layout would render > the Storylist out as a grid. > > An implementation of the Mentat "virtual HUD" plugin would have its own > drag-able window that renders the Storylist according the the current > setting (as a regular Storylist view, as a Muuri grid, etc). > > An implementation of the Landing Page layout would allow the storyview to > be collapsed sticky-notes, etc. > > Best, > Joshua Fontany > > On Sunday, April 25, 2021 at 8:20:36 AM UTC-7 [email protected] wrote: > >> Hi Odin >> >> The use of TailWind might be a distraction. It’s a great framework, but >> if we went with this landing page approach I would want to take our usual >> approach to CSS. I don’t think that’s a problem, what matters is that it’s >> great to have a concrete, tangible prototype to play with. >> >> Best wishes >> >> Jeremy. >> >> >> On 24 Apr 2021, at 14:01, Odin <[email protected]> wrote: >> >> Hi Alvaro, >> >> Thanks for replying! >> TailwindCSS includes a script that purges all unused CSS from the CSS >> file, which is really handy. So the extra CSS for this landing page is >> about 11kb. All in all, it adds 0,3MB to the TiddlyWiki website file. Which >> isn't that bad I think. >> >> "... you add a lof of noise in html. You need add too many classes for >> each element, and it is very similar to use inline styles but with >> shortcuts. (I know it, I am sometime too purist/perfectionist)" >> >> This is off-topic, but I think it is just a difference in design >> philosophy. After a while, it is easy to read the classes, and this way you >> don't have to ever see the CSS file. (google object/component-orientated >> CSS vs utility-first CSS). >> >> >>>>>> >> -- >> You received this message because you are subscribed to the Google Groups >> "TiddlyWiki" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/tiddlywiki/5cac5806-c119-4a07-a6e9-8fb73c908e36n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/tiddlywiki/5cac5806-c119-4a07-a6e9-8fb73c908e36n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> >> -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/2f681d2b-1f9a-4fab-b6ab-17aa6cd58c48n%40googlegroups.com.
