Thanks. This was just what I was looking for. I like the idea of using Tachyons as a starter kit.
Any idea why my localhost:3000 refreshes the whole page when I make changes to .php-files? I’m using Local by Flywheel. It is also painfully slow when whole page starts to reload. CSS changes happen instantly.
Sounds like a Blade caching issue. Search the forum for that one, it’s quite common.
I think it’s common more for people who are making constant changes to their Blade templates — like you would be using Tachyons. Every time there is a change to the templates, it rebuilds the page and as you could imagine this is slow since your filesystem is syncing with VM. Updating the CSS is fast because webpack is just injecting it (I think).
Maybe a time for another topic, but I’m interested how do you style elements outside of templates with Tachyons? I mean tags created by the_content() etc. I used to use @extend with Tachyons Sass. Found out it’s possible with PostCSS too, but not sure it’s the best way. Maybe just style them with regular css utilizing vars?
Yes, this is off topic. I’ll give an answer, but you can DM me if you would like to discuss more — cause I do like talking about this stuff. I’m thinking of creating a more general topic on using utility/functional CSS frameworks with Sage, since it usually comes its own set of issues — and advantages!
The tachyons-cms module is included in Tachyons (see here). It has .nested- classes for this type of thing. The problem with this approach is — though you will be required to duplicate code — it is being duplicated in a way that is, IMO, not super manageable. @extend, like you said, could be the solution to this, however, it is considered by many to be an anti-pattern.