#dartsass — Public Fediverse posts

Annoying that #DartSass is removing the @import function just as #CKEditor has stopped using an iframe.

Now ckeditor stylesheets on a #Drupal edit form are no longer isolated to the wysiwyg field, and there is no clean and simple way to wrap the entire front-end theme in a ckeditor class selector using an import.

Update for Sassy dark mode https://no-pe.netlify.app/dark-mode/

Now with #DartSass.

Short version: I want light/dark themes that are backwards compatible. With Dart Sass, we create two maps, one for light and one for dark colors. Then, we use them in a `mixin` for all our color information. Finally, we include it twice: once as the default and once behind the media query.

#hugo #sass #css #DarkTheme #LightTheme

Made my first little contribution to @gohugoio documentation yesterday! It's about installing #dartsass in the CI workflow on #Sourcehut Builds, which I'm using to deploy my Hugo site to my static host of choice: Bunny.net.

(libsass is deprecated in Hugo)

I learnt a bit more Git during the pull request too—about rebasing, but I'm still not very good at it (merging the changes is a bit confusing to me).

The actual docs page: https://gohugo.io/host-and-deploy/host-on-sourcehut-pages/

#gohugoio #gohugo #Hugo #CICD #srht

Oh wonderful that #DartSass is going to suddenly start throwing a bunch of warnings because they are changing the way that #SCSS nesting works to match #CSS.

https://sass-lang.com/documentation/breaking-changes/mixed-decls/

The thing is, I can't actually find any examples where changing the output from nesting would result in changes to the actual styles of the page. The font-weight example would result in everything still being the same font weight.