Drupal

For a few years now, quite a lot of effort has gone into making Drupal work in a Headless or Restful state. This has led to the creation of modules such as the subrequests module that allows any set of requests to be aggregated together.

In a previous article I touched on the oEmbed standard and a little about the use of remote media including remote images.

Of course embedding images into to page whether hosted remotely or locally is not a new thing. Embedding remote images from the Drupal UI is not supported out of the box. Of course you can manually edit the html using your wysiwyg editor, but that is not very user friendly and is not a great user experience. Furthermore doing so increases that the risk your markup may be malformed etc

Drupal 8.6.0 has an out-of-box adds support for embedding remote YouTube and Vimeo videos by means of the oEmbed format. You may notice these are often encapsulated in an iframe. You can see this evident in a new media type being defined called 'Remote Video' available form /admin/structure/media. A new icon is also available form your wysiwyg that allows you to embed the new format in your page or block.

One of the changes introduced with the launch of Drupal 8.7.7 included support for semantic versioning. The Semantic Versioning specification was originally authored by Tom Preston-Werner, inventor of Gravatar and cofounder of GitHub. We are currently on Semantic Versioning 2.0.0.

The recent acquisition of Acquia by Vista Equity Partners for $1billion probably overshadowed the smaller acquisition of Cohesion by Acquia a few weeks earlier. The move helps Acquia enhance its portfolio by also acquiring the DX8 page editor and site builder tools:

Yesterday, May 1st 2019, Drupal announced the latest stable iteration to their open source CMS Drupal 8.7.0. There were a number of announcements including 

With the latest release from Drupal also including the latest security fixes, it was time to update again. One issue that experienced Drupal Developers are probably quite used to by now are the continual stream of security advisories that need to be addressed, especially if you are managing a site that also includes peoples data. This means regularly maintaining your site to ensure it is kept up to date and secure.

I have been using Drupal since 2009 and one of things that is impressive is how modular it is. The core Drupal build is very extensible and there are literally 100's of thousand's of contributed modules out there, many of them regularly updated and maintained by the very active open source Drupal community.

So it has taken me a while to come up with an idea for a Drupal module that no one else seems to have addressed, the idea of a 'CSS reset'.