w3guy

/**
 * Insert an attachment from an URL address.
 *
 * @param  String $url 
 * @param  Int    $post_id 
 * @param  Array  $meta_data 
 * @return Int    Attachment ID
 */
function crb_insert_attachment_from_url($url, $post_id = null) {

w3guy

var DATE_RFC2822 = "ddd, DD MMM YYYY HH:mm:ss ZZ";
moment().format(DATE_RFC2822);

w3guy

0. Table of contents
1. General information
   1. Terms
   2. General structure of a test
   3. WordPress-specific assertions and test functions
      • enqueues
      • creating posts
      • creating terms
      • attaching images

• ?

w3guy

WordPress Emails

This document lists all the situations where WordPress sends an email, along with how to filter or disable each email.

This is accurate as of WordPress 4.8, and includes some upcoming changes in WordPress 4.9.

There are a few TODOs left. Please bear with me.

• Comments
• Change of Admin Email

w3guy

(function() {
  var css = "*{font-family:\"Blokk Regular\", blokk !important;}",
    head = document.getElementsByTagName("head")[0],
    style = document.createElement("style");
  style.type = "text/css";
  if ( style.styleSheet ) {
    style.styleSheet.cssText = css;
  } else {
    style.appendChild( document.createTextNode( css ) );
  }

w3guy

function Emitter() {
    this.events = {};
}

Emitter.prototype.on = function (type, listener) {
    this.events[type] = this.events[type] || [];
    this.events[type].push(listener);

}

w3guy

function Emitter() {
    this.events = {};
}

Emitter.prototype.on = function (type, listener) {
    this.events[type] = this.events[type] || [];
    this.events[type].push(listener);

}

w3guy

.in-sub-panel #customize-theme-controls .customize-pane-child.current-panel-parent,
#customize-theme-controls .customize-pane-child.current-section-parent {
  -webkit-transform: translateX(-100%);
  -ms-transform: translateX(-100%);
  transform: translateX(-100%);
}

w3guy

This is the follow up to a post I wrote recently called From Require.js to Webpack - Party 1 (the why) which was published in my personal blog.

In that post I talked about 3 main reasons for moving from require.js to webpack:

1. Common JS support
2. NPM support
3. a healthy loader/plugin ecosystem.

Here I'll instead talk about some of the technical challenges that we faced during the migration. Despite the clear benefits in developer experience (DX) the setup was fairly difficult and I'd like to cover some of the challanges we faced to make the transition a bit easier.

w3guy

## CLI
https://github.com/zfcampus/zf-console

[https://github.com/mnapoli/silly](Silly CLI micro-framework based on Symfony Console)


## GitHub authors
https://github.com/mnapoli?tab=repositories