This Drupal / TWIG issue is why I check my vendor directory into GIT.

I spent time spinning my wheels on this and lost face with a client when I pushed after sufficient testing and this breaking change in TWIG slipped in while pushinbg live.  I'd rather have a larger repo then push live and have a different codebase in live than I tested.

This looks promising ... instead of a developer chunking out YML playing working on the command line for one off CSV -> Drupal migrations, a UI which can move it into the hands of an admin.

Looking at the Drupal Quicklinks Module and am thinking about visitors' who have datacaps.  Is it ethical to preload pages that visitors might not visit?

OK, I’m trying the best way to handle this:

On a Drupal 7 site I had a poor man’s URL shorter.  I create a slug by encoding a node’s NID using an algorithm that wouldn’t contain a vowel.  In hook_boot I’d test to see if there was a vowel and in the URL’s path.  If there wasn’t I’d decode the slug and redirect to /node/nid otherwise Drupal would continue doing its thing.   Since all the content is in English any aliases would contain vowels so I was OK.  It worked well and would redirect before Drupal fully bootstrapped, saving some cycles.

I’m thinking about moving this to Drupal 8.  I’ve been debating between building a module with an event subscriber and just putting the code at the top of settings.php.    Any thoughts or advice please answer on stack exchange.

A quick PHP one liner to calculate US Thanksgiving day. Leaving this for future reference.

    $thanksgiving = date('m d, Y', strtotime('fourth thursday of november '.date('Y')));