Blog

Web site content must be served in such a way that a visitor with visual or hearing impairments can consume substantially the same content, even if in alternate form. This involves images with alternative text, video and audio with closed captioning, and adjusting the page markup to cater to screen readers and other assistive technology.

When large organizations build or rebuilt their sites, they may face a dilemma if they have divisions requiring their own web presence. It may be tempting to use Drupal’s multisite option for this, but the pros and cons need to be carefully weighed.

Drupal 8.4.0-rc1 is available for testing now. Drupal 8.4 is expected to be released October 4.

Let’s clear up some misconceptions about when to and when NOT to migrate to Drupal 8

On January 5th the US Access Board announced that the OMB (Office of Management and Budget) had cleared the Final Rule for ICT (Information and Communication Technology) Standards and Guidelines, a.k.a. the “Section 508 Refresh”. The new standards and guidelines were published in the U.S. Federal Register on January 18th and will become effective and enforceable starting January 18th, 2018.

Lately, you may have noticed some sites getting labelled as “Not secure” in Google Chrome:

One of the things that makes Drupal a great CMS is the quality and robustness of its modules. Today I wanted to shine a spotlight on the Pathauto module.

Drupal 8.3.0-rc1 (release candidate 1) is now available for testing.

Drupal 8.2 beta is out, and it is a harbinger of some pretty neat improvements in content editing.

Developing any kind of enterprise site typically involves multiple environments, for example Development, Staging, and Production. A very common scenario developers run into is that a site is developed locally (on the developer’s own machine) and then the code changes get pushed to a repository (version control using Git, Subversion, Mercurial, etc). But what about database changes? Those aren’t code … but they can be.