Info for Decision makers / evaluators

Submitted by admin on
Body

This documentation needs work. See "Help improve this page" in the sidebar.

 

Goal: help reader decide if they should implement a decoupled Drupal site>

Who is this page for?

Anyone who is thinking of implementing decoupled Drupal and wants to see its benefits and current limitations.

<Assumptions: 

  • User has read the “What is Decoupled?” introduction; 

  • Site status

    • Does not have a site

    • Has a coupled Drupal site

    • Has a coupled CMS and is thinking about coming over to Drupal

    • Has a decoupled CMS and is thinking about coming over to Drupal

    • (Not sure if we should include this scenario: Has a decoupled Drupal site and wants to see the current state)>

<Thinking of having a section called, “Questions to ask yourself”; but, need to figure out how to break it down, and create a decision tree. 

Goal: Help reader understand scope of effort with benefits and challenges.

Similar to what Dries wrote in 2019; may need to be updated, not sure if we can just reference it, and it is a bit messy. https://dri.es/how-to-decouple-drupal-in-2019; 

Only local images are allowed.https://dri.es/files/images/drupal/how-to-decouple-drupal-in-2019-flowchart-full.png>

Questions to ask yourself

  1. <Audience>

    1. Where are the users you are trying to reach? <Or, Who needs to consume your content?>

      1. Customers on the web

      2. Digital signs in the office

      3. External partners ingesting my content

  2. <Content>

    1. <Structured Content>

    2. Do your content managers need to customize page layouts?

    3. Do your content managers need to preview unpublished content?

    4. <Views; ref to REST API note in “What is Decoupled?”>

  3. <Team>

    1. Do your design changes outpace your development team? <Do not necessarily need decoupled; but, this is an advantage over out of the box>

    2. <Do you have a frontend team that wants to use a JS framework (react, vue, nextjs, etc)>

    3. How big is your development team? Decoupling can help with project governance in large teams whereas it can add to the maintenance burden in small teams.

    4. Do you hire your whole web team from an assortment of vendors? Or are you responsible for web content amongst many disparate groups in your organization? Having a decoupled approach can ease splitting work up amongst stakeholder groups who have different budgets and schedules of work.

  4. <Technology>

    1. <Backend API>

    2. <Frontend JS Framework>

    3. <Security>

  5. <Organization / company / policies / regulations>

    1.  

<ToDo: 

  • Add non-Drupal decoupled considerations

  • Add in method to show decision score between standard and decoupled>

Case studies

<Goal: Help reader see what is possible>

<Placing it after “Questions to ask yourself” to establish a baseline in the user’s mind so they can understand what they are seeing and reading in the case studies; however, can see the argument of place this as the first thing to hook the reader in>

Knowledge Category
Decoupled Drupal