Code

Accessibility on the web has always been an afterthought, with a great number of websites having no compliance with any standards and adhering to no laws. But in this day and age that shouldn’t have to be the case, when the tools to improve this are readily available.

A few days ago I was asked what the best way to manage 30-something or so Grav sites would be, using either a “symlink approach” or a “subtree/submodule approach”. Here’s a quick run-through on what this sort of setup entails.

When the term “Web 2.0” became popular after 2004, the focus was largely on design, usability, and new media. In the past few years, however, web development has focused a lot on more on speed and performance, as well as delivery of media across varied devices.

For version 2 of my DirectoryListing-plugin I wanted to move away from the folder-traversal I had previously utilized. This post details how to programmatically iterate through Grav’s pages recursively, and gather information about page-media along the way. By the end, we’ll have produced a structure like this: