Book Image

Elevating React Web Development with Gatsby

Book Image

Elevating React Web Development with Gatsby

Overview of this book

Gatsby is a powerful React static site generator that enables you to create lightning-fast web experiences. With the latest version of Gatsby, you can combine your static content with server-side rendered and deferred static content to create a fully rounded application. Elevating React Web Development with Gatsby provides a comprehensive introduction for anyone new to GatsbyJS and will help you get up to speed in no time. Complete with hands-on tutorials and projects, this easy-to-follow guide starts by teaching you the core concepts of GatsbyJS. You'll then discover how to build performant, accessible, and scalable websites with the GatsbyJS framework. Once you've worked through the practical projects in the book, you'll be able to build anything from a personal website to large-scale applications with authentication and make your site rise through those SEO rankings. By the end of this Gatsby development book, you'll be well-versed in every aspect of the tool's performance and accessibility and have learned how to build client websites that your users will love.
Table of Contents (18 chapters)
1
Part 1: Getting Started
7
Part 2: Going Live
12
Part 3: Advanced Concepts

Contributing to the plugin ecosystem

So, you've built a plugin and now you want to use it in a separate Gatsby project? Or perhaps you think the plugin could help other developers? In either case, you'll need to publish your plugin. By publishing your plugin with npm, your plugin will automatically become visible on Gatsby's site plugins page (https://www.gatsbyjs.com/plugins). Let's start this journey by looking at a pre-publish checklist.

Pre-publish checklist

Before we publish our plugin, it's important to ensure that we are ready to do so. The following is a suggested pre-publish checklist:

  • Ensure your plugin's name explains what it does. This might seem a little trivial but naming your plugin in a way that makes it clear what it does will make it easier to find online.
  • Ensure your plugin's name is unique. Two npm packages cannot share the same name, so you mustn't try and deploy a package with a name that is already in...