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
{{ message }}
This repository was archived by the owner on Nov 8, 2024. It is now read-only.
Kick off your project with this default boilerplate. This starter ships with the main Gatsby configuration files you might need to get up and running blazing fast with the blazing fast app generator for React.
3
+
## Running the app locally
4
+
Navigate into your new site’s directory and start it up.
12
5
13
-
_Have another more specific idea? You may want to check out our vibrant collection of [official and community-created starters](https://www.gatsbyjs.org/docs/gatsby-starters/)._
14
-
15
-
## 🚀 Quick start
16
-
17
-
1.**Create a Gatsby site.**
18
-
19
-
Use the Gatsby CLI to create a new site, specifying the default starter.
20
-
21
-
```shell
22
-
# create a new Gatsby site using the default starter
23
-
gatsby new my-default-starter https://github.com/gatsbyjs/gatsby-starter-default
24
-
```
25
-
26
-
1. **Start developing.**
27
-
28
-
Navigate into your new site’s directory and start it up.
29
-
30
-
```shell
31
-
cd my-default-starter/
6
+
```shell
7
+
cd website
32
8
gatsby develop
33
9
```
34
10
@@ -38,33 +14,16 @@ _Have another more specific idea? You may want to check out our vibrant collecti
38
14
39
15
_Note: You'll also see a second link: _`http://localhost:8000/___graphql`_. This is a tool you can use to experiment with querying your data. Learn more about using this tool in the [Gatsby tutorial](https://www.gatsbyjs.org/tutorial/part-five/#introducing-graphiql)._
40
16
41
-
Open the `my-default-starter` directory in your code editor of choice and edit `src/pages/index.js`. Save your changes and the browser will update in real time!
42
-
43
-
## 🧐 What's inside?
44
-
45
-
A quick look at the top-level files and directories you'll see in a Gatsby project.
17
+
Update file and watch the browser update in real time!
46
18
47
-
.
48
-
├── node_modules
49
-
├── src
50
-
├── .gitignore
51
-
├── .prettierrc
52
-
├── gatsby-browser.js
53
-
├── gatsby-config.js
54
-
├── gatsby-node.js
55
-
├── gatsby-ssr.js
56
-
├── LICENSE
57
-
├── package-lock.json
58
-
├── package.json
59
-
└── README.md
19
+
2. See `index.html` in `/docs` for further info
60
20
61
-
1. **`/node_modules`**: This directory contains all of the modules of code that your project depends on (npm packages) are automatically installed.
21
+
## Deployment
22
+
See [Gatsby's Guide to Deploying to Firebase](https://www.gatsbyjs.org/docs/deploying-to-firebase)
62
23
63
-
2. **`/src`**: This directory will contain all of the code related to what you will see on the front-end of your site (what you see in the browser) such as your site header or a page template. `src` is a convention for “source code”.
24
+
https://website-888.web.app/about
64
25
65
-
3. **`.gitignore`**: This file tells git which files it should not track / not maintain a version history for.
66
-
67
-
4. **`.prettierrc`**: This is a configuration file for [Prettier](https://prettier.io/). Prettier is a tool to help keep the formatting of your code consistent.
26
+
## Config info
68
27
69
28
5.**`gatsby-browser.js`**: This file is where Gatsby expects to find any usage of the [Gatsby browser APIs](https://www.gatsbyjs.org/docs/browser-apis/) (if any). These allow customization/extension of default Gatsby settings affecting the browser.
70
29
@@ -74,24 +33,7 @@ A quick look at the top-level files and directories you'll see in a Gatsby proje
74
33
75
34
8.**`gatsby-ssr.js`**: This file is where Gatsby expects to find any usage of the [Gatsby server-side rendering APIs](https://www.gatsbyjs.org/docs/ssr-apis/) (if any). These allow customization of default Gatsby settings affecting server-side rendering.
76
35
77
-
9. **`LICENSE`**: Gatsby is licensed under the MIT license.
78
-
79
-
10. **`package-lock.json`** (See `package.json` below, first). This is an automatically generated file based on the exact versions of your npm dependencies that were installed for your project. **(You won’t change this file directly).**
80
-
81
-
11. **`package.json`**: A manifest file for Node.js projects, which includes things like metadata (the project’s name, author, etc). This manifest is how npm knows which packages to install for your project.
82
-
83
-
12. **`README.md`**: A text file containing useful reference information about your project.
84
-
85
-
## 🎓 Learning Gatsby
86
-
87
-
Looking for more guidance? Full documentation for Gatsby lives [on the website](https://www.gatsbyjs.org/). Here are some places to start:
88
-
89
-
- **For most developers, we recommend starting with our [in-depth tutorial for creating a site with Gatsby](https://www.gatsbyjs.org/tutorial/).** It starts with zero assumptions about your level of ability and walks through every step of the process.
90
-
91
-
- **To dive straight into code samples, head [to our documentation](https://www.gatsbyjs.org/docs/).** In particular, check out the _Guides_, _API Reference_, and _Advanced Tutorials_ sections in the sidebar.
92
-
93
-
## 💫 Deploy
94
-
95
-
[](https://app.netlify.com/start/deploy?repository=https://github.com/gatsbyjs/gatsby-starter-default)
96
36
97
-
<!-- AUTO-GENERATED-CONTENT:END -->
37
+
# Resources
38
+
Original template: [Fatima, Themeforest](https://themeforest.net/item/fatima-creative-react-gatsby-blog-template/26418684)
39
+
See `/template` for compressed version of original source
0 commit comments