10 January 2019
|
Jono Alderson
In our ongoing quest to make yoast.com lightning fast, we’ve reached a bottleneck when it comes to optimising our CSS. The ways in which WordPress themes manage, handle and output stylesheets just aren’t good enough. Technology has changed, the web has evolved, and the tools we have are out of date. We think we can come »
Read: "A better, faster approach to CSS in WordPress themes"
18 September 2018
|
Luc Kickken
In our previous post on how to theme our HowTo content block for Gutenberg, I explained the HTML structure of the block. I walked you through a few approaches to styling the generated block to make it blend in with your theme. With the release of Yoast 8.2 we’ve not only included the HowTo structured »
Read: "Theming Gutenberg: the FAQ block"
11 September 2018
|
Luc Kickken
With the launch of Yoast SEO 8.0, we’ve released our first real integration with Gutenberg. Now, with Yoast SEO 8.2 we took the first step into how to combine the power of Gutenberg with the field of SEO. More specific: the user-friendly implementation and usage of structured data. I won’t go into the technicalities, so »
Read: "Theming Gutenberg: the How-to block"
29 June 2018
Andrea Fercia
Two weeks ago, I’ve attended WordCamp Europe in Belgrade, together with many colleagues from the Yoast team. As usual, it’s been a great event and also an excellent opportunity to think about what an inclusive event is. In this post, I’d not like to talk technical accessibility, but share some personal thoughts about what I think »
Read: "How inclusiveness improves a global community at WordCamp"
4 May 2018
|
Andrea Fercia
Modals are a pretty common interface on the Web. Developers and designers might give them different names: lightbox, modal window, dialog, overlay… but they’re basically the same thing. A modal is a window that appears on top of the page overlaying other content. In this post, I’ll try to explain what needs to be done to make »
Read: "The a11y Monthly: Making modals accessible"
30 March 2018
Andrea Fercia
In my previous monthly post, I’ve shared a few tips and tools for accessibility testing for beginners. In this post, I’d like to tell you when I was a complete beginner myself, and how starting to test for accessibility helped me to be a better professional. Not surprisingly, my first impact with assistive technologies wasn’t »
Read: "a11y Monthly: Testing for Accessibility, or my journey"
28 February 2018
Andrea Fercia
In-depth accessibility testing requires knowledge and experience. But even if you’re not a specialist, you can start testing for accessibility today. In a previous post, I’ve talked about five easy things you can do to improve accessibility. In this post, I’d like to share with you a few tools you can use to test the accessibility »
Read: "The a11y Monthly: Accessibility testing for beginners"
27 February 2018
|
Anton Timmermans
At Yoast, we optimize every aspect of websites’ performance. Our goal is to make the web a better place by making websites more usable, easier to navigate, faster, and more reliable. In September 2017 we migrated our webshop from Easy Digital Downloads (EDD) to WooCommerce — it’s where we sell all the tools, products, and »
Read: "Migrating Yoast.com’s webshop from EDD to WooCommerce"
31 January 2018
Andrea Fercia
In modern web development, building web applications using JavaScript frameworks is a growing trend. And with good reasons, as JavaScript frameworks offer several advantages. However, the shift to a different interaction model creates new accessibility challenges that haven’t been fully addressed yet. In this post, I’d like to talk about a fundamental aspect of accessibility: »
Read: "The a11y Monthly: How to fix navigation in JavaScript"
20 December 2017
|
Anton Timmermans
The WordPress JavaScript documentation standards have an interesting section about line length. You should wrap your DocBlock text to the next line after 80 characters of text. The reason for this is to make code readable in any editor. Even if the editor doesn’t have a build-in wrapping mechanism. There is a simple way to »
Read: "How to correctly wrap WordPress JavaScript documentation"