Source for the Ocular-Rhythm website
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.

Ocular-Rhythm Site

Netlify Status

The source code to my personal website and blog, Ocular-Rhythm. I built this using Gatsby, which is a rad JavaScript framework. I also used Netlify for the first time with this project and am extremely impressed with it.

All code can be found in the src directory. Inside that directory, the structure is broken down into several sub-directories:

Directory Purpose
Components This is where all of the React components are situated. Each component has its' own sub-directory that contains an index.js file and its' css module.
Global I put global CSS styles in here
Images Static images
Pages Pages that also are named routes
Posts The blog posts in markdown form
Templates Blog post and category templates
Utils Utility functions

Getting Started

It's preferred to use npm because I was running into an issue with yarn that was causing the Netlify deployment to fail. The issue stems from the use of gatsby-plugin-sharp and I was unable to actually figure out the root cause. It seems that when using yarn to install that package, it fails to resolve some symbols used by the package. Using npm negates this issue. As I personally prefer yarn, this is something I'll need to revisit. In the meantime, use...

npm install
npm develop

Netlify Configuration

In the static directory there is a file called _headers. This file is responsible for telling Netlify on how to handle my custom domains. This file gets copied to public when the site is built.


Getting up and running in Gatsby is fairly straightforward. Writing components in React and piecing those together is also nothing new. The biggest hurdle I had to tackle was figuring out how to structure my pages/posts in a way that reflects the URL structure I was looking for. After a while a tinkering and trial and error, I found the sweet spot.


I've seen often where people praise Gatsby for their clear and helpful documentation, but I will say that for someone with 4 or 5 years of JavaScript experience and using a ton of different frameworks, I still found myself confused and frustrated at certain points.

I believe Gatsby will continue to improve and evolve so I am confident it will only get better from here.


I ran into an issue with Prism that made displaying code blocks kind of challenging. The problem I encountered was that I wanted to be able to use markdown to write my posts while also having the flexibility to displaying the language of a code block, along with a copy code button. I was hopeful that I could use the Github flavor of code blocks in markdown as well instead of having to write HTML in my markdown.

Exacerbating the issue was the fact that my code blocks were styled differently than the content around it on the page. My code blocks are 100% width of the viewport, while the remaining content in posts are limited to a max width of 666 pixels. This meant I needed to close off the wrapping div before injecting my code block HTML, finally re-opening the wrapping div.

After hours (or maybe days, I don't remember) of attempting different solutions, the ultimate winner was a regex that parses the HTML output by the Gatsby markdown plugin and replaces any code block with the appropriate structure.

const REGEXP = new RegExp('<div class="gatsby-highlight" data-language="([a-z]*)?">(\t|\r|\n|.)*?<\/div>', 'g');
html += content.html.replace(REGEXP,
    `</div><div class="${ style.block }"><div class="${ style.heading }">` +
    `<p class="${ style.language }">$1</p></div>` +
    `<div class="${ style.wrapper } gatsby-highlight">$&</div></div><div class="${ style.copy }">`