Few web dev technologies sparked joy for me like Gatsby, and I've been thinking about what real mastery in the framework looks like. The obvious things to me seem like:
Deep comfort with Reach Router and which of it's features can save work in certain instances.
Understanding what sort of query (static vs page) to use and when.
Some things I wonder about:
Which plugins one needs to know forwards and backwards, versus just looking up when the use case for it comes up.
Are there React features we're better off not using in Gatsby?
Are you or somebody you know an expert in Gatsby? What does expertise in the framework look like to you?
Top comments (4)
Some of the things I've learned after using Gatsby since v1.
This is a great list! Could you dig into what you mean when you say "optimize the entire site for SEO in a clean way"? Would that just be by using plugins like
gatsby-plugin-react-helmet, or is are there other major considerations for that?
Yeah for sure!
So, yes, using that plugin is a part of it. With respect to cleanly optimizing the site for SEO, we have to consider:
Because we want all of those different
PageTypes to be SEO-optimized, we gotta do a little bit of design work to figure out how to cleanly address that problem.
Perhaps if every Gatsby page or template that were wrapped in a
<Layout/>component, we might be able to provide some props to the
<Layout/>and do all the SEO-setup in one place (Layout).
Also, if we were to setup JSON-LD, that would probably be different for each
PageType(blog post JSON-LD vs. breadcrumb JSON-LD).
So there's a lot of things to consider about how to cleanly structure your SEO.
I wrote an article about this a while back, but it's a bit outdated now. Here's how I'm currently doing it on my blog.
I’m interested to know any answers to those questions as well. My experience with Gatsby is significantly low; I always felt like there’s much more to Gatsby than just building my blog.
FreeCodeCamp, I think, uses Gatsby but I’m not sure how it is actually used in the codebase.