gatsby-starter-yong

demo

🎉Feature

  • 🎁 MDX(Markdown for the component)
  • 💬 Comment(utterances)
  • ☕ Buy me a coffee
  • 🌙 Dark mode
  • 🎫 Series
  • # tags
  • 🔗 Title of Contents
  • 🎨 Featured Image

✨Demo

Demo Site

🚀 Quick start

  1. Create a Gatsby site.

    Use the Gatsby CLI to create a new site, specifying the blog starter.

    # create a new Gatsby site using the blog starter
    gatsby new my-blog-starter https://github.com/dayongbz/gatsby-starter-yong
  2. Start developing.

    Navigate into your new site’s directory and start it up.

    cd my-blog-starter/
    gatsby develop // Or npm run start
  3. 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.

    Open the my-blog-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!

⚙ Configure

  1. Change site meta data required
// gatsby-config.js
siteMetadata: {
  title: `site name`,
  author: {
    name: `author name`,
    summary: `for bio summary`,
  },
  description: `for seo meta tag(your blog description)`,
  siteUrl: `https://yourblog.com/`,
  social: {
    twitter: `twitter username`,
    facebook: `facebook username`,
    github: `github username`,
  },
  utterances: `github nickname/repo`,
  buyMeACoffee: `buy me a coffee id`,
}
  1. Run preload-fonts for preload fonts optional

Before building your application, you will need to generate a font asset map using the included gatsby-preload-fonts script.

// terminal tab 1
gatsby develop // Or npm run start
// terminal tab 2
npm run preload-fonts

You’ll need to run this script again after adding routes to your application (including new dynamic routes generated by source plugins), as well as any time you add new font assets or stylesheets that link to font assets.

This script outputs a file named font-preload-cache.json to the root of your project. You will want to check this file into your project’s source control so all contributors have the latest version of the cache.

If you don’t need this plugin, you can remove gatsby-plugin-preload-fonts in the gatsby-config.js.

gatsby-plugin-preload-fonts

🧐 What’s inside?

A quick look at the top-level files and directories you’ll see in a Gatsby project.

├── node_modules
├── src
├── .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. .gitignore: This file tells git which files it should not track / not maintain a version history for.
  4. .prettierrc: This is a configuration file for Prettier. Prettier is a tool to help keep the formatting of your code consistent.
  5. gatsby-browser.js: This file is where Gatsby expects to find any usage of the Gatsby browser APIs (if any). These allow customization/extension of default Gatsby settings affecting the browser.
  6. 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 for more detail).
  7. gatsby-node.js: This file is where Gatsby expects to find any usage of the Gatsby Node APIs (if any). These allow customization/extension of default Gatsby settings affecting pieces of the site build process.
  8. gatsby-ssr.js: This file is where Gatsby expects to find any usage of the Gatsby server-side rendering APIs (if any). These allow customization of default Gatsby settings affecting server-side rendering.
  9. LICENSE: This Gatsby starter is licensed under the 0BSD license. This means that you can see this file as a placeholder and replace it with your own license.
  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).
  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.
  12. 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. Here are some places to start:

  • For most developers, we recommend starting with our in-depth tutorial for creating a site with Gatsby. 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. In particular, check out the Guides, API Reference, and Advanced Tutorials sections in the sidebar.

💫 Deploy

Deploy to Netlify

Deploy with Vercel