Commanding Chaos for Coworking, Open Source and Creative Communities

drupaleasypodcast

Selecting a client-side framework for Drupal | Dries Buytaert

Wed, 01/06/2016 - 17:20 -- rprice

I tasked a small team made up of various experts from the Drupal and various JavaScript communities with putting together a list of criteria and a comparison matrix to help us decide on the most appropriate client-side framework for progressive decoupling in Drupal.

drupaleasypodcast
javascript

Selecting a client-side framework for Drupal | Dries Buytaert

Wed, 01/06/2016 - 17:20 -- rprice

I tasked a small team made up of various experts from the Drupal and various JavaScript communities with putting together a list of criteria and a comparison matrix to help us decide on the most appropriate client-side framework for progressive decoupling in Drupal.

drupaleasypodcast
javascript

Selecting a client-side framework for Drupal | Dries Buytaert

Wed, 01/06/2016 - 17:20 -- rprice

I tasked a small team made up of various experts from the Drupal and various JavaScript communities with putting together a list of criteria and a comparison matrix to help us decide on the most appropriate client-side framework for progressive decoupling in Drupal.

drupaleasypodcast
javascript

Sending a Drupal Site Into Retirement | Lullabot

Wed, 01/06/2016 - 16:56 -- rprice

maintaining an inactive Drupal site can be a pain. There is a constant stream of security releases that you need to apply. And it's really maddening if you apply a security release to an inactive site only to find out the release contains other changes that break things that used to work, so that you have to spend time trying to get that inactive site working again. Not to mention that it's expensive to pay for hosting that can securely deploy Drupal sites if you aren't even using any Drupal interactivity any more.

drupaleasypodcast
archive
backup
tutorial

Sending a Drupal Site Into Retirement | Lullabot

Wed, 01/06/2016 - 16:56 -- rprice

maintaining an inactive Drupal site can be a pain. There is a constant stream of security releases that you need to apply. And it's really maddening if you apply a security release to an inactive site only to find out the release contains other changes that break things that used to work, so that you have to spend time trying to get that inactive site working again. Not to mention that it's expensive to pay for hosting that can securely deploy Drupal sites if you aren't even using any Drupal interactivity any more.

drupaleasypodcast
archive
backup
tutorial

Sending a Drupal Site Into Retirement | Lullabot

Wed, 01/06/2016 - 16:56 -- rprice

maintaining an inactive Drupal site can be a pain. There is a constant stream of security releases that you need to apply. And it's really maddening if you apply a security release to an inactive site only to find out the release contains other changes that break things that used to work, so that you have to spend time trying to get that inactive site working again. Not to mention that it's expensive to pay for hosting that can securely deploy Drupal sites if you aren't even using any Drupal interactivity any more.

drupaleasypodcast
archive
backup
tutorial

Pages

Subscribe to RSS - drupaleasypodcast