As more and more third-party services (Mailchimp, Stripe, etc.) become required for our websites and for our client websites, the WordPress HTTP API has become an important tool in any developer kit. Knowing how to use the HTTP API methods to send and receive data to and from these third-party services will help you stand out from the crowd. Jonathan will teach you how to use the HTTP API to build a straightforward WordPress subscription plugin that will hook into the Mailchimp API.
Required skill set
A basic understanding of web development (HTML/CSS and PHP) would be useful. Working knowledge of HTML forms would also be useful. The workshop is aimed at beginners or those who’ve never used the WordPress HTTP API before.
Technical requirements
Bring a laptop with a working local WordPress.org install and a code editor. Attendeesalso need to install Postman for testing API endpoints https://www.getpostman.com/. And it would be ideal if they have already signed up for a free Mailchimp account.
After deploying code, most of us go look at the homepage and other templates to make sure things are okay. It’s a cumbersome task that, let’s be honest, we probably can do more thoroughly. Andrew looks at using visual regression testing to automate this process, letting tools do the work!
Required skill set
To get the most out of this workshop, attendees should be comfortable editing Node.js (JavaScript) files and running commands in the terminal (command line).
Technical requirements
To follow examples in this workshop, attendees need to have a computer with Node.js (https://nodejs.org) installed, a code editor, a Git client (command-line or UI), Google Chrome, and a WordPress site with two environments (e.g., production and staging or production and local).
Gutenberg is making waves in the WordPress community and changing how we compose content forever. What essential new stuff does Gutenberg bring to content authoring? Elio will focus on the block, the brick used to build content, and show you how to build a Gutenberg block from scratch to offer everyone an easy and predictable way to compose content.
Required skill set
Attendees should be familiar with WordPress plugin development, but need not be experts, and familiar with terms such as hooks, filters and enqueuing scripts. No previous experience with creating Gutenberg blocks is necessary.
Technical requirements
Bring a laptop with a setup appropriate for development of WordPress plugins. It’s better if this setup is local. Please note that *we will need network connection* whenever we run npm to download JS packages necessary for compiling the Gutenberg blocks created.
Setup for plugin development includes:
- a local server such as Apache
- a database manager such as MySQL
- a local WP 5.1 installation with its corresponding database
Setup for Gutenberg block creation includes:
- Latest Node.js 10.x. Gutenberg recommends the active LTS version that is currently one–see https://nodejs.org/en/about/releases.
- Latest version of npm
Everyone should be able to turn their virtual private server into a blazing fast WordPress LNMP stack by the end of this talk. George will cover how to set up a complete stack via automated scripts like EasyEngine and analyse all parameters of it, with hands-on experience of using NGINX, PHP7, MySQL/MariaDB, and Redis Cache for a super-fast website.
Required skill set
Attendees should understand basic Linux commands, have basic Linux hosting experience, and must be familiar with the use of terminal.
Technical requirement
Bring a laptop. No WordPress-related setup is needed. This workshop will be all about setting up a web server.
This year I took the challenge of #100DaysOfCode. But why? Am I new to code? Do I need to learn code as a designer in the first place? And what does it behold? Is it a fixed format?
In this talk, I’ll explain what #100DaysOfCode is an why I took the challenge. I also challenge you to join when you work with WordPress, even though you don’t fancy a career as a frontend or backend developer.
Blocks aren’t just for editing posts and pages. Tom will build a block, then show you how to put it in other places, such as a settings page or even on the front-end. Why should posts get all the attention?
You usually notice design and content when you visit a website, but what do attackers see? They spot misconfigurations, forgotten endpoints, out-of-date components, emails and other sensitive information. Vladimír will give a 10-minute preview of common but not often-mentioned mistakes he saw during security scans of WordPress sites, specifically: Username and email leaking, full path disclosures, accessible backups, open .git repositories and DoS capable endpoints. He will also provide tips on how to reduce risks, where it is worth restricting access, how to enable Bcrypt password hashing and 2FA, and what configuration directives you need to check.
You made a mistake months ago, and a part of the site is broken. No one noticed at first, but now the client is upset, so you need to fix it…and fast! But where in the code was this bug introduced? What if David told you there’s a tool hidden within Git to quickly find when a bug was committed and then fix it? Git Bisect allows you to comb through dozens of commits at once and find the culprit in seconds, even when you don’t know when it happened or what file was edited. Once you understand the basics, David will take it a step further with automation.