Hi Tony > Dropping Awesome fonts,
Just as an aside, icon fonts like Font Awesome are now widely considered to be a bad idea because they are not accessible: https://cloudfour.com/thinks/seriously-dont-use-icon-fonts/ <https://cloudfour.com/thinks/seriously-dont-use-icon-fonts/> It’s a controversial topic, but even the most ardent supporters of icon fonts acknowledge that they should only be used either if one doesn’t care about accessibility or if one is skilful enough to fix the accessibility issues. The TW core aims to be universal which implies doing what we can to support accessibility, and avoiding features that are known to compromise it. > bootstrap and or w3.css <https://www.w3schools.com/w3css/default.asp> css > files into a tiddler and tagging as style sheets is easy, trivial even and > provides a lot of additional styling opportunities. I like this open solution > better than bespoke ones. It is indeed possible right now for apps built with TW to use off-the-shelf CSS frameworks. Using one in the core means selecting one specific one, though. > To me the main barrier is documentation that helps people understand how to > identify, and how to manipulate the elements within tiddlywiki, and the > classes, and related variables already in use so that you may override them > if desired. I suspect that stuff is pretty self explanatory to a somebody like Arlen who understands both TW5 and CSS. I think that’s the real problem: CSS is complex and takes a significant investment before one fully understands the intricacies that make it so hard at the beginning. I’m not sure that TW5 can take much responsibility for addressing that. Perhaps more in the spirit of TW5 is to grow a community where people with CSS skills can find and work together with people with design vision. Best wishes Jeremy. > I recently discovered you can even leverage whole html/css platforms if you > are prepared to include their dependencies in the same folder of your wiki. > > However the new class field should be explored more > https://tiddlywiki.com/#Custom%20styles%20by%20user-class > <https://tiddlywiki.com/#Custom%20styles%20by%20user-class> > > Regards > Tony > > > On Monday, April 29, 2019 at 4:37:36 AM UTC+10, Mat wrote: > Jeremy Ruston wrote: > >> In reply to @TiddlyTweeters footnote; I also think CSS is one of the areas >> that need more love. IMO we see very little variations in TW appearences. >> IMO, CSS is a kind of poor mans coding to affect how things appear so I >> suspect the big JS-boys here don't fully appreciate this need for us non-JS >> mortals. > > I took Josiah to be expressing agreement with my suggestion of replacing > Vanilla and Snow White with an off-the-shelf CSS framework. > > Aha! That would be great! > > What exactly is the need that isn’t being recognised? > > Thanks for asking. I'm referring to that CSS is relatively simple to learn at > a rudimentary level but still pretty powerful - but that TW is not really set > up for manipulating css easily. Here are a few things that would make working > with CSS simpler and many are kind of connected: > The main obstacle for manipulating the styling is by far the current > stylesheets monolithic nature. These should be split up even though I can't > say exactly how. In complement to splitting them, they could afterwards be > grouped into cascade order, perhaps by means of tags or... (next bullet) > Slugification <https://github.com/Jermolene/TiddlyWiki5/issues/3379> of > tiddler titles would enable more direct manipulation of CSS in wikitext, > using e.g tiddler titles as class names and even appended as selectors. > Cascade order deserves <https://github.com/Jermolene/TiddlyWiki5/issues/2823> > an explicit D'nD listing somewhere under Ctrlpanel > Appearance > To create a SS tiddler, it ought to be enough to add a $:/tags/Stylesheet > tag, i.e auto-detect type. > Local styleblocks are easily "lost". If there was a way to automatically > "collect" (transclude?) them, it would be relatively easy to create custom > complex stylesheets or themes gradually. > Hope this clarifies a bit. > > <:-) > > -- > 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 [email protected] > <mailto:[email protected]>. > To post to this group, send email to [email protected] > <mailto:[email protected]>. > Visit this group at https://groups.google.com/group/tiddlywikidev > <https://groups.google.com/group/tiddlywikidev>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/tiddlywikidev/09d309a0-d7fe-42c8-a645-2fcfc665d454%40googlegroups.com > > <https://groups.google.com/d/msgid/tiddlywikidev/09d309a0-d7fe-42c8-a645-2fcfc665d454%40googlegroups.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywikidev. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/B99D4E21-413B-4021-B1CC-819E7084DF77%40gmail.com. For more options, visit https://groups.google.com/d/optout.
