Our blog

Drupal 8 comes with a new guided help API in the form of the Tour module.

Here at PreviousNext we were instrumental in getting this module in prior to feature freeze and are excited by the possibilities it presents to ease the learning curve for new Drupal site-builders.

In this post we discuss how the module came about, how we went about building support for the idea and the way the API works.

In part two we will go on to show some examples of how you can add tour module support to your modules and talk about some of the advanced features of the API.

We are passionate about code quality. We want to make sure our code is well tested and confirms to standards at all times. If there is a bug, we want to know as soon as possible, so we can fix it and keep our code stable, well tested and bug free, even in early development versions.

Typical workflows use a git topic branch for development of each feature, and require code to be merged into a development branch before automated tests are run. The problem with this approach is it tests code after it has been reviewed and merged.

Using Jenkins for automated testing of Github pull requests, we can get one step closer to code quality nirvana.

We've entered the clean-up phase of the Drupal 8 release cycle. Drupal 8 is shaping up to be the best Drupal release to date - with a raft of new features and a less Drupal-centric developer experience.

So the question on everyone's lips is, when will Drupal 8 be released? The answer is the same as it has always been, 'When it is ready'!

We can't wait to start working with Drupal 8 on a daily basis. The new features will make our day-to-day jobs so much easier and our development workflow so much cleaner.

So to this effect, I'm aiming to work on one patch per day from now until the Drupal 8 release.

Will you join me in the Drupal 8 Patch a Day Challenge? Read on for more details.

Come and join us on Drupal Global Training day, and get a great introduction to Drupal, FREE! This only happens 4 times a year, so grab yourself a spot before they go!

aGov is a Drupal distribution built to address the accessibility, security and design guidelines for Australian Government sites. In a previous blog, I talked about some of the benefits aGov has for public sector agencies trying to do more with less in the online environment. In this post, I'm going to show you are practical example of building a micro-site using aGov, to show you how easy, and quick, it is to get up and running.

We're going to be building a site for a government initiative, but you could easily use the same methodology for a smaller public sector agency, a special event, an informational site, or a minister.

Hear how and why PreviousNext's client, the Special Broadcasting Service (SBS), deployed Drupal with a centralised, decoupled Content Repository to power the digital network into the future

Drupal gives us a range of powerful tools for structuring and presenting content, but relying on these can produce bland, list-driven websites. How do you structure a site to get the benefits of Drupal's content-first tools, while still producing a first-class user experience?

3 PreviousNext developers, Jack Taranto, Christian Biggins & Nick Schuch, deliver a detailed technical insight into the huge development effort that went into NovaFM's new website.