Skip to content

Commit 2eda97e

Browse files
tyankatsu0105wardpeet
authored andcommitted
docs(creating-a-starter) Add site-name before starter-url (#17467)
1 parent 24805dc commit 2eda97e

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/docs/creating-a-starter.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -27,13 +27,13 @@ Let's expand upon these items to prepare you for creating a winning starter.
2727

2828
## Open source and available from a stable URL
2929

30-
The Gatsby CLI allows users to install a new site with a starter using the command `gatsby new <starter-url>`. For this to work, your starter needs to be available to download. The easiest way to accomplish this is to host your starter on GitHub or GitLab and use the publicly available repo URL, such as:
30+
The Gatsby CLI allows users to install a new site with a starter using the command `gatsby new <site-name> <starter-url>`. For this to work, your starter needs to be available to download. The easiest way to accomplish this is to host your starter on GitHub or GitLab and use the publicly available repo URL, such as:
3131

32-
`gatsby new https://github.com/gatsbyjs/gatsby-starter-blog`
32+
`gatsby new my-app https://github.com/gatsbyjs/gatsby-starter-blog`
3333

3434
Although the official starters live in the Gatsby repo, community members can offer their own starters from their own repos. Here's an example of installing a community starter:
3535

36-
`gatsby new https://github.com/netlify-templates/gatsby-starter-netlify-cms`
36+
`gatsby new my-app https://github.com/netlify-templates/gatsby-starter-netlify-cms`
3737

3838
## Configurable
3939

0 commit comments

Comments
 (0)