From bdec78eb4939c91e40731fd7fef124617b713de4 Mon Sep 17 00:00:00 2001 From: Kevin Date: Thu, 14 May 2020 11:12:15 -0400 Subject: [PATCH] Updated README - fixed fragments anchor --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 509cfcc..0603b29 100644 --- a/README.md +++ b/README.md @@ -56,7 +56,7 @@ export function() { } ``` -5. For more flexibility and advanced usage checkout [Fragments]() +5. For more flexibility and advanced usage check out [Fragments](#fragments") ## 🤔 What is This? Gatsby is an amazing tool that has helped advance modern web development in significant ways. While many love it for its magical frontend concotion of static generation an rehydration via React, easy routing, smart prefetching, image rendering, etc., one of the key areas where it stands out from other similar tools is its GraphQL data layer. This feature is in large part the reason why some love Gatsby and why others choose to go in another direction. Being able to source data from multiple APIs, files, etc. and compile them altogether into a queryable GraphQL layer is ***amazing***, but many developers don't enjoy working with GraphQL. This is where GROQ comes in.