OceanSoft

Follow

OceanSoft

Follow
โšก Building a Production-Ready Headless CMS with Jamstack (Gatsby and Contentful) ๐ŸŽ

โšก Building a Production-Ready Headless CMS with Jamstack (Gatsby and Contentful) ๐ŸŽ

OceanSoft's photo
OceanSoft
ยทOct 11, 2022ยท

4 min read

Play this article

Table of contents

๐ŸŽฏ Implementing Headless Architecture for Content Management System (CMS) using Jamstack (JavaScript, APIs, and Markup) and Cloud Hosting (Gatsby Cloud, Netlify, AWS Amplify) โšก

๐Ÿš€ Live Demo: academy.job4u.io

๐ŸŒฅ๏ธ The cloud journey generally involves migrating and modernizing websites and apps, including building and hosting websites, developing web and mobile apps, and monitoring and managing them. This hands-on series illustrates how to build a production-ready Headless CMS and Headless eCommerce using Jamstack (stands for JavaScript, API, and Markup) on Cloud (Heroku, AWS ...).

  1. โœ… โšก Building a Production-Ready Headless CMS with Jamstack (Gatsby and Contentful) ๐ŸŽ
  2. โ˜‘๏ธ ๐Ÿณ Dockerizing Strapi - Open-Source NodeJS Headless CMS
  3. โ˜‘๏ธ ๐Ÿณ Medusa Headless-eCommerce - Open-Source Shopify alternative โšก

Incremental Architecture Approach

We'll look at a traditional waterfall project timeline, in which all evaluation is done upfront, step by step, before approval and kickoff. After that, you add the content to the CMS, develop the site, do some launch preparation, and then launch it ๐Ÿš€.

OLD - Traditional Project Timeline.png

Using incremental architecture, project timelines can be reduced by making architectural decisions during the project rather than delaying the start of the project. You can also synchronize work across multiple systems, such as Headless CMS, Headless eCommerce, and Analytics.

By mocking your content during initial development, you can add content to your CMS while developing your site. You can also add content to your CMS/eCommerce Backend while working on your frontend.

NEW - Incremental Architecture.png

Headless Architecture for CMS

Traditional or monolithic Web-first CMS, such as WordPress, combine the frontend (website design and layout) and backend (the interface for editing and creating content) into a single application.

The next-generation Content-first Headless CMS use an API for content delivery and allow complete separation of the backend (creation and storage) and frontend (design and deployment). Headless architecture not only rewards better performance and flexibility but also provides stronger security by making it nearly impossible for end-users to access the backend.

Headless Architecture

Headless CMS with Jamstack

In the diagram below, Jamstack's typical website is made up of several types of systems, such as Gatsby and Contentful/Strapi CMS, that are fast, secure, and offer a great digital experience.

headless-cms-strapi-gatsby.png

By utilizing modular architecture, you can not only achieve better business results, but also do so in an accelerated timeframe. This proves to all your stakeholders and clients the value of new technologies.

Modular Architecture

Reference: Ship your Contentful website faster with incremental architecture

Cloud Hosting (Gatsby Cloud, Netlify, AWS Amplify)

  • โœ… AWS Amplify
  • โ˜‘๏ธ Gatsby Cloud
  • โ˜‘๏ธ Netlify

[Webhook] AWS Amplify & Contentful

  • [ ] .env --> Amplify > Environment variables

  • [ ] 1. Create an incoming webhook to publish content updates.

    • [x] Choose App Settings > Build Settings > Incoming webhooks, and then choose Create webhook. This webhook enables you to trigger a build in the Amplify Console on every POST to the HTTP endpoint.
    • [x] After you create the webhook, copy the URL (it looks like webhooks.amplify.ap-southeast-1.amazonaws.c..)
  • [ ] 2. Go back to the Contentful dashboard, and choose Settings > Webhooks. Then choose Add Webhook. Paste the webhook URL you copied from the Amplify Console into the URL section and update the Content Type to application/json. Choose Save.

๐Ÿ“š Checklist Template ๐ŸŽ“

#FeatureDescriptionYour Site
01๐ŸŽฏ IntegrationsEnabling Contentful CMS Integrationโœ…
02Enabling Algolia Integration (search system)โœ…
03Enabling Disqus/Graph/Facebook Comments Integration (blog commenting)
04Enabling MailChimp integration (newsletter list building)
05Enabling Web App Manifestโœ…
06๐ŸŽฏ SEOAdding your Site's metadata SEO tagsโœ…
07Enabling Google Analytics Trackingโœ…
08Enabling Automatic Sitemap Generationโœ…
09๐ŸŽฏ BrandingAdding your Brand's colorsโœ…
10Adding your Social Media linksโœ…
11Adding your Logo to header and footerโœ…
12Adding your Faviconโœ…
13Adding fonts to match your brand
14๐ŸŽฏ Form HandlingSetting up Contact Form with Netlify Forms
15๐ŸŽฏ Deployment ConfigurationSetting up a Git repository
16Deploying a site to Amplify / NetlifyAmplify
17Configuring Your Site for Continuous Deployment via Gitโœ…
18Enabling a Contentful CMS Hook for automatic site-buildingโœ…
19Setting up your custom domainโœ…
20Temporary URLโœ…

๐ŸŽ Installation Service: Gatsby & Contentful CMS-Blog

๐Ÿ’ฒ Service Fee: $500 (Gatsby Theme + Support + Installation Service)

โŒ› Turnaround: 1 Business Day

๐ŸŽฏ Within 1 business day, you will receive the source code for your Amplify/Netlify-hosted website, as well as a temporary URL.

ย 
Share this