Blog

I recently went through the process of setting up an RSS Feed for our blog here at DevCollaborative so that our articles can be syndicated to Planet Drupal. It had a surprising amount of gotchas and the documentation was dated and sparse. So I thought I’d help remedy that by sharing what I learned.

Clayton introduced me to the Consentful Tech Project, which provides a framework for applying Planned Parenthood's FRIES definition of consent to applications. Clayton and I played around with extending that framework into the world of web UX, and the result of those thought experiments is our talk, Consentful UX. A video of the talk and its slides are here. 

This is good news for nonprofit organizations on Drupal 7 who don’t have funds, capacity, and/or time for a rebuild right now. We'll attempt to tackle some questions about Drupal versions, upgrades, rebuilds, timing, and planning website projects here.

I stopped complaining about overly-complex Drupal 8 starter themes and, together with the DevCollab team, made our own ready-to-customize sub-theme of Classy. Our Drupal 8 starter theme is called LightShip, and we shared it on Drupal.org.

• It's a fully customizable sub-theme of Drupal 8 core's Classy theme, leveraging the good accessibility work that's gone into core;
• It has a light Sass implementation;
• It has a README file to help you get started.

This week, Dries announced at DrupalEurope, and on his blog, that November 2021 will be the End of Life (EOL) date for both Drupal 7 and Drupal 8. Drupal 9 is now scheduled to be released in 2020, giving people a year to upgrade from version 8 to version 9 before Drupal 8's EOL. Why is Being on a Supported Version Important? Because being on a version of Drupal that's "no longer supported" means that it will not be updated when new security vulnerabilities are discovered.

How does this affect resource-constrained nonprofits using Drupal?