Erin Sparling everyplace

OOCSS vs OOSass

OOCSS is awesome because it helps us organize our style sheets in clean and simple ways but it can be far too rigid for the new responsive web. How can we use preprocessors to preserve both flexibility and cleanliness of code? Can these objects be abstracted to our preprocessors?

Lets first take a look at three column widths in OOCSS to see how they compare.

CSS

.width-1 {

Keybase proof

I hereby claim:

I am everyplace on github.
I am everyplace (https://keybase.io/everyplace) on keybase.
I have a public key ASBku7Xg52Syqa-w2lLWyaLp4eNiG1QuPu7rLINsziCunQo

To claim this, I am signing this object:

	COOKIE_SECRET="It's a secret to everybody"
	FLICKR='{"api_key":"XXXXXX", "api_secret":"XXXXXX", "callback_url":"https://XXXXXX/auth/flickr/callback"}'
	TWITTER='{"consumer_key":"XXXXXX", "consumer_secret":"XXXXXX","request_token_url":"https://api.twitter.com/oauth/request_token","authorize_url":"https://api.twitter.com/oauth/authorize","access_token_url":"https://api.twitter.com/oauth/access_token","callback_url":"http://XXXXXX/auth/twitter/callback"}'
	GOOGLE='{"web":{"auth_uri":"https://accounts.google.com/o/oauth2/auth","client_secret":"XXXXXX","token_uri":"https://accounts.google.com/o/oauth2/token","client_email":"XXXXXX","redirect_uris":["https://XXXXXX/auth/google/callback"],"client_x509_cert_url":"https://www.googleapis.com/robot/v1/metadata/x509/XXXXXX","client_id":"XXXXXX","auth_provider_x509_cert_url":"https://www.googleapis.com/oauth2/v1/certs","javascript_origins":["XXXXXX"]}}'
	GOOGLE_SCOPE='["https://www.googleapis.com/auth/userinfo.profile","https://www.googleapis.com/auth/userinfo.email"]'
	GOOGLE

	#!/bin/sh

	# ci_post_clone.sh
	#
	# Created by Erin Sparling on 3/01/24.
	#
	# Put this file in ci_scripts/ in the root of your project.

	# https://social.jvns.ca/@b0rk_reruns/112033146491358262
	set -euo pipefail

	UA=UA-3289748-1
	DOMAIN=erinsparling.com