The intro blog post on the gatsbyjs blog is

:: https://www.gatsbyjs.org/blog/2018-11-11-introducing-gatsby-themes/

The example repo that will update as new theme functionality is merged is

:: https://github.com/ChristopherBiscardi/gatsby-theme-examples

I'm talking about themes at Gatsby Days which you can get a ticket for here

:: https://www.eventbrite.com/e/gatsby-days-tickets-51837151315

You can either file issues on the example repo or start new discussions here to participate in the evolution of theming :)

I love where this is going. btw.

Thank you for the community :)

(Found from https://www.reactiflux.com/transcripts/gatsby-team/)

Really excited to start hacking around on the example theme! This is such a cool addition to Gatsby!

Hi, I tried following the steps in the blog post to enable themes but I get this error: error It looks like you were trying to add the config file? Please rename "gatsby-config.js" to "gatsby-config"

@jmnoz Happy to help, can you file an issue at https://github.com/ChristopherBiscardi/gatsby-theme-examples?

I have a question -- will it be possible to share configuration like linting, or TS with Gatsby themes?

you can definitely put TS config in a theme (anything you can put in a gatsby-config works).

Going to be converting a starter into a theme + npm package this weekend, wish me luck!

Good luck, and please share your results. Lots of people (me included) will learn from your example.

I'll post more details after my traveling this weekend! Usage instructions are in both repos however and the code is there for reference

@[talves] I just cloned and ran that repo successully

Just read about themes. This makes sense. Always heard people whining about Gatsby bcz of the same reason. Finally it will be solved :)

Gatsby themes are looking pretty great. Thanks Chris and everyone working on this. 💯

Hi, how do I access options in the user's gatsby-config.js in my theme's components? The docs (https://www.gatsbyjs.org/docs/themes/api-reference/#configuration) only mention being able to access the options in gatsby-node.js. Is this possible or do I need to figure out a workaround using component shadowing?

You can export a function in gatsby-config.js and the first argument it will receive is the options passed in by the end user. Here's an example: https://github.com/gatsbyjs/gatsby/blob/8f4408606a20e355ea29e8982abd62198a901592/themes/gatsby-theme-blog/gatsby-config.js#L1