Hello! I'm new to gatsby and I found this really nice starter theme for it. gatsby develop seems to be working fine. But when I use gatsby build I get the following error:

update:

I tried to build on ubuntu (the last one was on mac) and I got the following error:

⠂ run graphql queriesvips warning: VipsJpeg: error reading resolution
⢀ run graphql queriesvips warning: VipsJpeg: error reading resolution
vips warning: VipsJpeg: error reading resolution
⠠ run graphql queriesvips warning: VipsJpeg: error reading resolution
The GraphQL query from /home/wern/www/dev-box/public/me/wernancheta/src/templates/page-template.js failed

        Errors:
          GraphQLError: Unexpected token u in JSON at position 0
        Query:
          query PageBySlug(
  $slug: String!
) {
  site {
    siteMetadata {
      title
      subtitle
      copyright
      menu {
        label
        path
      }
      author {
        name
        email
        telegram
        twitter
        github
        rss
        vk
      }
    }
  }
  markdownRemark(fields: {slug: {eq: $slug}}) {
    id
    html
    frontmatter {
      title
      date
      description
    }
  }
}

(sharp:8384): GLib-CRITICAL **: g_hash_table_lookup: assertion 'hash_table != NULL' failed

(sharp:8384): GLib-CRITICAL **: g_hash_table_insert_internal: assertion 'hash_table != NULL' failed

(sharp:8384): GLib-CRITICAL **: g_hash_table_lookup: assertion 'hash_table != NULL' failed
Segmentation fault (core dumped)

Seems to be a problem with the graphql query. Any ideas?

Hello, huge thanks for this gatsby theme! Very inspiring :)

What do you say if use activeClassName (and onlyActiveOnIndex) in SiteNav component from react-router api?

https://github.com/ReactTraining/react-router/blob/6eeb7ad358f987520f5b519e48bdd31f725cbade/docs/API.md#link

A Small thought.

I wanted to express that when navigating between - Articles, About me & Contact me in mobile phones of medium sized screens, it is not easy for the visitor to realise that the selected section has been rendered below, upon selection, because the page is pretty much still and the only indication is the selected section being highlighted, i.e., it appears like in the picture below:

The visitor could miss scrolling to find out that the selected section has actually been rendered below.

Would auto-scroll to section title help?

Hi - new to Gatsby and trying to discern the authoring workflow - I checked the docs and have been customizing Lumen - I can't figure out how to author new posts/articles.

I tried following the existing pattern: creating a new directory within src/pages/articles for each new article that is written (containing a markdown file and referenced images) - but it doesn't seem to be rendered after restarting the gatsby develop.

Can you please describe how to author new articles/posts in lumen?

Hi. Most of these have to do with the cms. Not so much a concern for me as i will use another cms.
the gatsby ones are known and in a PR.

warning "netlify-cms > [email protected]" has unmet peer dependency "immutable@^3.7.6".
warning "netlify-cms > [email protected]" has unmet peer dependency "netlify-cms-lib-auth@^2.0.4".
warning "netlify-cms > [email protected]" has unmet peer dependency "netlify-cms-lib-util@^2.1.0".
warning "netlify-cms > [email protected]" has unmet peer dependency "netlify-cms-ui-default@^2.0.6".
warning "netlify-cms > [email protected]" has unmet peer dependency "prop-types@^15.6.2".
warning "netlify-cms > [email protected]" has unmet peer dependency "react-emotion@^9.2.6".
warning "netlify-cms > [email protected]" has unmet peer dependency "immutable@^3.7.6".
warning "netlify-cms > [email protected]" has unmet peer dependency "netlify-cms-lib-auth@^2.0.0".
warning "netlify-cms > [email protected]" has unmet peer dependency "netlify-cms-lib-util@^2.0.0".
warning "netlify-cms > [email protected]" has unmet peer dependency "netlify-cms-ui-default@^2.0.0".
warning "netlify-cms > [email protected]" has unmet peer dependency "prop-types@^15.6.2".
warning "netlify-cms > [email protected]" has unmet peer dependency "react-emotion@^9.2.6".
warning "netlify-cms > [email protected]" has unmet peer dependency "netlify-cms-lib-auth@^2.0.0".
warning "netlify-cms > [email protected]" has unmet peer dependency "netlify-cms-lib-util@^2.0.0".
warning "netlify-cms > [email protected]" has unmet peer dependency "netlify-cms-ui-default@^2.0.0".
warning "netlify-cms > [email protected]" has unmet peer dependency "prop-types@^15.6.2".
warning "netlify-cms > [email protected]" has unmet peer dependency "react-emotion@^9.2.6".
warning "netlify-cms > [email protected]" has unmet peer dependency "immutable@^3.7.6".
warning "netlify-cms > [email protected]" has unmet peer dependency "netlify-cms-lib-auth@^2.0.0".
warning "netlify-cms > [email protected]" has unmet peer dependency "netlify-cms-lib-util@^2.0.0".
warning "netlify-cms > [email protected]" has unmet peer dependency "netlify-cms-ui-default@^2.0.0".
warning "netlify-cms > [email protected]" has unmet peer dependency "prop-types@^15.6.2".
warning "netlify-cms > [email protected]" has unmet peer dependency "react-emotion@^9.2.6".
warning "netlify-cms > [email protected]" has unmet peer dependency "immutable@^3.8.2".
warning "netlify-cms > [email protected]" has unmet peer dependency "netlify-cms-lib-util@^2.0.0".
warning "netlify-cms > [email protected]" has unmet peer dependency "netlify-cms-ui-default@^2.0.0".
warning "netlify-cms > [email protected]" has unmet peer dependency "prop-types@^15.6.2".
warning "netlify-cms > [email protected]" has unmet peer dependency "react-emotion@^9.2.6".
warning "netlify-cms > [email protected]" has unmet peer dependency "react-immutable-proptypes@^2.1.0".
warning "netlify-cms > [email protected]" has unmet peer dependency "netlify-cms-lib-util@^2.0.4".
warning "netlify-cms > [email protected]" has unmet peer dependency "netlify-cms-ui-default@^2.0.0".
warning "netlify-cms > [email protected]" has unmet peer dependency "prop-types@^15.5.10".
warning "netlify-cms > [email protected]" has unmet peer dependency "react-immutable-proptypes@^2.1.0".
warning "netlify-cms > [email protected]" has unmet peer dependency "netlify-cms-ui-default@^2.0.0".
warning "netlify-cms > [email protected]" has unmet peer dependency "prop-types@^15.5.10".
warning "netlify-cms > [email protected]" has unmet peer dependency "react-emotion@^9.2.6".
warning "netlify-cms > [email protected]" has unmet peer dependency "immutable@^3.7.6".
warning "netlify-cms > [email protected]" has unmet peer dependency "netlify-cms-ui-default@^2.0.0".
warning "netlify-cms > [email protected]" has unmet peer dependency "prop-types@^15.5.10".
warning "netlify-cms > [email protected]" has unmet peer dependency "react-emotion@^9.2.6".
warning "netlify-cms > [email protected]" has unmet peer dependency "react-immutable-proptypes@^2.1.0".
warning "netlify-cms > [email protected]" has unmet peer dependency "immutable@^3.7.6".
warning "netlify-cms > [email protected]" has unmet peer dependency "netlify-cms-ui-default@^2.0.0".
warning "netlify-cms > [email protected]" has unmet peer dependency "prop-types@^15.5.10".
warning "netlify-cms > [email protected]" has unmet peer dependency "react-emotion@^9.2.6".
warning "netlify-cms > [email protected]" has unmet peer dependency "immutable@^3.7.6".
warning "netlify-cms > [email protected]" has unmet peer dependency "netlify-cms-ui-default@^2.0.0".
warning "netlify-cms > [email protected]" has unmet peer dependency "prop-types@^15.5.10".
warning "netlify-cms > [email protected]" has unmet peer dependency "react-emotion@^9.2.6".
warning "netlify-cms > [email protected]" has unmet peer dependency "react-immutable-proptypes@^2.1.0".
warning "netlify-cms > [email protected]" has unmet peer dependency "immutable@^3.7.6".
warning "netlify-cms > [email protected]" has unmet peer dependency "netlify-cms-ui-default@^2.0.0".
warning "netlify-cms > [email protected]" has unmet peer dependency "prop-types@^15.5.10".
warning "netlify-cms > [email protected]" has unmet peer dependency "react-emotion@^9.2.5".
warning "netlify-cms > [email protected]" has unmet peer dependency "react-immutable-proptypes@^2.1.0".
warning "netlify-cms > [email protected]" has unmet peer dependency "netlify-cms-ui-default@^2.0.0".
warning "netlify-cms > [email protected]" has unmet peer dependency "prop-types@^15.5.10".
warning "netlify-cms > [email protected]" has unmet peer dependency "immutable@^3.7.6".
warning "netlify-cms > [email protected]" has unmet peer dependency "netlify-cms-ui-default@^2.0.0".
warning "netlify-cms > [email protected]" has unmet peer dependency "prop-types@^15.5.10".
warning "netlify-cms > [email protected]" has unmet peer dependency "react-emotion@^9.2.6".
warning "netlify-cms > [email protected]" has unmet peer dependency "react-immutable-proptypes@^2.1.0".
warning "netlify-cms > [email protected]" has unmet peer dependency "immutable@^3.7.6".
warning "netlify-cms > [email protected]" has unmet peer dependency "netlify-cms-ui-default@^2.0.0".
warning "netlify-cms > [email protected]" has unmet peer dependency "prop-types@^15.5.10".
warning "netlify-cms > [email protected]" has unmet peer dependency "react-emotion@^9.2.5".
warning "netlify-cms > [email protected]" has unmet peer dependency "uuid@^3.1.0".
warning "netlify-cms > [email protected]" has unmet peer dependency "immutable@^3.7.6".
warning "netlify-cms > [email protected]" has unmet peer dependency "netlify-cms-ui-default@^2.0.0".
warning "netlify-cms > [email protected]" has unmet peer dependency "prop-types@^15.5.10".
warning "netlify-cms > [email protected]" has unmet peer dependency "react-immutable-proptypes@^2.1.0".
warning "netlify-cms > [email protected]" has unmet peer dependency "netlify-cms-ui-default@^2.0.0".
warning "netlify-cms > [email protected]" has unmet peer dependency "prop-types@^15.5.10".
warning "netlify-cms > [email protected]" has unmet peer dependency "netlify-cms-ui-default@^2.0.0".
warning "netlify-cms > [email protected]" has unmet peer dependency "prop-types@^15.5.10".
warning "netlify-cms > netlify-cms-widget-markdown > [email protected]" has unmet peer dependency "immutable@>=3.8.1".
warning "netlify-cms > netlify-cms-widget-markdown > [email protected]" has unmet peer dependency "immutable@^3.8.2".
warning "netlify-cms > netlify-cms-widget-markdown > [email protected]" has incorrect peer dependency "slate@^0.32.0".
warning "netlify-cms > netlify-cms-widget-markdown > [email protected]" has unmet peer dependency "immutable@^3.8.1".
warning "netlify-cms > netlify-cms-widget-markdown > [email protected]" has incorrect peer dependency "slate@^0.33.3".
warning "netlify-cms > netlify-cms-widget-markdown > [email protected]" has unmet peer dependency "slate-schema-violations@^0.1.7".
warning "netlify-cms > netlify-cms-widget-markdown > [email protected]" has unmet peer dependency "immutable@>=3.8.1".
warning "netlify-cms > netlify-cms-widget-markdown > [email protected]" has unmet peer dependency "immutable@>=3.8.1".
warning "netlify-cms > netlify-cms-core > redux-notifications > [email protected]" has incorrect peer dependency "redux@^2.0.0 || ^3.0.0".
warning "netlify-cms > netlify-cms-widget-markdown > slate-react > [email protected]" has unmet peer dependency "immutable@>=3.8.1".

warning "gatsby > [email protected]" has incorrect peer dependency "graphql@^0.12.0 || ^0.13.0".
warning "gatsby > [email protected]" has incorrect peer dependency "graphql@^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0".
warning "gatsby > [email protected]" has incorrect peer dependency "graphql@^0.13.0".
warning "gatsby-plugin-netlify > [email protected]" has unmet peer dependency "webpack@>=4.4.0".
warning "gatsby-plugin-sass > [email protected]" has unmet peer dependency "webpack@^3.0.0 || ^4.0.0".

It seems like there's a clash between the prettier and eslint settings.

For example, .prettierrc has:

  "trailingComma": "es5",

While .eslintrc has:

        "comma-dangle": ["error", "never"],

I'm not familiar enough with eslint to know how to quickly fix these issues. Maybe we need to drop the airbnb style guide as it doesn't play nicely with these prettier settings?

There have been updates to the gatsby monorepo:

• • The dependency gatsby-link was updated from 2.0.9 to 2.0.10.

• The dependency gatsby-plugin-catch-links was updated from 2.0.9 to 2.0.10.
• The dependency gatsby-plugin-feed was updated from 2.0.12 to 2.0.13.
• The dependency gatsby-plugin-google-analytics was updated from 2.0.12 to 2.0.13.
• The dependency gatsby-plugin-manifest was updated from 2.0.16 to 2.0.17.
• The dependency gatsby-plugin-netlify-cms was updated from 3.0.11 to 3.0.12.
• The dependency gatsby-plugin-netlify was updated from 2.0.7 to 2.0.8.
• The dependency gatsby-plugin-offline was updated from 2.0.21 to 2.0.22.
• The dependency gatsby-plugin-react-helmet was updated from 3.0.5 to 3.0.6.
• The dependency gatsby-plugin-sass was updated from 2.0.9 to 2.0.10.
• The dependency gatsby-plugin-sharp was updated from 2.0.19 to 2.0.20.
• The dependency gatsby-plugin-sitemap was updated from 2.0.4 to 2.0.5.
• The dependency gatsby-remark-copy-linked-files was updated from 2.0.8 to 2.0.9.
• The dependency gatsby-remark-images was updated from 3.0.2 to 3.0.3.
• The dependency gatsby-remark-prismjs was updated from 3.2.3 to 3.2.4.
• The dependency gatsby-remark-responsive-iframe was updated from 2.0.8 to 2.0.9.
• The dependency gatsby-remark-smartypants was updated from 2.0.7 to 2.0.8.
• The dependency gatsby-source-filesystem was updated from 2.0.19 to 2.0.20.
• The dependency gatsby-transformer-remark was updated from 2.2.3 to 2.2.4.
• The dependency gatsby-transformer-sharp was updated from 2.1.12 to 2.1.13.
• The dependency gatsby was updated from 2.0.113 to 2.0.114.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the gatsby group definition.

gatsby is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Hi,

Looking super good!!

FYI the README info shows a wrong / broken path to the star theme ( gatsby new Lumen https://github.com/gatsbylabs/gatsby-starter-lumen )

I think it should be https://github.com/hb-gatsby/gatsby-starter-lumen instead?

when I run gatsby build I get this output:

Generating CSS Warning: postcss-cssnext found a duplicate plugin ('autoprefixer') in your postcss plugins. This might be inefficient. You should remove 'autoprefixer' from your postcss plugin list since it's already included by postcss-cssnext. Note: If, for a really specific reason, postcss-cssnext warnings are irrelevant for your use case, and you really know what you are doing, you can disable this warnings by setting 'warnForDuplicates' option of postcss-cssnext to 'false'. Generating Static HTML Compiling production bundle.js Copying assets Done

a small tool for lumen to generate the directory structure of a post.
https://www.npmjs.com/package/gatsby-blog-post

.prettierrc has:

{
  "trailingComma": "es5",
  "semi": false,
  "singleQuote": true
}

But gatsby-node.js beings

const _ = require('lodash');
const Promise = require('bluebird');

Open to a PR which applies the prettier config to the whole codebase?

Can anyone provide details on adding additional logos for use in the Links component which is a child of the Sidebar component?

I can see that the links are assigned classes that exist in multiple Fontello related files. For example, a search for the icon-github class showed that it existed in five CSS and one HTML file.

Is there a way to add another logo? I am trying to add one for Medium.com

How do I activate Disqus. The props.url in <DisqiusThread/> comes back with the https://url/undefined when on a post. The 'path' for the post is undefined.

Thanks

Feature spec: Request to add SEO metadata to fill out Lumen features for a starter blog

Justification: Lumen theme already provides most blog requirements out of the box but does not support rich metadata for social sharing

Additional info: By example, @cherihung's current starter linked here currently implements this.

Hi, I'm currently exploring your nice Gatsby starter - thank you for providing this.

In the demo, I noticed that always the current date is displayed at the end of each article instead of the date specified in the front matter (e.g. today it says "Published 28 Sep 2016").

If I change post.datePublished to post.date the correct date values are shown (line 31 of index.jsx in SitePost component).

Another way to fix this could be to change the front matter variable of each post to datePublished (instead of date) and accordingly to adjust acces(page, 'data.datePublished') in SiteIndex class.

However, I am totally new to React and it is quite possible that I am missing something...

After initial clone and running Gatsby develop I get an error Cannot query field "allMarkdownRemark" on type "RootQueryType

I did get his this warning warning The gatsby-source-filesystem plugin has generated no Gatsby nodes. Do you need it? which may be where the error stems from.

Here is the full stack trace:

gatsby develop
success delete html and css files from previous builds — 0.010 s
success open and validate gatsby-config.js — 0.007 s
success copy gatsby files — 0.038 s
success onPreBootstrap — 0.950 s
warning The gatsby-source-filesystem plugin has generated no Gatsby nodes. Do you need it?
success source and transform nodes — 0.120 s
success building schema — 0.168 s
success createLayouts — 0.012 s
⠁ [ { GraphQLError: Cannot query field "allMarkdownRemark" on type "RootQueryType".
    at Object.Field (*/node_modules/graphql/validation/rules/FieldsOnCorrectType.js:65:31)
    at Object.enter (*/node_modules/graphql/language/visitor.js:295:29)
    at Object.enter (*/node_modules/graphql/language/visitor.js:337:25)
    at visit (*/node_modules/graphql/language/visitor.js:227:26)
    at visitUsingRules (*/node_modules/graphql/validation/validate.js:75:22)
    at validate (*/node_modules/graphql/validation/validate.js:60:10)
    at */node_modules/graphql/graphql.js:69:51
    at initializePromise (*/node_modules/es6-promise/dist/es6-promise.js:458:5)
    at new Promise (*/node_modules/es6-promise/dist/es6-promise.js:874:33)
    at graphqlImpl (*/node_modules/graphql/graphql.js:59:10)
    at graphql (*/node_modules/graphql/graphql.js:48:227)
    at graphqlRunner (*/node_modules/gatsby/dist/bootstrap/index.js:368:22)
    at Promise (*/gatsby-node.js:17:5)
    at Promise._execute (*/node_modules/bluebird/js/release/debuggability.js:303:9)
    at Promise._resolveFromExecutor (*/node_modules/bluebird/js/release/promise.js:483:18)
    at new Promise (*/node_modules/bluebird/js/release/promise.js:79:10)
    at Object.exports.createPages (*/gatsby-node.js:11:10)
    at runAPI (*/node_modules/gatsby/dist/utils/api-runner-node.js:110:36)
    at */node_modules/gatsby/dist/utils/api-runner-node.js:187:33
    at */node_modules/async/internal/map.js:27:9
    at replenish (*/node_modules/async/internal/eachOfLimit.js:64:17)
    at iterateeCallback (*/node_modules/async/internal/eachOfLimit.js:49:17)
    message: 'Cannot query field "allMarkdownRemark" on type "RootQueryType".',
    locations: [ [Object] ],
    path: undefined } ]
error gatsby-node.js returned an error

I am considering this starter project for rebuilding my blog. after I got this repo cloned and run the command yarn develop, something weird happened.

Current version of yarn is 1.0.1 and gatsby-cli is 1.1.6. (latest versions)
Please check this issue and it would be greatful if there is anything I can research for.

Hello, this project is awesome, but I wonder if sidenote can be supported, so the content can be more expressive.

I get this error when trying to import posts that I have from jekyll. According the Gatsby, this happens because not all the tags generated are arrays. Can you see what's up?

https://github.com/twhite96/TWBlog-newish

Nothing has changed but me adding posts.

System info:

  System:
    OS: macOS 10.14.1
    CPU: x64 Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz
    Shell: 5.3 - /bin/zsh
  Binaries:
    Node: 10.12.0 - ~/.nvm/versions/node/v10.12.0/bin/node
    Yarn: 1.10.1 - /usr/local/bin/yarn
    npm: 6.4.1 - ~/.nvm/versions/node/v10.12.0/bin/npm
  Browsers:
    Firefox: 62.0.3
    Safari: 12.0.1
  npmPackages:
    gatsby: ^1.9.164 => 1.9.279
    gatsby-link: ^1.6.34 => 1.6.46
    gatsby-plugin-catch-links: ^1.0.14 => 1.0.26
    gatsby-plugin-feed: ^1.3.15 => 1.3.25
    gatsby-plugin-google-analytics: ^1.0.15 => 1.0.31
    gatsby-plugin-google-fonts: latest => 0.0.4
    gatsby-plugin-offline: ^1.0.12 => 1.0.18
    gatsby-plugin-postcss-sass: ^1.0.15 => 1.0.22
    gatsby-plugin-react-helmet: ^2.0.3 => 2.0.11
    gatsby-plugin-sharp: ^1.6.25 => 1.6.48
    gatsby-plugin-sitemap: ^1.2.10 => 1.2.25
    gatsby-remark-copy-linked-files: ^1.5.25 => 1.5.37
    gatsby-remark-images: ^1.5.37 => 1.5.67
    gatsby-remark-prismjs: ^1.2.12 => 1.2.24
    gatsby-remark-responsive-iframe: ^1.4.16 => 1.4.20
    gatsby-remark-smartypants: ^1.4.10 => 1.4.12
    gatsby-source-filesystem: ^1.5.11 => 1.5.39
    gatsby-transformer-remark: ^1.7.28 => 1.7.44
    gatsby-transformer-sharp: ^1.6.16 => 1.6.27

Hey. First of all, thanks for the awesome theme. I ported your theme to Statinamic (another static site generator based on React and webpack).

Demo: https://khoanguyen.me/statinamic-theme-lumen/
Repo: https://github.com/thangngoc89/statinamic-theme-lumen

I tried to keep everything as close as possible with the original theme (along with best practice with React and Statinamic)

I'm struggling with adding a prev- and a next-link to my blogposts (like in the default blog starter). Has anyone achieved this? Or an idea how I can implement this?

This is the best starter for a blog, it would be great if it will be upgraded to work with 1.0.

Hiya~ I'm using your theme (gatsby-v2 branch) and there seems nothing for table css. Here's my opinion for css table style.

## _generic.scss

table {
    display: block;
    font-size: $typographic-small-font-size;
    line-height: $typographic-table-line-height;
    width: 100%;
    & tr {
        &:nth-child(even) {
            background-color: $color-table-tbody;
        }
    }
    & th {
        color: white;
        background-color: $color-table-thead;
        min-width: 80px;
    }
    & td {
        text-align: left;
        padding-left: 1rem;
    }
    & img {
        width: 15px;
        height: 15px;
    }
}

Hello,

In fact it is issue with used Roboto fonts i think. Just I'am posting here to warn you how special Polish chars looks ugly (both same on Chrome and Firefox).

Finally I've replaced it myself with "Open Sans"

Thank you for making this nice template.

I can change the color of the text in the variables.scss file but I am not sure how to change the background the page itself.

What is the process for deploying blog on a custom domain?

#gatsbyjs/gatsby#243

I was able to run the yarn run deploy script and push the public directory to the gh-pages branch.

Then I manually created a CNAMEfile with my custom domain.

The issue is every time I run the deploy script it removes the CNAME file.

Is there any way to prevent that?

Hello,
I am developing my own blog based on this theme. Thank you for your cool theme.
I found that links in 404 page are not working.

Steps

1. Move to non-exist page.
2. Click any link on that page (John Doe, Articles, About me, Contactt me)
3. Following error is occurred and the link is not working.

production-app.js:49 Uncaught TypeError: Cannot read property 'push' of undefined
    at eventHandler (production-app.js:49)
    at mitt.js:1
    at Array.map (<anonymous>)
    at Object.emit (mitt.js:1)
    at done (loader.js:284)
    at loader.js:302
    at loader.js:95
    at loader.js:78
    at index.json?832c:11
    at handler (patch.js:18)

Thank you

Thanks for this awesome project, could you please provide some quick hints to change the routing? For example, make 'about me' to be the homepage, whose path is '/'.
Thanks again!

When following the installation instructions I end up with a page without grid system.
Seems like the lost grid is not loaded/executed:

Links in SiteNav component are not working correctly without prefixLink at gh-pages hosted repositories

It is necessary to implement the functionality of switching between dark and light theme on macOS Mojave
Paul Miller - Using dark mode in CSS with MacOS Mojave

Hi,

I saw that you put the "photo.jpg" in your "pages" folder. I would like to link my resume (pdf file) from the "About me" page but it doesn't work. Any idea why ?
I tried to put all my static files in the static folder but it always redirect me on the 404 page.

I noticed there are eslint dependencies and a lint script in package.json, but no configuration file, therefore it doesn't work...

Do you mind me setting it up?
I really like the project and would love to see code style consistencies :)

Perhaps I'm missing something, but what is the preferred way to generate the posted date in the article header? Or is that something runs at deploy time.

When I created a project using the template, I got the following warnings in the console when I visited the main page.

Warning: Each child in an array or iterator should have a unique "key" prop. 
Check the render method of `SiteIndex`. 
See https://fb.me/react-warning-keys for more information.
    in div (created by SiteIndex)
    in SiteIndex (created by RouterContext)
    in div (created by Template)
    in Template (created by RouterContext)
    in RouterContext (created by Router)
    in ScrollBehaviorContext (created by Router)
    in Router

https://facebook.github.io/react/docs/lists-and-keys.html#keys

When I went to an article, I received this warning.

Warning: Failed prop type: The prop `post` is marked as required in `SitePost`, 
but its value is `undefined`.
    in SitePost (created by MarkdownWrapper)
    in MarkdownWrapper (created by RouterContext)
    in div (created by Template)
    in Template (created by RouterContext)
    in RouterContext (created by Router)
    in ScrollBehaviorContext (created by Router)
    in Router

post is on the route object at route.page.data and isn't passed into SitePost as an individual prop.

I plan to submit a pull request that would remove the warnings.

Summary

I noticed that anchor tags in posts had pretty much all styling stripped. I added the below styling to the anchors in posts so that they would become visible. Was this styling intentional? Seeing as the other links for the pages and read full posts are very obvious I assumed this was a bug.

For an example look at the wikipedia link on the demo site here.

If this isn't a bug, I apologize for creating more noise.

Potential Fix

.blog-single .text a:active, a:hover {
	outline: 0;
}
.blog-single .text a:active {
	color: #6a5dff;
}
.blog-single .text a:hover {
	border-bottom: 1px solid;
	color: #427ef7;
}

Example of Fix

Additional

Currently anchors also replace the current page because they don't use target='_blank'. If you would like it I can easily add this behavior to lumen so it happens automatically for links in posts.

I saw you included "react-google-analytic" in your npm dependencies but didn't use it.
Just finished implementing it at my clone of this repo.
Should I write a PR or do you have other plans?

Nice starter btw, I really like it!

Getting this :(

npm ERR! peerinvalid The package [email protected] does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer [email protected] wants eslint-plugin-jsx-a11y@^1.2.0

Ran into this issue while trying to install on Windows 10. The following command solved the issue:

npm install --global --production windows-build-tools

How would I go about creating a custom layout?

For example, I want to create a Resume page and use a custom layout SiteResume.

I tried reproducing the SitePage component to SiteResume but was unable to apply it to the Resume.md. It kept reverting to the SitePost layout.

Thanks for this awesome starter project. Keep up the good work.

I am new to Gatsby, so taking a hunch at this.

I could not get the profilePic to work without first removing prefixLink here.

So,

<img src={prefixLink(profilePic)} width='75' height='75' />
// becomes
<img src={profilePic} width='75' height='75' />

See Gatsby's config. It seems to be accounting for the prefixLink there.

I've got multiple posts but ReadNext is still not working. Any advice?

I realise it's a while away, but I've been working on a Gatsby v2 compatible version of this starter. You can check it out here:
https://github.com/GatsbyCentral/gatsby-starter-lumen/tree/gatsby-v2

I'm working on a site with 3.5k pages and so I need the json loader stuff that @pieh has been working on for v2. The branch might help if you come to update this starter for v2 at some point.

Hi, after running gatsby build, the port I was working on enters production mode. But even if I run gatsby develop again, the react tool icon still shows I'm in produciton env.

just tried on a fresh install. great starter though! :)

IndexPage -> Article something into
Error..

https://.disqus.com/embed.js net::ERR_NAME_NOT_RESOLVED

Previewing my site in dev, the posts and dates are in order. However, when I deploy to Netlify, the posts are out of order, refreshing the page puts them in a different order, and triggering a new deploy puts them in yet another order. I don't know if this is on Netlify or what, but my frontmatter is correct and folder structures are also correct.

Hi, I didn't find how to use disqus in the post page, can you help me please

I would like to add 'projects' folder inside pages thinking that I can add "Projects" as one of the lists in Sidebar. So I tried adding this new directory where articles is contained, but for the life of me, I can't figure out how I can accomplish it. I'm not sure if its doable or probably I should take a different approach.