Mountain Starter Theme

Kick off your project with this Mountain Starter Theme 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.

Demo

Live Preview

WordPress MDX Plugin Theme

With this theme/plugin you can use WP, MDX or both 🤯

gatsby-theme-wordpress-mdx

🚀 Quick start

1. Create a Gatsby site.

   Use the Gatsby CLI to create a new site, specifying the hello-world starter.

   # create a new Gatsby site using the hello-world starter
   gatsby new my-mountain-starter https://github.com/artezan/gatsby-starter-mountain

2. Start developing.

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

   cd my-mountain-starter/
   yarn install
   gatsby develop

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-hello-world-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!

🧐 What's inside?

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

.
├── node_modules
├── src
    ├──images
    ├──page
    ├──posts
    ├──sections
    ├──index.mdx
    ├──gatsby-plugin-theme-ui
├── .gitignore
├── .prettierrc
├── gatsby-config.js
├── LICENSE
├── package-lock.json
├── package.json
└── README.md

1. /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”.

   1. /page All the page in the Side and Nav bar
   2. /posts All the posts for mdx
   3. /sections Sections on landing page
   4. /index.mdx in this file you can generate the landing page

2. .gitignore: This file tells git which files it should not track / not maintain a version history for.

3. .prettierrc: This is a configuration file for Prettier. Prettier is a tool to help keep the formatting of your code consistent.t Gatsby settings affecting the browser.

4. 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).

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

6. LICENSE: Gatsby is licensed under the MIT license.

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

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

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

💫 Deploy