Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/agneym/gatsby-blog-starter
A Gatsby Blog Starter with Styled Components
https://github.com/agneym/gatsby-blog-starter
gatsby gatsby-starter react styled-components
Last synced: about 2 months ago
JSON representation
A Gatsby Blog Starter with Styled Components
- Host: GitHub
- URL: https://github.com/agneym/gatsby-blog-starter
- Owner: agneym
- License: mit
- Created: 2018-12-25T17:01:37.000Z (almost 6 years ago)
- Default Branch: master
- Last Pushed: 2024-03-28T16:47:35.000Z (9 months ago)
- Last Synced: 2024-05-01T15:15:24.470Z (8 months ago)
- Topics: gatsby, gatsby-starter, react, styled-components
- Language: JavaScript
- Homepage: https://vigilant-leakey-a4f8cd.netlify.com/
- Size: 8.52 MB
- Stars: 19
- Watchers: 3
- Forks: 10
- Open Issues: 3
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
Minimalist Blog Starter
This project with `styled-components` shows off a minimalist blog layout.
**[See Live Demo](https://vigilant-leakey-a4f8cd.netlify.com/)**
## 🚀 Quick start
1. **Create a Gatsby site.**
Use the Gatsby CLI to create a new site, specifying the default starter.
```sh
# create a new Gatsby site using the default starter
npx gatsby new gatsby-blog https://github.com/BoyWithSilverWings/gatsby-blog-starter
```
1. **Start developing.**
Navigate into your new site’s directory and start it up.
```sh
cd gatsby-blog/
gatsby develop
```
1. **Open the source code and start editing!**
Your site is now running at `http://localhost:8000`!
\_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).\_
Open the `gatsby-blog` directory in your code editor of choice and edit `src/pages/index.js`. Save your changes and the browser will update in real time!
## 💫 Deploy
[](https://app.netlify.com/start/deploy?repository=https://github.com/BoyWithSilverWings/gatsby-blog-starter)
## Blogs using this theme:
- [Mindless](https://blog.agney.in)
- [Cheatsheet](http://blog.amaljose.com/)
- _Add yours here_
## 🧐 What's inside?
A quick look at the top-level files and directories you'll see in a Gatsby project.
.
├── node_modules
├── src
├── content
├── .gitignore
├── .prettierrc
├── gatsby-browser.js
├── gatsby-config.js
├── gatsby-node.js
├── gatsby-ssr.js
├── LICENSE
├── package-lock.json
├── package.json
└── README.md
1. **`/node_modules`**: This directory contains all of the modules of code that your project depends on (npm packages) are automatically installed.
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”.
3. **`src/content`**: Holds the markdown files for the blog
4. **`.gitignore`**: This file tells git which files it should not track / not maintain a version history for.
5. **`.prettierrc`**: This is a configuration file for [Prettier](https://prettier.io/). Prettier is a tool to help keep the formatting of your code consistent.
6. **`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.
7. **`gatsby-config.js`**: This is the main configuration file for a Gatsby site. This is where you can specify information about your site (metadata) like the site title and description, which Gatsby plugins you’d like to include, etc. (Check out the [config docs](https://www.gatsbyjs.org/docs/gatsby-config/) for more detail).
8. **`gatsby-node.js`**: This file is where Gatsby expects to find any usage of the [Gatsby Node APIs](https://www.gatsbyjs.org/docs/node-apis/) (if any). These allow customization/extension of default Gatsby settings affecting pieces of the site build process.
9. **`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.
10. **`LICENSE`**: Gatsby is licensed under the MIT license.
11. **`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).**
12. **`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.
13. **`README.md`**: A text file containing useful reference information about your project.
## 🎓 Learning Gatsby
Looking for more guidance? Full documentation for Gatsby lives [on the website](https://www.gatsbyjs.org/). Here are some places to start:
- **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.
- **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.
_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/)._