Blog

This post summarizes current anti-spam methods available for Drupal 8.

Some Drupal sites don’t allow regular users to log in at all; they may only be used by administrators. In such cases it may be desirable to lock down access to the login and admin screens. This can be done using htaccess.

During the past few weeks lots of us have been bombarded with privacy policy notification emails from various companies. This is because of GDPR, a new data privacy regulation being implemented by the European Union. It builds on and expands on the prior regulation from 1995.

WordPress is a great blogging platform that can also handle many CMS functions. It can be extended with plugins, much the same way as modules are used to extend Drupal.

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: