diff --git a/docs/blog/2019-01-31-using-react-context-api-with-gatsby/index.md b/docs/blog/2019-01-31-using-react-context-api-with-gatsby/index.md
new file mode 100644
index 0000000000000..17d8ab69e31cb
--- /dev/null
+++ b/docs/blog/2019-01-31-using-react-context-api-with-gatsby/index.md
@@ -0,0 +1,284 @@
+---
+title: Using React Context API with Gatsby
+author: Muhammad Muhsin
+date: 2019-01-31
+tags:
+ - "React"
+---
+
+You often feel the unsettling flash of a bright phone screen while relaxing in a dimly lit room. This is alleviated by introducing a "dark mode" which switches background and foreground colors to reduce eye strain. I decided to add this to my boutique web agency [Laccadive IO's](https://laccadive.io/) new Gatsby-based site.
+
+
+One of the few types of alternative theme that adds real value to users is a low light intensity “night mode” theme. Not only is it easier on the eyes when reading in the dark, but it also reduces the likelihood of migraine and the irritation of other light sensitivity disorders. As a migraine sufferer, I’m interested!
+
+
+In considering the different ways to implement this a natural fit become apparent: React’s new Context API. Having worked with Context API before, this seemed like a particularly well suited use for this API. However, I soon realized I would need to do a little set-up work to get this up and running.
+
+After a brief search, I came across just what I was looking for, the Gatsby Browser APIs. Specifically, the [`wrapRootElement`](https://www.gatsbyjs.org/docs/browser-apis/#wrapRootElement) API was a perfect fit for this use case. This API allows you to wrap your root element with a wrapping component, e.g. a `Provider` from Redux or... a ThemeProvider from React Context. Using this, I managed to achieve dark mode for my use case.
+
+Let's do a deep dive into how this feature was actually implemented step by step using React Context, Gatsby, and a Theme Provider to implement a dark mode UI!
+
+## Creating the Context file in a new Gatsby project
+
+First of all, you have to initialize a Gatsby project and start it in develop mode.
+
+1. npx gatsby new gatsby-dark-mode
+1. cd gatsby-dark-mode
+1. npm start
+
+Then, create a `context` folder within src and the `ThemeContext.js` file within it.
+
+```js:title=src/contex/ThemeContext.js
+import React from "react"
+
+const defaultState = {
+ dark: false,
+ toggleDark: () => {},
+}
+
+const ThemeContext = React.createContext(defaultState)
+
+export default ThemeContext
+```
+
+[`React.createContext`](https://reactjs.org/docs/context.html#reactcreatecontext) is a new function in React 16.3 and allows you to create a Context object. It accepts a default state, the value which will be used when a component does not have a matching Provider above it in the tree. The function returns an object with Provider and Consumer properties which we will be using later.
+
+## Modifying the Gatsby Browser file
+
+Next, write the following code within the `gatsby-browser.js` file, which is in the root folder in a Gatsby project:
+
+```jsx:title=gatsby-browser.js
+import React from "react"
+
+import ThemeContext from "./src/context/ThemeContext"
+
+// Getting dark mode information from OS!
+// You need macOS Mojave + Safari Technology Preview Release 68 to test this currently.
+const supportsDarkMode = () =>
+ window.matchMedia("(prefers-color-scheme: dark)").matches === true
+
+class ThemeProvider extends React.Component {
+ state = {
+ dark: false,
+ }
+
+ toggleDark = () => {
+ let dark = !this.state.dark
+ localStorage.setItem("dark", JSON.stringify(dark))
+ this.setState({ dark })
+ }
+
+ componentDidMount() {
+ // Getting dark mode value from localStorage!
+ const lsDark = JSON.parse(localStorage.getItem("dark"))
+ if (lsDark) {
+ this.setState({ dark: lsDark })
+ } else if (supportsDarkMode()) {
+ this.setState({ dark: true })
+ }
+ }
+
+ render() {
+ const { children } = this.props
+ const { dark } = this.state
+ return (
+
+ {children}
+
+ )
+ }
+}
+{
+ /* highlight-start */
+}
+export const wrapRootElement = ({ element }) => (
+ {element}
+)
+{
+ /* highlight-end */
+}
+```
+
+Create the `ThemeProvider` component which wraps its children with `ThemeContext.Provider`. This component then wraps the root element and is exported as `wrapRootElement`. This API is then invoked appropriately by the Gatsby API runner.
+
+The `toggleDark` function gets the current `state.dark` value and switches the value to the opposite. It then stores the new value in `localStorage` before setting it back to state using the `setState` function, so that it persists over page refreshes. The dark value from `state` and the `togglDark` function are passed to the Provider.
+
+## Editing the Layout file
+
+The default `layout.js` uses a `` and renderProp to render the layout, which is wrapped by a Fragment `<>`. Modify it to look like this:
+
+```jsx:title=src/components/layout.js
+import React from 'react'
+import PropTypes from 'prop-types'
+import { StaticQuery, graphql } from 'gatsby'
+
+import ThemeContext from '../context/ThemeContext'
+import Header from './header'
+import './layout.css'
+
+const Layout = ({ children }) => (
+ (
+ {/* highlight-start */}
+
+ {theme => (
+
+ {/* highlight-end */}
+
+
+ {children}
+
+
+
+ )}
+
+ )}
+ />
+)
+
+Layout.propTypes = {
+ children: PropTypes.node.isRequired,
+}
+
+export default Layout
+```
+
+The class of the wrapper div will change based on the context value of the dark variable, which we set as state in the `ThemeContext.js` file.
+
+## Adding the switch in the Header
+
+With this configuration completed, we can now add the actual switch to toggle dark mode. Modify the `header.js` component, like so:
+
+```jsx:title=src/components/header.js
+import { Link } from "gatsby"
+import PropTypes from "prop-types"
+import React from "react"
+
+import ThemeContext from "../context/ThemeContext"
+
+const Header = ({ siteTitle }) => (
+
+ {theme => (
+
+
+
+
+ {siteTitle}
+
+
+
+
+
+ )}
+
+)
+
+Header.propTypes = {
+ siteTitle: PropTypes.string,
+}
+
+Header.defaultProps = {
+ siteTitle: ``,
+}
+
+export default Header
+```
+
+## Adding styles
+
+At this point, we've set up a dark mode toggle and conditionally render a `className` if dark mode is enabled. However, we still need to actually _style_ based upon this conditional `className`. As such, we need to add the following styles in the `layout.css` file:
+
+```css:title=src/components/layout.css
+/* Dark mode styles */
+.dark-switcher {
+ color: #fff;
+ margin-top: 5px;
+ background: transparent;
+ border: none;
+ cursor: pointer;
+}
+
+@media (min-width: 992px) {
+ .dark-switcher {
+ position: absolute;
+ right: 15px;
+ top: 10px;
+ }
+}
+
+.dark {
+ background-color: #2a2b2d;
+ color: #fff;
+ transition: all 0.6s ease;
+}
+
+.light {
+ transition: all 0.6s ease;
+ background-color: #fefefe;
+}
+
+.dark a,
+.dark a:visited {
+ color: #fff;
+}
+```
+
+## Conclusion
+
+In just a few, simple steps we've enabled a conditional dark mode that our users will certainly appreciate. We've leveraged APIs like `Context` in React, as well as internal Gatsby APIs to wrap our code with a provider. Now if you visit `http://localhost:8000/` you can see all of our work pay off!
+
+We covered the following in today’s article:
+
+- Introduction to dark mode in web development
+- Initializing a Gatsby project
+- Initializing the context object with `createContext`
+- Using the Gatsby Browser API and returning `wrapRootElement` from `gatsby-browser.js`
+- Wrapping the JSX within `layout.js` with a Context Consumer and a div with class referring to the dark mode state
+- Adding the switch inside the header
+- Adding the styles relevant to the Dark mode
+
+Interested in seeing this in action? Head over to https://github.com/m-muhsin/gatsby-dark-mode and clone or fork my project.
diff --git a/docs/blog/author.yaml b/docs/blog/author.yaml
index 1b8d49234f784..ed658e57ad529 100644
--- a/docs/blog/author.yaml
+++ b/docs/blog/author.yaml
@@ -204,6 +204,10 @@
bio: Infinite Builder working on DX @ Netlify. Helping people Learn In Public at /r/reactjs
avatar: avatars/swyx.jpg
twitter: "@swyx"
+- id: Muhammad Muhsin
+ bio: Co-founder & Lead Developer at Laccadive IO. Author at Smashing Magazine.
+ avatar: avatars/muhammad-muhsin.jpg
+ twitter: "@muhsinlk"
- id: Ondrej Polesny
bio: Full-stack developer, speaker and trainer with passion for anything new and intriguing. Opensource contributor. Dev evangelist @ Kentico Cloud.
avatar: avatars/ondrej-polesny.jpg
diff --git a/docs/blog/avatars/muhammad-muhsin.jpg b/docs/blog/avatars/muhammad-muhsin.jpg
new file mode 100644
index 0000000000000..8840868b19f47
Binary files /dev/null and b/docs/blog/avatars/muhammad-muhsin.jpg differ