add conclusion (#9202)

gatsbyjs · Oct 18, 2018 · 977953b · 977953b
1 parent f8ebc6e
commit 977953b
Show file tree

Hide file tree

Showing 5 changed files with 134 additions and 5 deletions.
diff --git a/docs/blog/2018-10-04-journey-to-the-content-mesh/index.md b/docs/blog/2018-10-04-journey-to-the-content-mesh/index.md
@@ -59,13 +59,13 @@ The key challenge is that without a content mesh, integrating these systems toge
 
 As this series continues, we’ll explore the rise of this "content mesh" -- that allows enterprises to adopt these new technologies without needing to DIY themselves.
 
-In Part 2, <a href="/blog/2018-10-10-unbundling-of-the-cms">The Unbundling of the CMS</a>, we’ll explore the rise of headless CMSs and best-of-breed website content and functionality systems.
+In Part 2, [The Unbundling of the CMS](/blog/2018-10-10-unbundling-of-the-cms), we’ll explore the rise of headless CMSs and best-of-breed website content and functionality systems.
 
-In Part 3, <a href="/blog/2018-10-11-rise-of-modern-web-development">The Rise of Modern Web Development</a>, we’ll detail the maturing of the JavaScript ecosystem, the emergence of stable UI libraries like React for creating rich web technologies, and how they help website teams at scale build high-quality sites.
+In Part 3, [The Rise of Modern Web Development](/blog/2018-10-11-rise-of-modern-web-development), we’ll detail the maturing of the JavaScript ecosystem, the emergence of stable UI libraries like React for creating rich web technologies, and how they help website teams at scale build high-quality sites.
 
-In Part 4, Why Mobile Performance Has Become Crucial, we’ll discuss the ROI of site speed, explore two modern, complementary trends for improving web performance and how website teams can get the best of both out of the box.
+In Part 4, [Why Mobile Performance is Crucial](/blog/2018-10-16-why-mobile-performance-is-crucial), we’ll discuss the ROI of site speed, explore two modern, complementary trends for improving web performance and how website teams can get the best of both out of the box.
 
-In our conclusion, Creating Compelling Experiences, we’ll discuss a step-by-step approach for choosing a content architecture, modern development environment, a performance strategy -- and most importantly, choosing an "content mesh" that makes all the other choices easy. We’ll also explore how one clear option -- Gatsby -- emerges as the most feature-complete of any content mesh alternatives.
+In our conclusion, [Creating Compelling Experiences](/blog/2018-10-18-creating-compelling-experiences), we’ll discuss a step-by-step approach for choosing a content architecture, modern development environment, a performance strategy -- and most importantly, choosing an "content mesh" that makes all the other choices easy. We’ll also explore how one clear option -- Gatsby -- emerges as the most feature-complete of any content mesh alternatives.
 
 ## The Modern Website Landscape
 

diff --git a/docs/blog/2018-10-16-why-mobile-performance-is-crucial/index.md b/docs/blog/2018-10-16-why-mobile-performance-is-crucial/index.md
@@ -154,7 +154,7 @@ To overcome these obstacles, high-performing website teams should look to a cont
 
 One example is Gatsby, which includes [both delivery optimization and payload optimization out of the box](/features/#legend).
 
-In the next and final post in this series, Creating Compelling Experiences, we’ll explain how to implement a content mesh and get all the benefits of best-of-breed content systems, modern development frameworks, and high-performing websites.
+In the next and final post in this series, [Creating Compelling Experiences](/blog/2018-10-18-creating-compelling-experiences), we’ll explain how to implement a content mesh and get all the benefits of best-of-breed content systems, modern development frameworks, and high-performing websites.
 
 <figure>
   <img alt="" src="./modern-website-performance.png" />

diff --git a/docs/blog/2018-10-18-creating-compelling-content-experiences/content-mesh.png b/docs/blog/2018-10-18-creating-compelling-content-experiences/content-mesh.png
diff --git a/docs/blog/2018-10-18-creating-compelling-content-experiences/index.md b/docs/blog/2018-10-18-creating-compelling-content-experiences/index.md
@@ -0,0 +1,129 @@
+---
+title: "Journey to the Content Mesh Conclusion: Creating Compelling Content Experiences"
+author: "Sam Bhagwat"
+"date": 2018-10-18
+tags: ["content-mesh"]
+---
+
+_This is Part 5, the conclusion of a series. Part 1 is_ [The Journey to a Content Mesh](/blog/2018-10-04-journey-to-the-content-mesh)_; Part 2 is_ [Unbundling of the CMS](/blog/2018-10-10-unbundling-of-the-cms)_; Part 3 is_ [The Rise of Modern Web Development](/blog/2018-10-11-rise-of-modern-web-development); _Part 4 is_ [Why Mobile Performance is Crucial](/blog/2018-10-16-why-mobile-performance-is-crucial).
+
+In the last three sections, we’ve described the different facets of how to create modern, compelling content experiences. We’ve covered trends in [content management](/blog/2018-10-10-unbundling-of-the-cms), [web development](/blog/2018-10-11-rise-of-modern-web-development), and [website performance](/blog/2018-10-16-why-mobile-performance-is-crucial).
+
+While these trends target different stakeholders, they’re deeply interrelated. That’s because to adopt a new architecture in one area, you often need to adopt new technologies in the other two.
+
+With users after user writing headlines like "[Gatsby + Contentful + Netlify (and Algolia)](https://www.gatsbyjs.org/blog/2017-12-06-gatsby-plus-contentful-plus-netlify/)" -- grouping a React-based website framework, a headless CMS, a static host + CDN, and a search provider -- it’s clear these these technologies are meant to be used together.
+
+Website teams moving to this space have to plan four steps -- one for each category, plus integration.
+
+<figure>
+  <img alt="" src="./modern-website-performance.png" />
+  <figcaption>
+    Three facets of modern website projects
+  </figcaption>
+</figure>
+
+## Moving to the content mesh
+
+### First, choose content systems.
+
+In a modular CMS system, website teams can [use preferred workflows to choose your content systems](/blog/2018-10-10-unbundling-of-the-cms).
+
+This allows content teams to replace their heavyweight CMS monolith with their choice of:
+
+- A spreadsheet and text files (for extremely simple sites).
+- Specialized systems tailored to their use case, such as Shopify + Salsify + Bazaarvoice for an e-commerce site.
+- A headless cloud CMS with rich content modelling capabilities, such as Contentful.
+
+### Second, pick a UI development library
+
+[React and Angular are both excellent, ubiquitious, modern choices](/blog/2018-10-11-rise-of-modern-web-development), with rich community ecosystems to address website-specific concerns like:
+
+- SEO
+- Routing
+- Accessibility
+- i18n
+
+### Third, choose a performance strategy
+
+There are two main approaches to performance -- [payload optimization and delivery optimization](https://www.gatsbyjs.org/blog/2018-10-16-why-mobile-performance-is-crucial#how-performance-optimization-works).
+
+Payload optimization involves performance-enhancing development practices. Delivery optimization means compiling websites to static files that can be served from a global CDN, rather than running servers and databases.
+
+Often, to ensure a fast site, you'll need both.
+
+To do delivery optimization, you'll need to pick a JAMStack site generator like Hugo or Gatsby.
+
+To do payload optimization, your team will need to implement a [long performance checklist](https://www.smashingmagazine.com/2018/01/front-end-performance-checklist-2018-pdf-pages/), or pick a framework such as Gatsby that [performs payload optimization](https://www.gatsbyjs.org/features/#legend) out of the box.
+
+### Fourth, choose your content mesh
+
+To truly engage users, you need a modern website -- a modular CMS architecture, modern development framework, and cutting-edge performance.
+
+The challenge for website teams is: how to achieve this without a lot of costly, time-intensive custom integration work?
+
+The answer: choose a content mesh. A content mesh:
+
+- pulls in data from your headless CMS systems
+
+- enables you to develop in your preferred UI library while providing website tooling
+
+- automatically makes your site fast out of the box
+
+<figure>
+  <img alt="The modern website landscape" src="./content-mesh.png" height="300" />
+  <figcaption>
+   The Content Mesh integrates <b>headless</b> content systems, modern development tools, and website performance
+  </figcaption>
+</figure>
+
+## Content Mesh Alternatives
+
+Website teams searching for a content mesh can consider:
+
+- utilizing vendor integrations
+- assorted JAMStack solutions
+- Gatsby
+
+While some solutions have _part_ of the puzzle, only Gatsby comes with out-of-the-box CMS integrations, a modern development framework, and cutting-edge performance.
+
+**Content vendor integrations**
+
+One option for website teams is to use existing vendor integrations to glue CMS systems together.
+
+For example, a team could build a site with Shopify, using their Liquid Template engine, pull in product listing data from Salsify, and reviews from Bazaarvoice.
+
+While this can solve the CMS integration problem, it locks the website in an idiosyncratic development environment without helping solve website performance.
+
+**Assorted JAMStack solutions**
+
+Another option is the JAMstack space, with a proliferation of tools that make sites fast. These tools tend to _either_ support modern development frameworks _or_ connect to content systems, but not both.
+
+For example, VuePress and Nuxt.js allow teams to build sites in Vue, but don't offer connections with any enterprise content systems -- they require content to be stored as markdown files within the code repository.
+
+Middleman allows connections to third-party data sources, though currently only DatoCMS and Contentful are supported.
+
+**Gatsby**
+
+Gatsby is the only content mesh option that creates fast websites, supports modern development frameworks, _and_ connects to enterprise content systems. Gatsby features:
+
+- **Integrations with 120+ backends**, including 15+ enterprise content systems like Wordpress, Drupal, Contentful, Contentstack, Salsify and Shopify, as well as the ability to add additional sources.
+
+- **A React development environment**, along with key plugins that provide key website features like SEO, routing, accessibility, and i18n.
+
+- **Lightning-fast out-of-the-box performance**, including both payload and delivery optimizations.
+
+## Conclusion
+
+Yesterday, publishing on the web was difficult. The CMS emerged as a single application to store content and build sites.
+
+Today, the CMS is being reimagined.
+
+With maturity comes growing functionality and complexity; a shift from monolithic to modular architectures.
+
+Today, there's a multitude of vendors, frameworks, and approaches for content modelling, authentication, search, analytics, payments, development environemnt, performance, and so on.
+
+The key question becomes: how to bring these pieces into a unified whole?
+
+Yesterday, our challenge was _creating a digital experience_.
+
+Today, our challenge is _making that experience incredible_.
diff --git a/...18-10-18-creating-compelling-content-experiences/modern-website-performance.png b/...18-10-18-creating-compelling-content-experiences/modern-website-performance.png