bdmason

Using Sage 9 blade templates for WooCommerce

Declare WooCommerce theme support

Open app/setup.php, find the after_setup_theme action and put add_theme_support('woocommerce'); inside the function.

Override the plugin templates

Add the templates you want to override in resources/woocommerce:

theme    
│

runofthemill

root() {
  local root
  if [[ "$PWD" == *"/trellis"* ]]; then
    root=${PWD%/trellis*}
  elif [[ "$PWD" == *"/site"* ]]; then
    root=${PWD%/site*}
  elif [[ -d "$PWD/trellis" || -d "$PWD/site" ]]; then
    root=${PWD}
  fi

winkerVSbecks

static propertyControls: PropertyControls = {
  text: { type: ControlType.String, title: 'Text' },
  fontSize: {
    type: ControlType.FusedNumber,
    toggleKey: 'fontPerBP',
    toggleTitles: ['Font', 'Font per BP'],
    valueKeys: ['font1', 'font2', 'font3', 'font4'],
    valueLabels: theme.breakpoints.map(s => s.replace('px', '')),
    min: 0,
    title: 'Font Size',

mmirus

Sage Snippets

Snippets frequently used with Sage

• Sage Snippets
  • Load custom fonts in TinyMCE
  • Text selection color
  • ACF theme options page w/ ACF Builder
  • Theme color meta tag

• Nicer Gravity Forms Spinner

threepointone

https://twitter.com/snookca/status/1073299331262889984?s=21

‪“‬In what way is JS any more maintainable than CSS? How does writing CSS in JS make it any more maintainable?”

‪Happy to chat about this. There’s an obvious disclaimer that there’s a cost to css-in-js solutions, but that cost is paid specifically for the benefits it brings; as such it’s useful for some usecases, and not meant as a replacement for all workflows. ‬

‪(These conversations always get heated on twitter, so please believe that I’m here to converse, not to convince. In return, I promise to listen to you too and change my opinions; I’ve had mad respect for you for years and would consider your feedback a gift. Also, some of the stuff I’m writing might seem obvious to you; I’m not trying to tell you if all people of some of the details, but it might be useful to someone else who bumps into this who doesn’t have context)‬

So the big deal about css-in-js (cij) is selectors.

DavidKuennen

(function (context, trackingId, options) {
    const history = context.history;
    const doc = document;
    const nav = navigator || {};
    const storage = localStorage;
    const encode = encodeURIComponent;
    const pushState = history.pushState;
    const typeException = 'exception';
    const generateId = () => Math.random().toString(36);
    const getId = () => {

WebReflection

Handy Custom Elements' Patterns

^{Photo by Ricardo Gomez Angel on Unsplash}

This gist is a collection of common patterns I've personally used here and there with Custom Elements.

These patterns are all basic suggestions that could be improved, enriched, readapted, accordingly with your needs.

cocopon

#1E2132,#2A3158,#C6C8D1,#161821,#2A3158,#C6C8D1,#B4BE82,#E27878

dominiklohmann

gkeep

background #161821
foreground #c6c8d1

selection_background #1e2132
selection_foreground #c6c8d1

cursor #d2d4de

# black
color0 #161821