Need help with gatsby-starter-julia?
Click the β€œchat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

160 Stars 38 Forks MIT License 57 Commits 0 Opened issues


A minimal GatsbyJS blog starter with landingpage, estimated reading time, markdown sourcing and much more.

Services available


Need anything else?

Contributors list

No Data


Gatsby Starter Julia

GatsbyJS is a free and open source static website builder build on React. It's one implementation of the JAMstack idea which creates high speed webpages.

πŸ“š Features:

  • Landingpage
  • Blog overview page
  • Markdown sourcing from /content folder
  • Estimated reading time for each post
  • Styled components with emotion
  • Netlify deployment friendly
  • Nunito font included as npm module
  • Syntax highlighting with prismjs
  • Textmarkerstyle headings inspired by Basecamp
  • Site meta tags with React Helmet
  • Plugins for offline support
  • Draft blog posts not published

πŸ‘¨πŸ»β€πŸ’» Customization

Create new pages like an About page in the

directory. The minimum code is:
import React from "react"

import Layout from "../components/layout" import SEO from "../components/seo"

const PageName = () => ( //CONTENT HERE )

export default PageName

To change the name on the landing page please modify the


The Nunito typeface is included as a npm module in

and in

This Gatsby starter is built on top of the official gatsby-starter-default. You can find a quick start guide in the following lines. There are the most important files explained.

πŸš€ Quick start

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.

  1. Create a Gatsby site.

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

    # create a new Gatsby site using the julia starter
    gatsby new julia-starter
  2. Start developing.

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

    cd julia-starter/
    gatsby develop
  3. Open the source code and start editing!

    Your site is now running at


    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

    directory in your code editor of choice and edit
    . Save your changes and the browser will update in real time!

🧐 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
  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.

    is a convention for β€œsource code”. A short description of what you can find there is below.πŸ‘¨πŸ»β€πŸ’»
  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. For example is the Nunito typeface imported here.

  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.

    : Gatsby is licensed under the MIT license.

  10. package-lock.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.

    : A text file containing useful reference information about your project.

The src directory

β”œβ”€β”€ components
β”œβ”€β”€ content
β”œβ”€β”€ images
β”œβ”€β”€ pages
└── templates
  1. /components
    : Your React components can be defined here. You can include them from there in your pages.

  2. /content
    : The filesystem plugin is configured to get the

    files from here. These will be published on the
  3. /images
    : This directory is the home for your images that you can query via GraphQL since the filesystem plugin publish them there.

  4. /pages
    : Here is where your pages like

    and also the 404 page lives. An example of the basic structure can be found above.
  5. /templates
    : You will find the

    template there which defines how every blog-post page is structured.

πŸŽ“ Learning Gatsby

Looking for more guidance? The perfect place to learn more about GatsbyJS is 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

You can also directly deploy this starter via Netlify.

Deploy to Netlify

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.