Dev Blog


Composer in Yoast projects

11 November 2015 by Andrey “Rarst” Savchenko »

web content accessibility at yoast

Earlier this year I implemented the Composer dependency manager support in Yoast projects. In recent years I spent a lot of time to explore and promote the use of Composer in the WordPress ecosystem in general. Implementing Composer in Yoast plugins is a great example of its success with WordPress projects, deployed on a widest possible »

Category:

YoastSEO.js design decisions

4 November 2015 by Omar Reiss »

Yoast SEO plugin

In the upcoming 3.0 release of Yoast SEO (for WordPress), we’re moving the entire content analysis from the server to the client side. This way our users can get instant feedback on the content they’re writing, while they’re writing it. In the past six months we’ve been working hard on a JavaScript library called YoastSEO.js »

Category:
Tag:

Yoast SEO: Developer Beta

8 October 2015 by Omar Reiss »

Yoast SEO plugin

Today we’re releasing a developer beta for the upcoming release of Yoast SEO for WordPress, containing the long anticipated real time content analysis functionality. The release is provisionally scheduled for november 2nd and will include native support for shortcodes. At the same time we had to break backwards compatibility for multiple filters. That means we really »

Category:
Tag:

Adding a Pinned Tab icon for Safari

2 October 2015 by Joost de Valk »

Safari pinned tabs - mask-icon

With the release of Mac OS X 10.11, Safari finally got pinned tabs. While all other browsers use a site’s favicon for the pinned tab, Apple deemed that “not esthetically pleasing enough” and created a new type of icon for it, which they call a “mask-icon”. By default, they’ll use the first letter of your domain »

Category:

Yoast SEO for Drupal 1.0-beta

23 September 2015 by Joost de Valk »

Drupal SEO image

Today we’re launching Yoast SEO for Drupal 1.0-beta. Or, in the common Drupal versioning scheme, Yoast SEO for Drupal 7.x-1.0-beta. Meaning, it works for Drupal 7. First of more platforms As announced earlier, this is the first time we’ve moved Yoast SEO to another platform, but it won’t be the last. We chose Drupal as a »

Category:
Tag:

Yoast SEO: announcing breaking API Changes

26 August 2015 by Joost de Valk » - 13 Comments

Yoast SEO plugin

As we announced a while back, we’re working on real time content analysis functionality for Yoast SEO. While we wanted to preserve backwards compatibility, we’ve come to the conclusion that we won’t be able to for some filters. This means that some themes and plugins, who integrate with our page analysis functionality, will need to be updated. We »

Tag:

Breaking up responsive design

19 December 2013 by Michiel Heijmans » - 60 Comments

AMP for eCommerce

Over the last couple of weeks I have been dealing with the fine art of CSS. Although that is not my daily business anymore – because I lead the website review team here at Yoast – I really enjoyed mastering SCSS and using that for an actual design. During this field trip, I encountered several »


Standardising WordPress theme hooks

20 June 2013 by Joost de Valk » - 16 Comments

I’ve been working on integrating our SEO plugins more deeply with Genesis the last few weeks and something dawned on me. Ever since I wrote my post on Genesis 2.0, I’ve been thinking: Genesis started a small revolution, but we should open that up. More theme developers should start doing a Schema.org API and if »

Tags: , ,

Schema.org & Genesis 2.0

28 May 2013 by Joost de Valk » - 37 Comments

About a week ago, we “migrated” Yoast.com to Genesis 2.0, in the process we switched to their new HTML5 / Schema.org code and we slightly updated our design, making the header shorter and making improvements to our responsive design. This was a bit of work, but not even half as much as that sounds like »

Tags: , , ,

Why relative URLs should be forbidden for web developers

17 August 2012 by Joost de Valk » - 60 Comments

Many web developers still use relative urls in their CMS. A relative url is a url that is not complete. Usually it’s just the last part (the path) of a url, which means the domain name is left out. It’s often used by web developers, because it comes in handy when moving content from a test or »