The Jamstack Book: Beyond static sites with JavaScript, APIs, and markup

inside front cover
The Jamstack Book
Copyright
dedication
contents
front matter
    foreword
    preface
    acknowledgments
    about this book
        Who should read this book
        How this book is organized: A road map
        About the code
        liveBook discussion forum
        Other online resources
    about the authors
    about the cover illustration
1 Why Jamstack?
    1.1 What is the Jamstack?
    1.2 A brief history of Jamstack
        1.2.1 The rise of static site generators
        1.2.2 From static sites to JAMstack
        1.2.3 From JAMstack to Jamstack
    1.3 The benefits of Jamstack architecture
        1.3.1 Performance
        1.3.2 Security
        1.3.3 Cost
    1.4 When Jamstack may not be the right choice
    1.5 Popular sites built with the Jamstack
        1.5.1 Smashing Magazine
        1.5.2 Nike
        1.5.3 Impossible Foods
        1.5.4 Restaurant Brands International (RBI)
        1.5.5 Digital.gov
    1.6 What you’ll learn in this book
    Summary
2 Building a basic Jamstack site
    2.1 Working with Eleventy
    2.1.1 Creating your first Eleventy site
    2.1.2 Working with template languages
    2.1.3 Adding layouts and includes
    2.1.4 Using collections in your Eleventy site
    2.1.5 Working with data
    2.2 Let’s build Camden Grounds
    2.3 Going further with Eleventy
    Summary
3 Building a blog
    3.1 Blogging with Jekyll
    3.2 Your first Jekyll site
    3.3 Writing a Jekyll post
        3.3.1 A liquid refresher
    3.4 Working with layouts and includes
        3.4.1 Layout inheritance
        3.4.2 Using includes
    3.5 Creating additional files
    3.6 Working with data
    3.7 Configuring your Jekyll blog
    3.8 Generating your site
    3.9 Building a Jekyll blog
    3.10 Going further with Jekyll
    Summary
4 Building a documentation site
    4.1 Requirements of a documentation site
    4.1.1 The example site requirements
    4.2 Choosing the right tools
    4.2.1 What is a headless CMS?
    4.2.2 Headless CMS options
    4.2.3 Why Netlify CMS?
    4.2.4 Static site generator (SSG) options
    4.2.5 Why Hugo?
    4.3 Building the example site
    4.3.1 Installing Hugo
    4.3.2 Creating a new Hugo site
    4.3.3 Setting up the Hugo Book theme
    4.3.4 Installing Netlify CMS
    4.3.5 Modeling content in Netlify CMS
    4.3.6 Deploying to Netlify
    4.3.7 Configuring GitHub for authentication
    4.3.8 Configuring Netlify for authentication
    4.3.9 Editing content as an admin
    4.3.10 The open authoring workflow
    4.3.11 Simplifying the open authoring workflow
    4.4 What’s next?
    Summary
5 Building an e-commerce site
    5.1 Requirements of an e-commerce site
    5.1.1 The example site requirements
    5.2 Choosing the right tools
    5.2.1 What is headless e-commerce?
    5.2.2 Headless e-commerce options
    5.2.3 Why Commerce.js?
    5.2.4 Static site generator options
    5.2.5 Why Next.js?
    5.3 Getting set up to build the example e-commerce site
    5.3.1 Setting up Next.js
    5.3.2 Setting up Commerce.js
    5.3.3 Setting Next.js environment variables
    5.3.4 Loading the Commerce.js SDK
    5.4 Building the Jam Store e-commerce site
    5.4.1 Creating the product listing component
    5.4.2 Building the product listing
    5.4.3 Building the Product Detail page
    5.4.4 Enabling add-to-cart functionality
    5.4.5 Building the shopping cart
    5.4.6 Adding Markdown content
    5.5 What’s next?
    Summary
6 Deployment
    6.1 Web servers—The tried-and-true way
    6.2 Cloud file storage providers
        6.2.1 Amazon S3
        6.2.2 Other cloud file storage hosting options
    6.3 Azure Static Web Apps
    6.4 Deploying with Vercel
    6.5 Deploying with Netlify
    Summary
7 Adding dynamic elements
    7.1 Forms, forms, and more forms
    7.1.1 Using Google Forms
    7.1.2 Integrating FormCake
    7.1.3 Other options
    7.2 Adding search
    7.2.1 Searching with Lunr
    7.2.2 Other options
    7.3 Other dynamic options
    Summary
8 Working with serverless computing
    8.1 What is serverless computing?
    8.2 Building serverless functions with Netlify
    8.2.1 Adding serverless computing to Camden Grounds
    8.2.2 More on Netlify functions
    8.3 Building serverless functions with Vercel
    8.3.1 Your first Vercel serverless function
    8.3.2 Vercel functions with dynamic path support
    8.3.3 Adding serverless functions to Camden Grounds (again)
    Summary
9 Adding a content management system
    9.1 Types of headless CMSs
    9.1.1 Pros and cons of Git-based headless CMSs
    9.1.2 Pros and cons of API-based headless CMSs
    9.2 Exploring popular headless CMSs
    9.2.1 Contentful
    9.2.2 Sanity
    9.2.3 Defining a content model using Sanity
    9.3 Using WordPress
    9.3.1 Installing WordPress locally with Local
    9.3.2 Installing the Gatsby plug-ins for WordPress
    9.3.3 Setting up Gatsby
    9.3.4 Exploring Gatsby’s data layer
    9.3.5 Consuming WordPress content in Gatsby
    9.3.6 Next steps in using WordPress as a headless CMS
    9.4 Connecting a CMS using a site builder
    9.4.1 WeWeb
    9.4.2 Strattic
    9.4.3 Stackbit
    9.5 What’s next?
    Summary
10 Migrating to the Jamstack
    10.1 What kind of site are you migrating?
    10.1.1 Content-heavy sites
    10.1.2 Web applications
    10.1.3 Large sites
    10.2 What functionality do you need to migrate?
    10.2.1 Popular third-party Jamstack services
    10.3 Making the move
    10.3.1 Don’t move everything at once
    10.3.2 Pick a headless CMS up front
    10.3.3 Consider building templates from scratch rather than porting
    10.3.4 Keep as much as possible
    10.4 What’s next?
    Summary
index
inside back cover