Like last year, Automattic went to Whistler, British Columbia for our annual Grand Meetup. We had almost 600 employees spanning the globe, suddenly just spanning 2 hotels for the week. It’s great to build things in person with people you usually only communicate with via text. Sure, it’s a little bit overwhelming, but I always walk away with a few new friends.
We built and learned quite a bit this week, and though there are no specific announcements yet, please watch the Jetpack Blog, WordPress.com Blog, and WooCommerce Blog for exciting news. As for myself, and as usual, I have a fair amount of photos to share:
Matt Mullenweg 2
Automattician Band 2
Automattician Band 3
Automattician Band 4
Automattician Band 5
Automattician Band 6
Automattician Band 7
Automattician Band 8
Automattician Band 9
Automattician Band 10
Automattician Band 11
Automattician Band 12
Automattician Band 13
Automattician Band 14
Automattician Band 15
Automattician Band 16
Automattician Band 17
Automattician Band 18
Automattician Band 19
In case you’re wondering, those last few photos are of our very talented band of Automatticians.
Net Neutrality is a big issue that everyone should be concerned about. When you request a website, or any information over the internet, you expect your ISP to deliver it as requested with no interference. This is what the FCC’s Net Neutrality rules protect. Without Net Neutrality rules, your ISP could block sites they don’t like or slow down access to sites that don’t pay a fee, and those rules are in jeopardy.
The FCC is considering repealing the Net Neutrality rules, but there’s still time to stand up for what’s right. The FCC is currently requesting your feedback, and the first comment deadline is July 17, so make sure that you send your feedback to let them know what Net Neutrality means to you. Next, join the Net Neutrality Day of Action protest tomorrow (July 12). There are many ways you can participate listed there, and if you have a WordPress site, use the Fight for the Future Alerts plugin.
Millions of people spoke out in 2014 to establish the Net Neutrality rules, and hopefully we can do the same this year to save them.
Last week, WordCamp Europe 2017 was filled with lots of opportunities to make WordPress better, including the announcement that the future WordPress Editor (codenamed Gutenberg) is now available for use as a plugin. The future of WordPress editing will be built on positionable blocks, where each block can be pretty much any kind of content, like this gallery:
There have already been plenty of great posts that go in depth on the current state of Gutenberg, so I won’t bore you with the details here, but the short version is that folks who are new to WordPress may find this to be an intuitive experience while long-time WordPress users may encounter a bit of a learning curve. Fortunately, Gutenberg won’t replace the existing WordPress editor until WordPress 5.0, so there’s plenty of time to install that plugin and start contributing.
P.S. This post was originally written with Gutenberg 0.2.0 on WordPress 4.8, but required a few tweaks after publishing, so please help us test this and contribute to make it better. 🙂
WordPress 4.8 has been released! This release introduces new widgets for images, videos, audio, and rich text, as well as new link boundaries to cure editor frustrations and a new Dashboard widget which displays nearby WordPress events!
346 volunteers contributed to this release, lead by Matt Mullenweg and Jeffrey Paul. At the time of writing this, WordPress 4.8 has been out for about 9 hours, and has already been downloaded 1,315,250 times!
All users can safely update from Dashboard -> Updates or download and update manually, though you should probably backup first just in case, unless you’re already using VaultPress, which you really should be.
For as far back as I can remember, browsers have always denoted HTTPS pages with a padlock icon, a tiny warning to let you know that anything you submit on the specific page will be securely encrypted. As with all never-changing warnings though, I imagine you’ve stopped noticing it as much as you used to years ago, and that effect combined with HTTPS usage reaching over half of all web pages and the popularity of extensions like HTTPS Everywhere, has spurred some changes in how Firefox and Chrome approach this.
Launched this week, Firefox 51 and Chrome 56 have reversed that age-old warning. Login forms over HTTP now display a “Not Secure” warning. This new warning should be enough to catch the attention of those of us who have begun to ignore the time-honored padlock, but I imagine site owners might be caught a bit off guard.
If you own a site with a login form over HTTP, don’t worry (sort of), your login form isn’t suddenly not secure … it has never been secure. If you’re the only person who uses that login form, and you never use it over a public internet connection, you generally have nothing to worry about.
If other people are expected to log in to your site over HTTP, or you often log in over a public internet connection, it’s time to start moving your site over to HTTPS. You’ll need to acquire an SSL/TLS certificate from a certificate authority to being with, and in the past those have been ridiculously expensive, but all of that changed when Let’s Encrypt premiered, offering free SSL/TLS certificates for everyone. Today, you’ll most likely find that your hosting provider either offers free or incredibly inexpensive certificates, like all of WordPress’s recommended hosting providers do. If your hosting provider still wants to charge you a ridiculous rate for a certificate, you might as well take this opportunity to check out the rapidly growing list of hosting providers who offer free Let’s Encrypt certificates.
Once you have your certificate, setting it up is generally just a matter of consulting the documentation from your hosting provider (though this is typically automated if you acquire the certificate from them) and your website’s software. If you use WordPress, the process is very simple.
As site owners, let’s do what we can to proliferate HTTPS and thus provide a more safe and secure web for everyone.