From 33aff39ede60a1d190f5c3d6798380f0971a5eaa Mon Sep 17 00:00:00 2001 From: Kyle Mathews Date: Thu, 30 Jul 2020 13:09:59 -0700 Subject: [PATCH] Update index.md --- docs/blog/2019-04-25-plugin-authoring-study/index.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/blog/2019-04-25-plugin-authoring-study/index.md b/docs/blog/2019-04-25-plugin-authoring-study/index.md index f80b2de0ac810..e51e842096a2b 100644 --- a/docs/blog/2019-04-25-plugin-authoring-study/index.md +++ b/docs/blog/2019-04-25-plugin-authoring-study/index.md @@ -49,6 +49,7 @@ ANSWER: make time-consuming things take less time, and make frustrating things l People who use plugin authoring docs say they are super helpful; however, most people don’t know about them and solve challenges through looking at the source code of other plugins. While this works for many people, we think making this even easier is a positive change. + ## Solution - [Gatsby CLI to add scaffolding for source plugin creation #13376](https://github.com/gatsbyjs/gatsby/issues/13376) @@ -66,6 +67,7 @@ Examples of things that are confusing: - Most people don’t know how to write automated tests for plugins and mentioned building a site just to test the plugin, which they felt wasn't the most ideal way to test - Rebuilding for every change often “feels wrong” to people + ## Solution [Redesigned the plugin docs](https://github.com/gatsbyjs/gatsby/pull/13261/files) to include a category called "Creating Plugins" where we can document answers to people's concerns; for example, ideas for how to test plugins and advice to use yarn workspaces to avoid yarn link inconsistencies.