for #3

readying content

cms/content/articles/content-migration-rescue-process.md

@@ -0,0 +1,40 @@
+metaData:
+    itemSlug: the-content-migration-rescue-process
+    itemName: The Content Migration Rescue Process
+    itemType: article
+    language: en-US
+    published: true
+    publishedDate: '2018-09-04T00:00:00.000Z'
+    createdDate: '2018-09-03T18:40:54.816Z'
+    modifiedDate: '2018-09-04T00:00:00.000Z'
+articleTitle: The Content Migration Rescue Process
+articleSubTitle: null
+author: 'Victor Kane'
+articleBody:
+    value: |
+        You can, and perhaps should, bring your own process. But we do offer a process template based on our own study and experience. It is based on Lean/UX, and should be tailored to the needs of each organization, as explained in my 2015 presentation [DrupalCon Latin America 2015: Setting up a Reusable and Durable Drupal Lean Process Factory](https://www.youtube.com/watch?v=bNbkBvtQ8Z0). Let's breiefly summarize here process highlights and take-aways.
+
+        * Waterfall spells disaster for web application software projects
+        * Agile replaced waterfall
+        * Agile wrongly applied to web application projects is the new waterfall
+            * If it doesn't do away with interdisciplinary silos that do not communicate with each other
+            * If it creates mini-waterfall cascades of input and output between them the various disciplines
+            * If huge amounts of time are wasted while each silo awaits its input and performs its work in isolation and without benefit of ongoing feedback
+            * Graphic design and UX, DevOps, and everything else, should participate together in an ongoing collective and truly incremental and iterative job of work
+        * Migration is not a mechanical transfer of (often unformed blobs of) legacy content from one closed architecture to another
+            * It's about a chance at creating a new updated business model and giving it a chance to breath and grow, prove itself, or pivot
+            * It's about structuring up
+            * It's about looking forward to developing multiple clients that can render content in multiple forms and anywhere
+            * It's about decoupling these clients (web apps, native apps, desktop apps) from the content management system
+            * It's about decoupling both these clients and the content management system from a single, scalable structured content server exposing content created once as a scalable REST API
+        * Just as waterfall and pseudo-agile are the enemies of success in the domain of process, the monolith is that enemy in the domain of architecture
+        
+        Many of our case studies will exemplify the Durable Drupal Lean Process Factory, whether in out and out migration rescue of content from the monoliths, or in fresh projects involving modern, open decoupled architecture right from the beginning. 
+articleSummary:
+    value: null
+tags:
+    - tagSlug: content-migration-rescue
+      tagName: Content Migration Rescue
+    - tagSlug: process
+      tagName: Process
+

cms/content/articles/what-is-content-migration-rescue.md

@@ -14,9 +14,29 @@ articleSummary:
     value: null
 articleBody:
     value: |
-        ## Quisque ut sodales ipsum
+        ### What is it?
 
-        Duis pellentesque eget velit ac ultrices. Proin ut sem eget dui interdum pretium eu at magna. Duis aliquet volutpat euismod. Integer lacus tellus, dictum in augue eget, facilisis ultrices dolor. Nam lacinia, nisl eget rhoncus finibus, elit neque commodo nisi, ac pulvinar ipsum sapien in libero. Donec id purus et turpis maximus aliquet eget a lacus. Nulla at fringilla purus. Etiam rutrum placerat tortor sit amet iaculis. Proin nec enim finibus, condimentum risus sed, efficitur ex. Suspendisse laoreet ante massa. Sed a enim sed libero sagittis cursus vel vel lectus. Etiam tincidunt ac dui ac bibendum. Vivamus in nibh nisi. Maecenas interdum tellus justo, nec porttitor augue auctor nec. Mauris iaculis iaculis lorem, non accumsan felis suscipit eget.
+        A step-by-step approach offering freely shared resources needed for migrating your content from an obsolete, monolithic architecture, to a modern and truly scalable fullstack JavaScript set of decoupled applications and services.
+
+        Included here in this DurableDrupal Content Migration Rescue Website repo, and free to use with the same license used by Wikipedia (the Creative Commons Attribution-ShareAlike License) are a Node.js/Express.js/Mongoose/MongoDB API-first structured content server which exposes that content in a simple REST API (see the `scs` folder); a sample Vue.js/Nuxt.js/Vuetify.js based Client Web Application which consumes that REST API (see the `cwa` folder); a command-line and yaml/markdown based CMS which allows you to edit your content and send it to the structured content server (see the `cms` folder); together with a set of videos which explain in detail each step outlined in the [repo Project](https://github.com/DurableDrupal/ddcmr/projects/1), broken down into a sequence of atomic commits implementing the requirements outlined in the [repo issue queue](https://github.com/DurableDrupal/ddcmr/issues). The transcript of each video will be published in the [repo Wiki](https://github.com/DurableDrupal/ddcmr/wiki).
+
+        And this is only the beginning. As soon as the website is up and running, we will publish our first case study, the migration of AwebFactory.com, the project founder's professional website now running on Drupal 6, to the same decoupled, API-first solution we are sharing here. The steps taken there will also be thoroughly explained and published in the form of a set of videos and a book, to be published on the DurableDrupal Content Migration Rescue Website we are building.
+
+        ### Why do we need it?
+
+        Drupal 8 itself may very well be the ideal solution for many use cases. However, in the case of wishing to go API-first in the form of a decoupled approach, [things may get complicated very quickly](https://events.drupal.org/nashville2018/sessions/decoupled-drupal-hard-problems). Even though Drupal content may be served in the form of a REST API, the need for an asynchrounous or otherwise optimized server proxy has proven necessary for actually serving that content in real time. And so on.
+
+        And when one turns to lists of other [Headless CMS](https://headlesscms.org/) hoping to find enticing alternatives, countless articles by dozens of developers witness the difficulties to be found in sifting through all these choices, both open source and commercial.
+
+        We place this project at the service of a growing community of individuals and organizations willing to freely share and contribute to a set of simple, straightforward and transparently organized resources aimed at moving on with our content and web applications in the face of growing complexity and skyrocketing costs, both up-front in commercial form, or else hidden in the often disappointing experience of real adoption.
+
+        At the hour of needing to move on to industry standard structured content managed and published on the basis of a decoupled and modern, scalable architecture, more and more we are faced with mystification, buzzwords and the unwillingness of companies born and raised on open source communities to share their solutions.
+
+        At the hour of adopting API-first structured content servers, more and more we are faced with the sole option of going behind a "serverless" paywall, which, to add insult to injury, powns our stuff.
+
+        At the hour of wanting to spin up client web applications, once again we are chronically placed at the mercy of open source projects made hopelessly chatoic to use due to a mind boggling rate of change as a result, once again, of having individual and community needs chained to the needs of large corporations and their compulsive and often irrational zigzags as they follow, cross-eyed, their own rapidly evolving crises and "opportunities".
+
+        Perhaps by sharing our results in the community, we can turn a bewildering, demoralizing journey into a pleasing, exciting and above all, empowering experience.
 tags:
     - tagSlug: content-migration-rescue
       tagName: Content Migration Rescue