w3guy

<form method="post" novalidate>
    <div id="msform">
        <!-- progressbar -->
        <ul id="progressbar">
            <li class="active">Account Setup</li>
            <li>Social Profiles</li>
            <li>Personal Details</li>
        </ul>
        <!-- fieldsets -->
        <fieldset>

w3guy

<form method="post" novalidate>
    <div id="msform">
        <!-- progressbar -->
        <ul id="progressbar">
            <li class="active">Account Setup</li>
            <li>Social Profiles</li>
            <li>Personal Details</li>
        </ul>
        <!-- fieldsets -->
        <fieldset>

w3guy

<div id="sc-register">
  <h1>Sign Up</h1>
  <div class="sc-container">
    [reg-username title="Username" placeholder="Username"]
    [reg-email title="Email Address" placeholder="Email Address"]
    [reg-password title="Password" placeholder="Password"]
    [reg-first-name title="First Name" placeholder="First Name"]
    [reg-last-name title="Last Name" placeholder="Last Name"]
    [reg-cpf key="gender" type="select" title="Gender"]
    Avatar[reg-avatar]

w3guy

<?php

//class docs: http://www.orderingdisorder.com/aws/ses/

require_once('ses.php');

//get credentials at http://aws.amazon.com My Account / Console > Security Credentials
$ses = new SimpleEmailService('ACCESSkeyID', 'SECRETaccessKEY');

$m = new SimpleEmailServiceMessage();

w3guy

<?php

class WP_Customize_Range_Control extends WP_Customize_Control
{
    public $type = 'custom_range';

    public function enqueue()
    {
        wp_enqueue_script(
            'cs-range-control',

w3guy

Keybase proof

I hereby claim:

• I am collizo4sky on github.
• I am collizo4sky (https://keybase.io/collizo4sky) on keybase.
• I have a public key whose fingerprint is 23AF 5C74 1A6C 107B 89EC A708 B3C6 9979 3133 585B

To claim this, I am signing this object:

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

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

.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

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

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

}