Note: This repo is based upon the
Netlify CMS and Gatsby Starter.
Do you have suggestions or feedback? Open an issue
- 🕶 Gatsby v2 for Static page generation
- 🤘 gatsby-plugin-purgecss for Stylesheet overhead reduction
- 📷UploadCare Integration for image uploading via cms
- 🍌 Bulma CSS baseline && Bulma builds are usually ~170K but reduced 90% by purgecss..
- 👌Page Transitions and avatar animation with react-spring
-
One may observe that much of the site data is pulled from these directories When using the Netlify CMS admin panel to creating postings, the postings made are contained within these folders.
The.mdfiles are parsed (corresponding to the config.yml) for data and stored within GraphQL. This data is then queried within the our template files One should note that Gatsby translates all of the contents within this directory into pages. For instance, if we deploy and visithttps://www.website.com/contact/thankswe will receiveTL;DR pages/ contains the data to be displayed by templates/ -
The CMS will use this configuration to parse the
.mdfiles. configure/declare the interchangeable data within each page. This is core in creating re-usable page templates within Netlify CMS Collection Types
Configuration Options > Add to your site -
at the bottom of each template, you will see that we are creating a graphql query to retrieve the previously parsed data. Within these files we are defining how we display the pages.
-
A key step in templating your pages is to register them Once this is completed, they should be available in the admin panel.
- Node (I recommend using v8.2.0 or higher)
- Gatsby CLI
$ git clone https://github.com/[GITHUB_USERNAME]/[REPO_NAME].git
$ cd [REPO_NAME]
$ yarn
$ npm run develop
To test the CMS locally, you'll need run a production build of the site:
$ npm run build
$ npm run serve
Follow the Netlify CMS Quick Start Guide to set up authentication, and hosting.