You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-**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.
76
73
74
+
-**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.
75
+
77
76
[**Learn how to use Gatsby for your next project.**](https://www.gatsbyjs.com/docs/)
78
77
79
78
## 🚀 Ship your first Gatsby site in 5 Minutes
@@ -88,36 +87,28 @@ At the end of this process, you'll have
88
87
2. a new repository that is linked to that new site
89
88
3. as you push changes to your new repository, Gatsby Cloud will automatically rebuild and redeploy your site!
90
89
91
-
## 💻 Get started with Gatsby _locally_ in 5 Minutes
90
+
## 💻 Get started with Gatsby locally in 5 Minutes
92
91
93
92
You can get a new Gatsby site up and running on your local dev environment in 5 minutes with these four steps:
94
93
95
-
1.**Install the Gatsby CLI.**
94
+
1.**Initialize a new project.**
96
95
97
96
```shell
98
-
npm install -g gatsby-cli
97
+
npm init gatsby
99
98
```
100
99
101
-
2.**Create a Gatsby site from a Gatsby starter.**
100
+
Give it the name "My Gatsby Site".
102
101
103
-
Get your Gatsby blog set up in a single command:
104
-
105
-
```shell
106
-
# Create a new Gatsby site using the interactive setup wizard
107
-
# Give it this name: My Gatsby site
108
-
gatsby new
109
-
```
110
-
111
-
3.**Start the site in `develop` mode.**
102
+
2.**Start the site in `develop` mode.**
112
103
113
104
Next, move into your new site’s directory and start it up:
114
105
115
106
```shell
116
107
cd my-gatsby-site/
117
-
gatsby develop
108
+
npm run develop
118
109
```
119
110
120
-
4.**Open the source code and start editing!**
111
+
3.**Open the source code and start editing!**
121
112
122
113
Your site is now running at `http://localhost:8000`. Open the `my-gatsby-site` directory in your code editor of choice and edit `src/pages/index.js`. Save your changes, and the browser will update in real time!
123
114
@@ -143,8 +134,9 @@ Also, read our [documentation on version support](https://www.gatsbyjs.com/docs/
143
134
144
135
## 💼 Migration Guides
145
136
146
-
Already have a Gatsby site? These handy guides will help you add the improvements of Gatsby v4 to your site without starting from scratch!
137
+
Already have a Gatsby site? These handy guides will help you add the improvements of Gatsby v5 to your site without starting from scratch!
147
138
139
+
-[Migrate from v4 to v5](https://www.gatsbyjs.com/docs/reference/release-notes/migrating-from-v4-to-v5/)
148
140
-[Migrate from v3 to v4](https://www.gatsbyjs.com/docs/reference/release-notes/migrating-from-v3-to-v4/)
149
141
-[Migrate from v2 to v3](https://www.gatsbyjs.com/docs/reference/release-notes/migrating-from-v2-to-v3/)
150
142
@@ -162,10 +154,6 @@ Check out our [**Contributing Guide**](https://www.gatsbyjs.com/contributing/how
162
154
163
155
This repository is a [monorepo](https://trunkbaseddevelopment.com/monorepos/) managed using [Lerna](https://github.com/lerna/lerna). This means there are [multiple packages](https://github.com/gatsbyjs/gatsby/tree/master/packages) managed in this codebase, even though we publish them to NPM as separate packages.
164
156
165
-
### Contributing to Gatsby v3
166
-
167
-
We are only accepting critical security patches for Gatsby v3.
-**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.
76
73
74
+
-**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.
75
+
77
76
[**Learn how to use Gatsby for your next project.**](https://www.gatsbyjs.com/docs/)
78
77
79
78
## 🚀 Ship your first Gatsby site in 5 Minutes
@@ -88,36 +87,28 @@ At the end of this process, you'll have
88
87
2. a new repository that is linked to that new site
89
88
3. as you push changes to your new repository, Gatsby Cloud will automatically rebuild and redeploy your site!
90
89
91
-
## 💻 Get started with Gatsby _locally_ in 5 Minutes
90
+
## 💻 Get started with Gatsby locally in 5 Minutes
92
91
93
92
You can get a new Gatsby site up and running on your local dev environment in 5 minutes with these four steps:
94
93
95
-
1.**Install the Gatsby CLI.**
94
+
1.**Initialize a new project.**
96
95
97
96
```shell
98
-
npm install -g gatsby-cli
97
+
npm init gatsby
99
98
```
100
99
101
-
2.**Create a Gatsby site from a Gatsby starter.**
102
-
103
-
Get your Gatsby blog set up in a single command:
104
-
105
-
```shell
106
-
# Create a new Gatsby site using the interactive setup wizard
107
-
# Give it this name: My Gatsby site
108
-
gatsby new
109
-
```
100
+
Give it the name "My Gatsby Site".
110
101
111
-
3.**Start the site in `develop` mode.**
102
+
2.**Start the site in `develop` mode.**
112
103
113
104
Next, move into your new site’s directory and start it up:
114
105
115
106
```shell
116
107
cd my-gatsby-site/
117
-
gatsby develop
108
+
npm run develop
118
109
```
119
110
120
-
4.**Open the source code and start editing!**
111
+
3.**Open the source code and start editing!**
121
112
122
113
Your site is now running at `http://localhost:8000`. Open the `my-gatsby-site` directory in your code editor of choice and edit `src/pages/index.js`. Save your changes, and the browser will update in real time!
123
114
@@ -139,10 +130,13 @@ We welcome suggestions for improving our docs. See the [“how to contribute”]
139
130
140
131
Wondering what we've shipped recently? Check out our [release notes](https://www.gatsbyjs.com/docs/reference/release-notes) for key highlights, performance improvements, new features, and notable bugfixes.
141
132
133
+
Also, read our [documentation on version support](https://www.gatsbyjs.com/docs/reference/release-notes/gatsby-version-support/) to understand our plans for each version of Gatsby.
134
+
142
135
## 💼 Migration Guides
143
136
144
-
Already have a Gatsby site? These handy guides will help you add the improvements of Gatsby v4 to your site without starting from scratch!
137
+
Already have a Gatsby site? These handy guides will help you add the improvements of Gatsby v5 to your site without starting from scratch!
145
138
139
+
-[Migrate from v4 to v5](https://www.gatsbyjs.com/docs/reference/release-notes/migrating-from-v4-to-v5/)
146
140
-[Migrate from v3 to v4](https://www.gatsbyjs.com/docs/reference/release-notes/migrating-from-v3-to-v4/)
147
141
-[Migrate from v2 to v3](https://www.gatsbyjs.com/docs/reference/release-notes/migrating-from-v2-to-v3/)
148
142
@@ -160,10 +154,6 @@ Check out our [**Contributing Guide**](https://www.gatsbyjs.com/contributing/how
160
154
161
155
This repository is a [monorepo](https://trunkbaseddevelopment.com/monorepos/) managed using [Lerna](https://github.com/lerna/lerna). This means there are [multiple packages](https://github.com/gatsbyjs/gatsby/tree/master/packages) managed in this codebase, even though we publish them to NPM as separate packages.
162
156
163
-
### Contributing to Gatsby v3
164
-
165
-
We are only accepting critical security patches for Gatsby v3.
0 commit comments