bikubi

Quasar supports SCSS but the style variables won't be available.
Here's a possible workaround -- incomplete & untested, since I gave up, went ahead and used stylus. (This is guide is primarily directed at future me, should this become more compelling in the future.)

Install stylus-converter

yarn add --dev stylus-converter

bikubi

# Very simplistic, use at your own risk. I am using this on Raspbian.
#
# put me into /etc/systemd/system
# systemctl start iptables-nat
# systemctl stop iptables-nat
# systemctl enable iptables-nat
#
# see: https://wiki.archlinux.org/index.php/Internet_sharing
# adapted from: https://github.com/gronke/systemd-iptables/blob/master/etc/systemd/system/iptables.service

bikubi

#!/bin/bash

# create a slideshow from images, with nice blending
# using MLT or ffmpeg
# adapted from https://superuser.com/a/834035
#
# beware of the ffmpeg command, it eats memory quickly

# USAGE
# 1 pass images as arguments

bikubi

#!/bin/bash

# Scans blade templates for WordPress's gettext functions
# so WPML will pick them up for its String Translation.
# (WPML doesn't see something like {{ __('Hello World', 'sage') }}

# Put me into THEME/resources/assets/build 
# so $fn will point to THEME/resouces and WPML can see it
# (and it's out of sage's way)

bikubi

#!/usr/bin/env python

import subprocess as sp
import RPi.GPIO as g
import time
import os

# see http://cyfta.com/?p=8480
# & listen to WFMU! http://wfmu.org

bikubi

Why

1. Sage doesn't come with Purgecss (or uncss, etc.)
2. Say, we use Bulma -- suddenly dist/main.css grows by 400K!
3. Let's purge it!
4. Oh dang, we need to whitelist /\.wp-/, /\.post-type/, /myfancylightbox/...
5. Wait we are whitelisting pretty much everything from /resource/assets/styles!
6. Isn't there an option to purge /node_modules/**/* only?
7. Nope.
8. purgecss start ignore, strategically placed, to the rescue!