From 2d881bef1805862b754ed3950a6f6f1852a245f8 Mon Sep 17 00:00:00 2001 From: Rodolfo Date: Thu, 27 Jul 2017 09:09:41 -0300 Subject: [PATCH] Update C01-tendencies-in-content-management.md May be its me, but the original paragraph was difficult to read. It moves backwards and forward in time too much, i think. In this proposal, I jjust moved the present time (the failure to adopt and declining of D8) to the top of the paragraph and leave the reasons for that (and for the title) with the history following. It is just a possibility, and again, it could be me (or my non-native english). --- manuscript/en/C01-tendencies-in-content-management.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/manuscript/en/C01-tendencies-in-content-management.md b/manuscript/en/C01-tendencies-in-content-management.md index 67bef4c..a778a17 100644 --- a/manuscript/en/C01-tendencies-in-content-management.md +++ b/manuscript/en/C01-tendencies-in-content-management.md @@ -213,7 +213,7 @@ The series was [completed in October, 2016](http://www.clevegibbon.com/2016/10/c #### "Should we upgrade to Drupal 8?" No. -Drupal 8 was too much, too late. Still monolithic, it launched in November, 2015, almost five years after Drupal 7. Almost two years later, still not widely adopted, already a declining trend, it was desperately trying to sell itself as an "API-First" and "decoupled" back-end solution (admitting that the front end was a total failure) despite it being even less performant, and hence non-scalable, than its predecessor. +At the time of writing this book, two-year-old Drupal 8 is still not widely adopted and already a declining trend. Was too much, too late. Still monolithic, it launched in November, 2015, almost five years after Drupal 7. it was desperately trying to sell itself as an "API-First" and "decoupled" back-end solution (admitting that the front end was a total failure) despite it being even less performant, and hence non-scalable, than its predecessor. It was also a complete re-write, with xxxx of the code changed. While [Laravel](https://laravel.com/), also based on [Symfony](https://symfony.com/), became the life of the PHP party framework (Laravel is not the hare and the duck at the same time) as it all but embraced Vue.js as its front end, and would be the obvious serious choice in the PHP server-side world.