Skip to content


Switch branches/tags

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

Personal Website and Blog

Built with GatsbyJS based on the Julia starter.

📚 Features:

  • Landingpage
  • Blog overview page
  • Markdown sourcing from /content folder
  • 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

👨🏻‍💻 Customization

Create new pages like an About page in the /pages directory. The minimum code is:

import React from "react"

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

const PageName = () => (
    <SEO title="PageName" keywords={[`gatsby`, `application`, `react`]} />

export default PageName

To change the name on the landing page please modify the title in gatsby-config.js

The Nunito typeface is included as a npm module in gatsby-browser.js and in /components/layout.css

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. Start developing.

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

    cd lev-izraelit
    gatsby develop
  2. 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 lev-izraelit directory in your code editor of choice and edit src/pages/index.js or src/pages/blog.js. 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
├── 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. src 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.

  9. LICENSE: Gatsby is licensed under the MIT 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. 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 *.md files from here. These will be published on the /blog page.

  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 /blog, /about and also the 404 page lives. An example of the basic structure can be found above.

  5. /templates: You will find the blog-post.js template there which defines how every blog-post page is structured.


Personal website and blog







No releases published


No packages published