diff --git a/docs/contributing/blog-contributions.md b/docs/contributing/blog-contributions.md deleted file mode 100644 index dd7b42fdd86cd..0000000000000 --- a/docs/contributing/blog-contributions.md +++ /dev/null @@ -1,39 +0,0 @@ ---- -title: Blog Contributions ---- - -Blog posts are a great way to share your own experiences working with Gatsby at work or on a personal project. - -If you'd like to contribute a post to the Gatsby blog, please review the process and guidelines outlined below and submit your post idea using the [Gatsby blog proposal form](https://airtable.com/shr3449954866i3iF). - -## Blog proposal submission process - -1. Complete and submit the [Gatsby blog proposal form](https://airtable.com/shr3449954866i3iF). -2. A Gatsby team member will review your proposal and let you know if the proposal has been accepted within the next week or so. - - **If the post is accepted:** A Gatsby team member will work with you on a timeline for submitting and reviewing a draft of your blog post and set a tentative publishing date. - - **If the post is not accepted:** We’ll let you know if there are any alternative offers we can make (e.g. offer to retweet if you publish the piece elsewhere, suggest submitting it as an addition to a Gatsby doc, etc.). We’ll also do our best to explain why your proposal was not accepted and encourage you to revise your proposal based on that feedback and resubmit. Please don’t be discouraged from submitting another post in the future! - -If you have any questions about the process or your submission, please email [marketing@gatsbyjs.com](mailto:marketing@gatsbyjs.com). - -## Content guidelines for submitting a blog post proposal - -As a Gatsby community member, you have unique insight into the ins and outs of learning Gatsby, building with Gatsby, and contributing to Gatsby’s open source community. Contributing to the Gatsby blog is a great way to share your experiences and insights. Here are some guidelines for what kind of content is and isn’t a good fit for the Gatsby blog. - -Things we’re looking for in Gatsby blog content: - -- Information to help others overcome challenges you’ve faced while working with Gatsby -- Stories about how Gatsby helped you overcome different challenges on work and personal projects -- Showcasing a tool, fix, or other content you or someone else have contributed to Gatsby’s open source community -- Showcasing a tool, fix, or other content someone else has contributed to Gatsby’s open source community -- Clear and thoughtful explanations of technical details or complex concepts related to React, GraphQL, web and application development, open-source contribution, Gatsby core, and other Gatsby-adjacent subject matter -- Guidance and resources for learning React, GraphQL, HTML/CSS, web development, best practices, accessibility, SEO, Gatsby, different tool and CMS integrations, and other Gatsby-adjacent subject matter. -- Other topics that you think would be valuable to people learning about or working with Gatsby - -Things we’d like to avoid on the Gatsby blog: - -- **Docs content.** Some content is better found in the Gatsby docs guides and tutorials, as it can be found in a section for related content and not buried under pages of other paginated blog posts. -- **Promotional content.** Please don’t submit content to the Gatsby blog solely for the purpose of promoting a product, yourself, or link-building. - - **Here’s what you can do instead:** If you have a product or project you want to share on the Gatsby blog, focus on practical information, and make sure there’s a clear relationship with Gatsby or Gatsby-adjacent topics. You could write a step-by-step guide to using your product with Gatsby. You could write a case study highlighting the direct impact Gatsby had on your awesome project and offer helpful tips for others to recreate your success. -- **Content that doesn’t seem to have a clear benefit for Gatsby users and/or the Gatsby community.** For example, if you’re writing about a use-case or integration that’s extremely niche or unique to specific conditions that are really uncommon outside of your organization, the Gatsby blog might not be the best place for your content. Likewise, if your blog post doesn’t seem to have any direct relationship with Gatsby (or an interesting indirect relationship with Gatsby), then it may be more appropriate for a personal blog or another community blog. - -**Please note** that these are guidelines, not rules. If you think your blog post belongs on the Gatsby blog, we absolutely encourage you to submit it. While we reserve the right to decide what is and isn’t appropriate for the Gatsby blog, we also value and encourage your creativity and your contributions. diff --git a/docs/contributing/code-contributions.md b/docs/contributing/code-contributions.md index 88360fcf88311..e1d8ee4c55a9a 100644 --- a/docs/contributing/code-contributions.md +++ b/docs/contributing/code-contributions.md @@ -86,7 +86,7 @@ If you create a loader or plugin, we would love for you to open source it and pu Gatsby's policy is that "Using" example sites (like those in the [examples part of the repo](https://github.com/gatsbyjs/gatsby/tree/master/examples)) should only be around plugins that are maintained by the core team as it's hard to keep things up to date otherwise. -To contribute example sites, it is recommended to create your own GitHub repo and link to it from your source plugin, etc. You can also create a starter project and submit it to the [starter showcase](/starters/submissions). +To contribute example sites, it is recommended to create your own GitHub repo and link to it from your source plugin, etc. ## Debugging the build process diff --git a/docs/contributing/contributor-swag.md b/docs/contributing/contributor-swag.md deleted file mode 100644 index 92d76c701509b..0000000000000 --- a/docs/contributing/contributor-swag.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: Free Swag for Gatsby Contributors! ---- - -Gatsby relies on contributors from the open source community, and we want to make sure you know how much it means to us that you’re willing to put time and effort into [contributing to Gatsby](/contributing/#how-to-contribute). - -To show our appreciation, _**everyone who contributes to Gatsby is eligible to receive free swag!**_ - -![Gatsby contributors wearing swag. Left image shows a woman wearing a black T-Shirt with a light gray Gatsby logo on it. Middle image shows the Gatsby socks. Right image shows a man wearing a purple T-Shirt with a light purple Gatsby logo on it.](./images/gatsby-swag.jpg) - -## How to claim your free swag - -If you contribute to the Gatsby organization on GitHub, you can claim your swag by [logging into the Gatsby Store](https://store.gatsbyjs.org/) and requesting a discount code. With five or more contributions, you can claim your _**Level 2**_ swag. - -If you’ve contributed in other ways, such as giving talks about Gatsby, teaching others to use it, writing Gatsby articles/tutorials, participating in a Gatsby research project, or any other way, please fill out [this short form](https://forms.gle/zBnybrZNjsdpXvDx8) to let us know! - -## Details about free swag - -- We will send one item from our [swag store](https://store.gatsbyjs.org/) per swag tier -- Tier 1 swag includes most items valued 10 dollars or less -- Tier 2 swag includes most items valued 31 dollars or less -- Not all items are eligible due to high cost to create the swag. We’ll make it clear which items are not eligible -- There’s a limit of one free swag item per swag tier -- Shipping is free worldwide -- Additional details can be found in our [swag FAQs](https://github.com/gatsbyjs/store.gatsbyjs.org#frequently-asked-questions) - -> **NOTE:** Worldwide free shipping is a pilot program. If shipping costs get out of control, we may need to adjust this policy in the future. diff --git a/docs/contributing/docs-contributions/docs-writing-process.md b/docs/contributing/docs-contributions/docs-writing-process.md index 5860493adb787..83b77b2774dae 100644 --- a/docs/contributing/docs-contributions/docs-writing-process.md +++ b/docs/contributing/docs-contributions/docs-writing-process.md @@ -26,8 +26,6 @@ A GitHub issue for new learning material should indicate the format. Is it a Ref Does docs coverage exist anywhere on `gatsbyjs.com`? If so, would an alternative format help provide information for Gatsby learners of different skill and experience levels? For example, if a tutorial exists but there is no coverage in Reference Guides, adding more content in a different format would benefit users. -Please follow the [Gatsby blog post guidelines](/contributing/blog-contributions/) and do not suggest blog posts when what is needed is user documentation. - ## Gathering and validating supporting information Writing an effective doc that meets the needs of Gatsby users requires gathering information from various sources and applying those concepts to your original writing. You must digest and validate the details you uncover and understand them enough to describe them in a way that users of multiple skill levels can learn. @@ -71,6 +69,5 @@ Apply feedback from pull request reviews in order for them to be accepted. Furth - [How to File an Issue](/contributing/how-to-file-an-issue/) - [Gatsby Style Guide](/contributing/gatsby-style-guide/) - [Markdown Syntax Doc](/docs/reference/markdown-syntax/) -- [Blog Post Guidelines](/contributing/blog-contributions/) - [Docs site setup instructions](/contributing/docs-contributions/#docs-site-setup-instructions) - [How to Open a Pull Request](/contributing/how-to-open-a-pull-request/) diff --git a/docs/contributing/docs-contributions/index.md b/docs/contributing/docs-contributions/index.md index cdd58d193635e..a9435c9a883f1 100644 --- a/docs/contributing/docs-contributions/index.md +++ b/docs/contributing/docs-contributions/index.md @@ -4,7 +4,7 @@ title: Docs Contributions Gatsby, unsurprisingly, uses Gatsby for its documentation website. Thank you in advance and cheers for contributing to Gatsby documentation! It's people like you that make this community great! -> _When deciding where to contribute to Gatsby (docs or [blog](/contributing/blog-contributions/)?), check out the [docs structure](/contributing/docs-contributions/docs-structure/) page._ +> _When deciding where to contribute to Gatsby, check out the [docs structure](/contributing/docs-contributions/docs-structure/) page._ When writing (or reviewing) learning materials that show Gatsby users how to complete tasks, you are expected to **test out any code examples or steps to ensure they work**. This can also help with writing in your own words, rather than copying from other sources. If you have a demo project or code example that strengthens docs and you don't know where to put it, mention it to the Gatsby Documentation team in a PR. @@ -124,7 +124,3 @@ Sometimes it makes sense to move or rename a file as part of docs restructuring - Run proposed structure changes by the Gatsby docs team in [a GitHub issue](/contributing/how-to-file-an-issue/) to ensure your change is accepted. - Update all instances of the old URL to your new one. [Find and replace](https://code.visualstudio.com/docs/editor/codebasics#_search-across-files) in VS Code can help. Check that the context of the original link reference still makes sense with the new one. - -## Claim your swag - -After your first code contribution to the Gatsby repo (including documentation) you become eligible for a free shirt or pair of socks. See the [swag page](/contributing/contributor-swag/) for more details! diff --git a/docs/contributing/gatsby-governance-model.md b/docs/contributing/gatsby-governance-model.md index 059834f0fc408..89632ccd34c36 100644 --- a/docs/contributing/gatsby-governance-model.md +++ b/docs/contributing/gatsby-governance-model.md @@ -35,7 +35,7 @@ We accept all types of contributions to [`packages`](https://github.com/gatsbyjs - [`gatsby`](https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby) - [`gatsby-core-utils/remote-file-utils`](https://github.com/gatsbyjs/gatsby/tree/master/packages/gatsby-core-utils/src/remote-file-utils) -For these two packages, we ask you to open a [feature request](#feature-requests) (or for larger changes an [RFC](/contributing/rfc-process/)) before opening PRs for features. Contributions, such as bug fixes and documentation updates, can be made without any prior interaction with the team and don't require a feature request/RFC. +For these two packages, we ask you to open a [feature request](#feature-requests) before opening PRs for features. Contributions, such as bug fixes and documentation updates, can be made without any prior interaction with the team. ## Contributor levels @@ -54,7 +54,7 @@ Have you done something (big or small) to contribute to the health, success, or #### Recognized contributions - **GitHub:** Submitting a merged pull request -- **GitHub:** Sending in a detailed feature request or RFC +- **GitHub:** Sending in a detailed feature request - **GitHub:** Updating documentation - Helping people on GitHub and other platforms. - Answering questions on Stack Overflow, Twitter, etc. @@ -63,7 +63,7 @@ Have you done something (big or small) to contribute to the health, success, or #### Privileges -At this time we have no specific privileges for this role except that you can claim yourself [free Gatsby swag](/contributing/contributor-swag/). If you have ideas here please let us know! +At this time we have no specific privileges for this role. If you have ideas here please let us know! #### Responsibilities @@ -87,8 +87,8 @@ The Maintainer role is critical to the long-term health of Gatsby. Maintainers s There is no strict minimum number of contributions needed to reach this level, as long as you can show **sustained** involvement over some amount of time (at least a couple of weeks). -- **GitHub:** Submitting non-trivial pull requests and RFCs -- **GitHub:** Reviewing non-trivial pull requests and RFCs +- **GitHub:** Submitting non-trivial pull requests +- **GitHub:** Reviewing non-trivial pull requests - Supporting users and participating in community events - **GitHub:** Triaging and confirming user issues - This list is incomplete! Similar contributions are also recognized. @@ -174,11 +174,7 @@ If you’d like to learn more about how we approach the relationship between our ### Feature requests -Please open a [feature request on GitHub Discussions](https://github.com/gatsbyjs/gatsby/discussions/categories/ideas-feature-requests) to voice your ideas. For larger changes please consider opening an [RFC](/contributing/rfc-process/). The **Team** will review incoming requests and give a first assessment. - -### RFCs - -Please see the dedicated [RFC Process document](/contributing/rfc-process/) for more details. +Please open a [feature request on GitHub Discussions](https://github.com/gatsbyjs/gatsby/discussions/categories/ideas-feature-requests) to voice your ideas. The **Team** will review incoming requests and give a first assessment. ## Voting diff --git a/docs/contributing/index.md b/docs/contributing/index.md index 19234d67070f3..fe1e2bb9b3a2b 100644 --- a/docs/contributing/index.md +++ b/docs/contributing/index.md @@ -17,7 +17,6 @@ In the interest of fostering an open and welcoming environment, we as contributo ### Gatsby news -- Read and discuss about [Request for Comment (RFC) proposals](/contributing/rfc-process) - Watch videos on [Gatsby's YouTube channel](https://www.youtube.com/c/Gatsbyjs/videos) to see past GatsbyConf presentations and tutorial walkthroughs - Follow the [official blog](/blog/) @@ -38,7 +37,7 @@ Read the [Gatsby Style Guide](/contributing/gatsby-style-guide/) to learn more a ## How to contribute -We want contributing to Gatsby to be fun, enjoyable, and educational for anyone and everyone. If you're interested in participating in the Gatsby community, contributions go far beyond pull requests and commits. We are thrilled to receive a variety of other contributions and as our way of saying “thank you” to our contributors, **all contributors are eligible for [free Gatsby swag](/contributing/contributor-swag/)** — whether you’re contributing code, docs, a talk, an article, or something else that helps the Gatsby community. [Learn how to claim free swag for contributors](/contributing/contributor-swag/). +We want contributing to Gatsby to be fun, enjoyable, and educational for anyone and everyone. If you're interested in participating in the Gatsby community, contributions go far beyond pull requests and commits. ### Help fellow users @@ -56,11 +55,10 @@ Contributing bug fixes or new features are the most direct form of contribution There are a few other ways of contributing to the Gatsby ecosystem: -- **Contribute to Gatsby's blog**. Want to write about Gatsby? Read the [blog contributions doc](/contributing/blog-contributions) to get your blog post onto gatsbyjs.com. - **Develop learning materials.** Strengthen your expertise by writing a blog post, developing a workshop, creating video tutorials, or present your knowledge as a presentation on meetups and conferences. -- **Create a plugin.** Learn how to [create a plugin](/docs/how-to/plugins-and-themes/) and [submit it to the Plugin Library](/docs/how-to/plugins-and-themes/submit-to-plugin-library/). +- **Create a plugin.** Learn how to [create a plugin](/docs/how-to/plugins-and-themes/). - **Contribute to the Gatsby User Collective.** Interested in working on plugins that benefit the whole community? You can find them in the [Gatsby User Collective repository](https://github.com/gatsby-uc/plugins). -- **Create a Gatsby starter.** Created a starter? Share it with the community and [submit it to the Starter Library](/starters/submissions). +- **Create a Gatsby starter.** Created a starter? Share it with the community. ### Help triage issues @@ -74,8 +72,6 @@ There are many reasons to contribute to Gatsby and open source software in gener - **Improving your skills.** When you work on a Gatsby issue or pull request, inevitably you'll learn more about how something works in the project; either by asking questions and gathering info or by digging deeper into the code yourself. There's a skill-building benefit to contributing to OSS! -- **Getting free swag!** By participating in the repo on GitHub, you can become eligible for free swag that the Gatsby team offers as a way to say thank you. With 5 contributions, you can advance to a second level with even more swag options! Learn more about this [sweet swag deal](/contributing/contributor-swag/). - - **Becoming an expert.** You might start off totally new to a project like Gatsby or React.js, and by building things and [opening issues](/contributing/how-to-file-an-issue/) when you encounter a new challenge or a bug, you'll learn a ton over time. Staying current with your favorite framework through its open source repo can also give you a leading edge on forthcoming changes. Eventually, you could find your knowledge of said project has grown so much that you've become an expert. Celebrate by updating your résumé! - **Speaking at conferences.** With those skills you've earned yourself working in open source, why not share that knowledge with the world? Web platform conferences the world over are continually looking for speakers and fresh takes on popular topics. Did you build something with Gatsby that you're excited about? The [industry would love to hear from you](http://weareallaweso.me/)! diff --git a/docs/contributing/rfc-process.md b/docs/contributing/rfc-process.md deleted file mode 100644 index 7fb667d18797d..0000000000000 --- a/docs/contributing/rfc-process.md +++ /dev/null @@ -1,152 +0,0 @@ ---- -title: RFC process ---- - -## What is the RFC process? - -Many changes, including bug fixes and documentation improvements can be implemented and reviewed via the normal GitHub pull request workflow. - -Some changes, however, are "substantial", and we ask that these be put through a bit of a design process and produce a consensus among the Gatsby core team. - -The "RFC" (request for comments) process is intended to provide a consistent and controlled path for new features to enter the project. - -- [Active RFC List](https://github.com/gatsbyjs/gatsby/discussions/categories/rfc) -- [List of implemented RFCs](https://github.com/gatsbyjs/gatsby/discussions/categories/rfc?discussions_q=category%3ARFC+label%3A%22status%3A+completed%22) - -## When to follow this process - -You should consider using this process if you intend to make "substantial" changes to Gatsby or its documentation. Some examples that would benefit from an RFC are: - -- A new feature that creates new API surface area, and would require a feature flag if introduced. -- The removal of features that already shipped as part of the release channel. -- The introduction of new idiomatic usage or conventions, even if they do not include code changes to Gatsby itself. - -The RFC process is a great opportunity to get more eyeballs on your proposal before it becomes a part of a released version of Gatsby. Quite often, even proposals that seem "obvious" can be significantly improved once a wider group of interested people have a chance to weigh in. - -The RFC process can also be helpful to encourage discussions about a proposed feature as it is being designed, and incorporate important constraints into the design while it's easier to change, before the design has been fully implemented. - -Some changes do not require an RFC: - -- Rephrasing, reorganizing or refactoring addition or removal of warnings -- Additions that strictly improve objective, numerical quality criteria (speedup, better browser support) -- Additions only likely to be _noticed by_ other implements-of-Gatsby, invisible to users-of-Gatsby. - -## What the process is - -In short, to get a major feature added to Gatsby, one usually first puts up a Discussion on GitHub. At that point the RFC is 'active' and may be implemented with the goal of eventual inclusion into Gatsby. - -- Copy the RFC template into your clipboard: - - ```md - ## Summary - - Brief explanation of the feature. - - ## Try it out - - Section with instructions on how to use the feature, e.g. with a canary. - - - - ### CodeSandbox - - Provide an up-to-date CodeSandbox with an example project using the canary. Users can use this project to provide minimal reproductions. - - ## Basic example - - If the proposal involves a new or changed API, include a basic code example. - Omit this section if it's not applicable. - - ## Motivation - - Why are we doing this? What use cases does it support? What is the expected - outcome? - - Please focus on explaining the motivation so that if this RFC is not accepted, - the motivation could be used to develop alternative solutions. In other words, - enumerate the constraints you are trying to solve without coupling them too - closely to the solution you have in mind. - - ## Detailed design - - This is the bulk of the RFC. Explain the design in enough detail for somebody - familiar with Gatsby to understand, and for somebody familiar with the - implementation to implement. This should get into specifics and corner-cases, - and include examples of how the feature is used. Any new terminology should be - defined here. - - ## Drawbacks - - Why should we _not_ do this? Please consider: - - - implementation cost, both in term of code size and complexity - - whether the proposed feature can be implemented in user space - - the impact on teaching people Gatsby - - integration of this feature with other existing and planned features - - cost of migrating existing Gatsby applications (is it a breaking change?) - - There are tradeoffs to choosing any path. Attempt to identify them here. - - ## Alternatives - - What other designs have been considered? What is the impact of not doing this? - - ## Adoption strategy - - If we implement this proposal, how will existing Gatsby developers adopt it? Is - this a breaking change? Can we write a codemod? Should we coordinate with - other projects or libraries? - - ## How we teach this - - What names and terminology work best for these concepts and why? How is this - idea best presented? As a continuation of existing Gatsby patterns? - - Would the acceptance of this proposal mean the Gatsby documentation must be - re-organized or altered? Does it change how Gatsby is taught to new developers - at any level? - - How should this feature be taught to existing Gatsby developers? - - ## Unresolved questions - - Optional, but suggested for first drafts. What parts of the design are still - TBD? - ``` - -- [Open a new GitHub discussion](https://github.com/gatsbyjs/gatsby/discussions/categories/rfc) in the RFC category -- Fill in the RFC. Put care into the details: **RFCs that do not present convincing motivation, demonstrate understanding of the impact of the design, or are disingenuous about the drawbacks or alternatives tend to be poorly-received**. -- As the RFC will receive design feedback from the larger community, you should be prepared to revise it in response. So build consensus and integrate feedback. RFCs that have broad support are much more likely to make progress than those that don't receive any comments. -- Eventually, the team will decide whether the RFC is a candidate for inclusion in Gatsby. -- RFCs that are candidates for inclusion in Gatsby will enter a "final comment period" lasting 3 calendar days. The beginning of this period will be signaled with a comment. -- An RFC can be modified based upon feedback from the team and community. -- An RFC may be rejected by the team after public discussion has settled and comments have been made summarizing the rationale for rejection. A member of the team should then add the label "status: rejected". -- An RFC may be accepted at the close of its final comment period. A team member will add the label "status: accepted". - -## The RFC lifecycle - -Once an RFC becomes active, the authors may implement it and submit the feature as a pull request to the Gatsby repo. Becoming 'active' is not a rubber stamp, and in particular still does not mean the feature will ultimately be merged; it does mean that the core team has agreed to it in principle and are amenable to merging it. - -Furthermore, the fact that a given RFC has been accepted and is 'active' implies nothing about what priority is assigned to its implementation, nor whether anybody is currently working on it. - -Modifications to active RFCs can be done by editing the discussion/commenting on it. We strive to write each RFC in a manner that it will reflect the final design of the feature; but the nature of the process means that we cannot expect every accepted RFC to actually reflect what the end result will be at the time of the next major release; therefore we try to keep each RFC document somewhat in sync with the -language feature as planned, tracking such changes via followup changes to the document. - -## Implementing an RFC - -The author of an RFC is not obligated to implement it. The RFC author (like any other developer) is welcome to post an implementation for review after the RFC has been accepted. - -If you are interested in working on the implementation for an 'active' RFC, but cannot determine if someone else is already working on it, feel free to ask (e.g. by leaving a comment on the associated issue). - -## Reviewing RFCs - -Each month the team will attempt to review some set of open RFC discussions. - -Every accepted feature should have a core team champion, who will represent the feature and its progress. - -**Gatsby's RFC process owes its inspiration to the [React RFC process], [Yarn RFC process], [Rust RFC process], and [Ember RFC process]** - -[react rfc process]: https://github.com/reactjs/rfcs -[yarn rfc process]: https://github.com/yarnpkg/rfcs -[rust rfc process]: https://github.com/rust-lang/rfcs -[ember rfc process]: https://github.com/emberjs/rfcs diff --git a/docs/docs/conceptual/data-fetching.md b/docs/docs/conceptual/data-fetching.md index bd399da828c05..59510238127ed 100644 --- a/docs/docs/conceptual/data-fetching.md +++ b/docs/docs/conceptual/data-fetching.md @@ -215,7 +215,6 @@ The repo's star count is fetched at runtime; if you refresh the page, this numbe You may be interested in other projects (both used in production and proof-of-concepts) that illustrate this usage: - [Live example][example site] of the code used in this guide -- [Gatsby store](https://github.com/gatsbyjs/store.gatsbyjs.org): with static product pages at build time and client-side interactions for e-commerce features - [Gatsby mail](https://github.com/DSchau/gatsby-mail): a client-side email application - [Example repo fetching data using Apollo](https://github.com/jlengstorf/gatsby-with-apollo) diff --git a/docs/docs/conceptual/gatsby-core-philosophy.md b/docs/docs/conceptual/gatsby-core-philosophy.md index 8e650a748bab6..faec0fc3ca73a 100644 --- a/docs/docs/conceptual/gatsby-core-philosophy.md +++ b/docs/docs/conceptual/gatsby-core-philosophy.md @@ -111,7 +111,7 @@ Two of Gatsby’s core strengths are its community and ecosystem. We’re convinced that the right path forward is to continue working in the open with both trust and support of our community. -Anyone can [open an issue](/contributing/how-to-file-an-issue/) and ask a question, and we'll respond. Anyone can submit a pull request, and we'll give honest feedback on it. Anyone can [submit an RFC](/contributing/rfc-process/) to make a major change to Gatsby. And when we want to do this, we'll submit an RFC as a proposal. +Anyone can [open an issue](/contributing/how-to-file-an-issue/) and ask a question, and we'll respond. Anyone can submit a pull request, and we'll give honest feedback on it. Many of Gatsby's key features emerged from conversation between contributors. If you plumb through Gatsby's old issues, you'll see discussion of many of the core ideas that led to Gatsby -- from our plugin system to performance optimizations and so on. diff --git a/docs/docs/creating-a-starter.md b/docs/docs/creating-a-starter.md index 59c6f1af2b26c..0a036949c8600 100644 --- a/docs/docs/creating-a-starter.md +++ b/docs/docs/creating-a-starter.md @@ -75,10 +75,6 @@ For more accessibility help, check out the [A11y Project checklist](https://a11y Since starters are Gatsby projects, you can run `gatsby develop` or `gatsby build` and then `gatsby serve` in order to ensure your starter is working. If you'd like to be extra thorough and make sure the `gatsby new` command works with your starter, you can run `gatsby new project-name ../relative/path/to/your/starter`, replacing the final part of that command with the appropriate relative path. -## Add your starter to the Gatsby Starter Library - -To make sure your starter is easily discoverable, you are welcome (but not required) to add it to the [Gatsby Starter Library](/starters/submissions). Add tags to your starter by first checking for existing ones (like `contentful`, `csv`, etc.), and adding more if needed! - ## Further reading: - [How to create a Gatsby Starter](https://dev.to/emasuriano/how-to-create-a-gatsby-starter-42m8) by Emanuel Suriano diff --git a/docs/docs/how-to/adding-common-features/building-a-site-with-authentication.md b/docs/docs/how-to/adding-common-features/building-a-site-with-authentication.md index 74db050f95f94..55d7d32bf323e 100644 --- a/docs/docs/how-to/adding-common-features/building-a-site-with-authentication.md +++ b/docs/docs/how-to/adding-common-features/building-a-site-with-authentication.md @@ -75,9 +75,9 @@ More information on build related errors is available in the guide on [debugging ## Real-world example: Gatsby store -The [Gatsby store](https://github.com/gatsbyjs/store.gatsbyjs.org) is a live application built with Gatsby that implements authentication using Auth0. +The [Gatsby store](https://github.com/gatsbyjs/store.gatsbyjs.org) was an application built with Gatsby that implemented authentication using Auth0. -[Util functions](https://github.com/gatsbyjs/store.gatsbyjs.org/blob/master/src/utils/auth.js) in the Gatsby Store repo make use of Auth0's APIs to authenticate users with GitHub, and wrap Auth0's APIs to check that [some of the Auth0 code runs only in the browser](https://github.com/gatsbyjs/store.gatsbyjs.org/blob/master/src/utils/auth.js#L3). +[Utility functions](https://github.com/gatsbyjs/store.gatsbyjs.org/blob/master/src/utils/auth.js) in the Gatsby Store repo made use of Auth0's APIs to authenticate users with GitHub and ensured that some of the Auth0 code ran only in the browser. In order to protect authenticated content with a private route, a `` is implemented in the `` component that checks whether a user is authenticated or reroutes them to `/login`. diff --git a/docs/docs/how-to/custom-configuration/add-custom-webpack-config.md b/docs/docs/how-to/custom-configuration/add-custom-webpack-config.md index f870283011cbc..70a1908acb445 100644 --- a/docs/docs/how-to/custom-configuration/add-custom-webpack-config.md +++ b/docs/docs/how-to/custom-configuration/add-custom-webpack-config.md @@ -2,7 +2,7 @@ title: "Adding a Custom webpack Config" --- -_Before creating custom webpack configuration, check to see if there's a Gatsby plugin already built that handles your use case in the [plugins section](/docs/plugins/). If there's not yet one and your use case is a general one, consider contributing your plugin to the Gatsby Plugin Library so it's available to others (including your future self)._ +_Before creating custom webpack configuration, check to see if there's a Gatsby plugin already built that handles your use case in the [plugins section](/docs/plugins/). If there's not yet one and your use case is a general one, consider publishing your plugin so it's available to others (including your future self)._ To add custom webpack configurations, create (if there's not one already) a `gatsby-node.js` file in your root directory. Inside this file, export a function called `onCreateWebpackConfig`. diff --git a/docs/docs/how-to/plugins-and-themes/building-themes.md b/docs/docs/how-to/plugins-and-themes/building-themes.md index f7714e7456f12..7ffc2a405191e 100644 --- a/docs/docs/how-to/plugins-and-themes/building-themes.md +++ b/docs/docs/how-to/plugins-and-themes/building-themes.md @@ -86,7 +86,7 @@ Inside it you'll find: ## Publishing a Theme -After building your theme, you may want to publish it for the Gatsby community. To do so, please [publish your theme plugin to the plugin library](/docs/how-to/plugins-and-themes/submit-to-plugin-library/#publishing-a-plugin-to-the-library). +After building your theme, you may want to publish it for the Gatsby community by releasing it on npm. ## Further resources diff --git a/docs/docs/how-to/plugins-and-themes/submit-to-plugin-library.md b/docs/docs/how-to/plugins-and-themes/submit-to-plugin-library.md deleted file mode 100644 index 0bf8a36e80045..0000000000000 --- a/docs/docs/how-to/plugins-and-themes/submit-to-plugin-library.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -title: Submit to Plugin Library ---- - -## Publishing a plugin to the library - -In order to add your plugin to the [Plugin Library](/plugins/), you need to: - -1. Publish a package to npm (learn how on the [npm docs](https://docs.npmjs.com/getting-started/publishing-npm-packages)). -2. Include the [required files](/docs/files-gatsby-looks-for-in-a-plugin/) in your plugin code. -3. **Include a `keywords` field** in your plugin's `package.json`, containing `gatsby` and `gatsby-plugin`. If your plugin is a theme, please also include `gatsby-theme`. -4. Document your plugin with a README, using the contributing [plugin template](/contributing/docs-contributions/how-to-write-a-plugin-readme/) for reference. - -After doing so, Algolia will take up to 12 hours to add it to the library search index (the exact time necessary is still unknown), and wait for the daily rebuild of https://www.gatsbyjs.com to automatically include your plugin page to the website. Then, all you have to do is share your wonderful plugin with the community! - -## Notes - -### Keywords - -You can include other _relevant_ keywords to your `package.json` file to help interested users in finding it. As an example, a Markdown MathJax transformer would include: - -```json:title=package.json -"keywords": [ - "gatsby", - "gatsby-plugin", - "gatsby-transformer-plugin", - "mathjax", - "markdown", -] -``` - -### Images - -If you include images in your plugin repo's README, please make sure you are referencing the image using an absolute URL in order for the image to show on your plugin page. diff --git a/docs/docs/how-to/routing/client-only-routes-and-user-authentication.md b/docs/docs/how-to/routing/client-only-routes-and-user-authentication.md index 61b47d34695ee..319b9c0aa6df8 100644 --- a/docs/docs/how-to/routing/client-only-routes-and-user-authentication.md +++ b/docs/docs/how-to/routing/client-only-routes-and-user-authentication.md @@ -127,4 +127,3 @@ Your server configuration should handle `GET` requests to `/app/*` e.g. `/app/wh - [Gatsby repo "simple auth" example](https://github.com/gatsbyjs/gatsby/blob/master/examples/simple-auth/) - a demo implementing user authentication and restricted client-only routes - [Live version of the "simple auth" example](https://simple-auth.netlify.app/) -- [The Gatsby store](https://github.com/gatsbyjs/store.gatsbyjs.org) which also implements an authenticated flow diff --git a/docs/docs/reference/release-notes/migrating-from-v1-to-v2.md b/docs/docs/reference/release-notes/migrating-from-v1-to-v2.md index 95f92f1351ba6..7a775f132292b 100644 --- a/docs/docs/reference/release-notes/migrating-from-v1-to-v2.md +++ b/docs/docs/reference/release-notes/migrating-from-v1-to-v2.md @@ -508,8 +508,7 @@ export default function Routes() { } ``` -Here's a more complex example of migrating a `` component (used -in store.gatsbyjs.org) from React Router to @reach/router. +Here's a more complex example of migrating a `` component from React Router to @reach/router. ```diff import * as React from 'react'; @@ -549,7 +548,6 @@ in store.gatsbyjs.org) from React Router to @reach/router. Here are links to diffs for three sites with client routes upgraded to @reach/router: -- [store.gatsbyjs.org](https://github.com/gatsbyjs/store.gatsbyjs.org/pull/111) - [client-only-routes](https://github.com/gatsbyjs/gatsby/pull/6918/files#diff-69757e54875e28ef83eb8efe45a33fdf) - [simple-auth](https://github.com/gatsbyjs/gatsby/pull/6918/files#diff-53ac112a4b2ec760b26a86c953df2339) diff --git a/docs/docs/starters.md b/docs/docs/starters.md index 55e8a0414adcf..3a3e35a68614a 100644 --- a/docs/docs/starters.md +++ b/docs/docs/starters.md @@ -91,5 +91,4 @@ Learn [how to make a starter](/docs/creating-a-starter/) in the Gatsby docs. Sta Community starters are created and maintained by Gatsby community members. -- Looking for a starter for a particular use case? Browse starters that have been submitted to the [Starter Library](/starters/#Community). -- Have you built your own starter? [Submit it](/starters/submissions) for review to share it with the community by having it featured in the Gatsby Starter Library. +- Looking for a starter for a particular use case? Browse starters in the [Starter Library](/starters/#Community). diff --git a/docs/docs/tutorial/creating-a-source-plugin/part-0/index.mdx b/docs/docs/tutorial/creating-a-source-plugin/part-0/index.mdx index b4976773ba12e..d0d7815fe0b7a 100644 --- a/docs/docs/tutorial/creating-a-source-plugin/part-0/index.mdx +++ b/docs/docs/tutorial/creating-a-source-plugin/part-0/index.mdx @@ -79,7 +79,7 @@ Both of these topics will be covered in later parts of this tutorial, so stay tu Gatsby plugins are most often thought of as modules that are published to [npm](https://www.npmjs.com/) so that they can be shared and installed by others, but they can also be [local plugins](/docs/creating-a-local-plugin/) that exist only in a single site. -This same logic applies to source plugins. If you create a source plugin that you think others might make use of and you care to maintain it, please do publish it and [submit to the Gatsby plugin library](/docs/how-to/plugins-and-themes/submit-to-plugin-library/)! However, there is certainly no obligation to publish your plugin. If it serves its purpose for your use case just fine, keep it a local plugin. +This same logic applies to source plugins. If you create a source plugin that you think others might make use of and you care to maintain it, please do publish it! However, there is certainly no obligation to publish your plugin. If it serves its purpose for your use case just fine, keep it a local plugin. The parts at the end of this tutorial will teach you how to go about developing a plugin in a way that makes it easy to publish later. @@ -113,4 +113,4 @@ In Part 1 of the tutorial, you'll set up your project and learn how the project variant="SECONDARY" > Continue to Part 1 - \ No newline at end of file + diff --git a/docs/tutorial/authentication-tutorial.md b/docs/tutorial/authentication-tutorial.md index 40678bca892ff..cd123d02b6bef 100644 --- a/docs/tutorial/authentication-tutorial.md +++ b/docs/tutorial/authentication-tutorial.md @@ -415,7 +415,6 @@ If you want to learn more about using production-ready auth solutions, these lin - [Gatsby repo simple auth example](https://github.com/gatsbyjs/gatsby/tree/master/examples/simple-auth) - [A Gatsby email _application_](https://github.com/DSchau/gatsby-mail), using React Context API to handle authentication -- [The Gatsby store for swag and other Gatsby goodies](https://github.com/gatsbyjs/store.gatsbyjs.org) - [Building a blog with Gatsby, React and Webtask.io!](https://auth0.com/blog/building-a-blog-with-gatsby-react-and-webtask/) - [JAMstack PWA — Let’s Build a Polling App. with Gatsby.js, Firebase, and Styled-components Pt. 2](https://medium.com/@UnicornAgency/jamstack-pwa-lets-build-a-polling-app-with-gatsby-js-firebase-and-styled-components-pt-2-9044534ea6bc) - [JAMstack Hackathon Starter - Authenticated Gatsby app starter with Netlify Identity](/starters/sw-yx/jamstack-hackathon-starter) diff --git a/docs/tutorial/remark-plugin-tutorial.md b/docs/tutorial/remark-plugin-tutorial.md index e78e3a085e043..b85c3b181cf13 100644 --- a/docs/tutorial/remark-plugin-tutorial.md +++ b/docs/tutorial/remark-plugin-tutorial.md @@ -339,7 +339,7 @@ At this point, our plugin is now ready to be used. To see the resulting function ## Publishing the plugin -To share this plugin with others, you can extract the plugin to its own directory outside of this site and then publish it to npm so it can be accessed both on npm and [Submitted to the Plugin Library](/contributing/submit-to-plugin-library). +To share this plugin with others, you can extract the plugin to its own directory outside of this site and then publish it to npm so it can be accessed by the community. ## Summary diff --git a/examples/ecommerce-tutorial-with-stripe/README.md b/examples/ecommerce-tutorial-with-stripe/README.md index e8cdfa6a36340..6fc9a651ed690 100644 --- a/examples/ecommerce-tutorial-with-stripe/README.md +++ b/examples/ecommerce-tutorial-with-stripe/README.md @@ -23,6 +23,6 @@ This is a Gatsby e-commerce example based on https://www.gatsbyjs.com/tutorial/e - run `npm install` - run `gatsby develop` -### 💫 Build, Preview, and Deploy to Gatsby Cloud +### 💫 Build, Preview, and Deploy to Netlify [![Deploy to Gatsby](https://www.gatsbyjs.com/deploynow.png "Deploy to Gatsby")](https://www.gatsbyjs.com/dashboard/deploynow?url=https://github.com/thorsten-stripe/ecommerce-gatsby-tutorial) diff --git a/examples/using-shopify/gatsby-config.js b/examples/using-shopify/gatsby-config.js index 1993a79c206ae..e2552de6be92d 100644 --- a/examples/using-shopify/gatsby-config.js +++ b/examples/using-shopify/gatsby-config.js @@ -34,7 +34,7 @@ module.exports = { { resolve: `gatsby-source-shopify`, options: { - shopName: `gatsby-swag`, + shopName: `example-shop`, accessToken: process.env.SHOPIFY_ACCESS_TOKEN, }, }, diff --git a/integration-tests/functions/src/pages/index.js b/integration-tests/functions/src/pages/index.js index f410894b64b81..abdf803a31ea0 100644 --- a/integration-tests/functions/src/pages/index.js +++ b/integration-tests/functions/src/pages/index.js @@ -120,7 +120,7 @@ const links = [ url: "https://www.gatsbyjs.com/cloud", badge: true, description: - "Now you’re ready to show the world! Give your Gatsby site superpowers: Build and host on Gatsby Cloud. Get started for free!", + "Now you’re ready to show the world! Give your Gatsby site superpowers: Build and host on Netlify. Get started for free!", color: "#663399", }, ] diff --git a/packages/gatsby-cli/src/handlers/plugin.ts b/packages/gatsby-cli/src/handlers/plugin.ts index ce15456289164..00ae02a81fe82 100644 --- a/packages/gatsby-cli/src/handlers/plugin.ts +++ b/packages/gatsby-cli/src/handlers/plugin.ts @@ -18,7 +18,6 @@ Creating a plugin: - Creating a Local Plugin (https://www.gatsbyjs.com/docs/creating-a-local-plugin/) - Creating a Source Plugin (https://www.gatsbyjs.com/docs/how-to/plugins-and-themes/creating-a-source-plugin/) - Creating a Transformer Plugin (https://www.gatsbyjs.com/docs/how-to/plugins-and-themes/creating-a-transformer-plugin/) -- Submit to Plugin Library (https://www.gatsbyjs.com/contributing/submit-to-plugin-library/) - Maintaining a Plugin (https://www.gatsbyjs.com/docs/how-to/plugins-and-themes/maintaining-a-plugin/) `) return diff --git a/packages/gatsby-plugin-offline/src/__tests__/fixtures/public/index.html b/packages/gatsby-plugin-offline/src/__tests__/fixtures/public/index.html index 53b9025bf0c93..08cad06abc8e3 100644 --- a/packages/gatsby-plugin-offline/src/__tests__/fixtures/public/index.html +++ b/packages/gatsby-plugin-offline/src/__tests__/fixtures/public/index.html @@ -54,11 +54,11 @@ }) } catch (e) {} - Home | Gatsby Inc. + Home | Netlify - + diff --git a/packages/gatsby/README.md b/packages/gatsby/README.md index 0764e22bbad21..6c2aa52e4b54f 100644 --- a/packages/gatsby/README.md +++ b/packages/gatsby/README.md @@ -64,7 +64,7 @@ Gatsby helps professional developers efficiently create maintainable, highly-per - **Use a Modern Stack for Every Site.** No matter where the data comes from, Gatsby sites are built using React and GraphQL. Build a uniform workflow for you and your team, regardless of whether the data is coming from the same backend. -- **Host at Scale for Pennies.** Gatsby sites don’t require servers, so you can host your entire site on a CDN for a fraction of the cost of a server-rendered site. Many Gatsby sites can be hosted entirely free on [Gatsby Cloud](https://www.gatsbyjs.com/cloud/) and other similar services. +- **Host at Scale for Pennies.** Gatsby sites don’t require servers, so you can host your entire site on a CDN for a fraction of the cost of a server-rendered site. Many Gatsby sites can be hosted entirely free on [Netlify](https://www.netlify.com/) and other similar services. - **Use Gatsby's Centralized Data Layer Everywhere.** With Gatsby's [Valhalla Content Hub](https://www.gatsbyjs.com/products/valhalla-content-hub/) you can bring Gatsby's data layer to any project. Making it accessible via a unified GraphQL API for building content sites, eCommerce platforms, and both native and web applications. @@ -72,15 +72,15 @@ Gatsby helps professional developers efficiently create maintainable, highly-per ## 🚀 Ship your first Gatsby site in 5 Minutes -Click the link below to quickly try the workflow of developing, building, and deploying websites with Gatsby and Gatsby Cloud. +Click the link below to quickly try the workflow of developing, building, and deploying websites with Gatsby and Netlify. -[Deploy to Gatsby Cloud](https://www.gatsbyjs.com/dashboard/deploynow?url=https://github.com/gatsbyjs/gatsby-starter-blog&utm_source=github&utm_medium=link&utm_campaign=onboarding&utm_content=oss) +[Deploy to Netlify](https://app.netlify.com/start/deploy?repository=https://github.com/gatsbyjs/gatsby-starter-blog) At the end of this process, you'll have -1. a site working on Gatsby Cloud +1. a site working on Netlify 2. a new repository that is linked to that new site -3. as you push changes to your new repository, Gatsby Cloud will automatically rebuild and redeploy your site! +3. as you push changes to your new repository, Netlify will automatically rebuild and redeploy your site! ## 💻 Get started with Gatsby locally in 5 Minutes diff --git a/starters/blog/LICENSE b/starters/blog/LICENSE index 7e964c1ee5f4f..740a168527525 100644 --- a/starters/blog/LICENSE +++ b/starters/blog/LICENSE @@ -1,6 +1,6 @@ The BSD Zero Clause License (0BSD) -Copyright (c) 2020 Gatsby Inc. +Copyright (c) 2020 Netlify, Inc. Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted. diff --git a/starters/default/LICENSE b/starters/default/LICENSE index 7e964c1ee5f4f..740a168527525 100644 --- a/starters/default/LICENSE +++ b/starters/default/LICENSE @@ -1,6 +1,6 @@ The BSD Zero Clause License (0BSD) -Copyright (c) 2020 Gatsby Inc. +Copyright (c) 2020 Netlify, Inc. Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted. diff --git a/starters/default/src/pages/index.js b/starters/default/src/pages/index.js index f5a18e0fa0db2..dfead80845420 100644 --- a/starters/default/src/pages/index.js +++ b/starters/default/src/pages/index.js @@ -29,7 +29,7 @@ const links = [ text: "Build and Host", url: "https://www.gatsbyjs.com/cloud", description: - "Now you’re ready to show the world! Give your Gatsby site superpowers: Build and host on Gatsby Cloud. Get started for free!", + "Now you’re ready to show the world! Give your Gatsby site superpowers: Build and host on Netlify. Get started for free!", }, ] diff --git a/starters/gatsby-starter-minimal-ts/LICENSE b/starters/gatsby-starter-minimal-ts/LICENSE index 1365ca1886c39..a84077085e395 100644 --- a/starters/gatsby-starter-minimal-ts/LICENSE +++ b/starters/gatsby-starter-minimal-ts/LICENSE @@ -1,6 +1,6 @@ The BSD Zero Clause License (0BSD) -Copyright (c) 2022 Gatsby Inc. +Copyright (c) 2022 Netlify, Inc. Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted. diff --git a/starters/gatsby-starter-minimal-ts/src/pages/index.tsx b/starters/gatsby-starter-minimal-ts/src/pages/index.tsx index 2da81b8906591..1ee5d99767222 100644 --- a/starters/gatsby-starter-minimal-ts/src/pages/index.tsx +++ b/starters/gatsby-starter-minimal-ts/src/pages/index.tsx @@ -71,7 +71,7 @@ const docLinks = [ text: "GraphQL Typegen Documentation", url: "https://www.gatsbyjs.com/docs/how-to/local-development/graphql-typegen/", color: "#8954A8", - } + }, ] const badgeStyle = { @@ -131,7 +131,7 @@ const links = [ url: "https://www.gatsbyjs.com/cloud", badge: true, description: - "Now you’re ready to show the world! Give your Gatsby site superpowers: Build and host on Gatsby Cloud. Get started for free!", + "Now you’re ready to show the world! Give your Gatsby site superpowers: Build and host on Netlify. Get started for free!", color: "#663399", }, ] @@ -142,11 +142,13 @@ const IndexPage: React.FC = () => {

Congratulations
- — you just made a Gatsby site! 🎉🎉🎉 + + — you just made a Gatsby site! 🎉🎉🎉 +

- Edit src/pages/index.tsx to see this page - update in real-time. 😎 + Edit src/pages/index.tsx to see this + page update in real-time. 😎

    {docLinks.map(doc => ( diff --git a/starters/gatsby-starter-minimal/LICENSE b/starters/gatsby-starter-minimal/LICENSE index 7e964c1ee5f4f..740a168527525 100644 --- a/starters/gatsby-starter-minimal/LICENSE +++ b/starters/gatsby-starter-minimal/LICENSE @@ -1,6 +1,6 @@ The BSD Zero Clause License (0BSD) -Copyright (c) 2020 Gatsby Inc. +Copyright (c) 2020 Netlify, Inc. Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted. diff --git a/starters/gatsby-starter-minimal/src/pages/index.js b/starters/gatsby-starter-minimal/src/pages/index.js index 79970f9996633..c8ccc4a8a8715 100644 --- a/starters/gatsby-starter-minimal/src/pages/index.js +++ b/starters/gatsby-starter-minimal/src/pages/index.js @@ -118,7 +118,7 @@ const links = [ url: "https://www.gatsbyjs.com/cloud", badge: true, description: - "Now you’re ready to show the world! Give your Gatsby site superpowers: Build and host on Gatsby Cloud. Get started for free!", + "Now you’re ready to show the world! Give your Gatsby site superpowers: Build and host on Netlify. Get started for free!", color: "#663399", }, ] @@ -129,7 +129,9 @@ const IndexPage = () => {

    Congratulations
    - — you just made a Gatsby site! 🎉🎉🎉 + + — you just made a Gatsby site! 🎉🎉🎉 +

    Edit src/pages/index.js to see this page diff --git a/starters/gatsby-starter-plugin/LICENSE b/starters/gatsby-starter-plugin/LICENSE index 7e964c1ee5f4f..740a168527525 100644 --- a/starters/gatsby-starter-plugin/LICENSE +++ b/starters/gatsby-starter-plugin/LICENSE @@ -1,6 +1,6 @@ The BSD Zero Clause License (0BSD) -Copyright (c) 2020 Gatsby Inc. +Copyright (c) 2020 Netlify, Inc. Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted. diff --git a/starters/gatsby-starter-theme-workspace/LICENSE b/starters/gatsby-starter-theme-workspace/LICENSE index 7e964c1ee5f4f..740a168527525 100644 --- a/starters/gatsby-starter-theme-workspace/LICENSE +++ b/starters/gatsby-starter-theme-workspace/LICENSE @@ -1,6 +1,6 @@ The BSD Zero Clause License (0BSD) -Copyright (c) 2020 Gatsby Inc. +Copyright (c) 2020 Netlify, Inc. Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted. diff --git a/starters/gatsby-starter-wordpress-blog/LICENSE b/starters/gatsby-starter-wordpress-blog/LICENSE index 7e964c1ee5f4f..740a168527525 100644 --- a/starters/gatsby-starter-wordpress-blog/LICENSE +++ b/starters/gatsby-starter-wordpress-blog/LICENSE @@ -1,6 +1,6 @@ The BSD Zero Clause License (0BSD) -Copyright (c) 2020 Gatsby Inc. +Copyright (c) 2020 Netlify, Inc. Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted. diff --git a/starters/hello-world/LICENSE b/starters/hello-world/LICENSE index 7e964c1ee5f4f..740a168527525 100644 --- a/starters/hello-world/LICENSE +++ b/starters/hello-world/LICENSE @@ -1,6 +1,6 @@ The BSD Zero Clause License (0BSD) -Copyright (c) 2020 Gatsby Inc. +Copyright (c) 2020 Netlify, Inc. Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted.