It’s common for brands to have catchy taglines. The former is from Apple. The latter was made famous by Google. At Automattic, our goal is to “democratize publishing.” We also have a creed that helps to guide our actions with some simple statements.
In a recent Tim Ferriss podcast with Tim O’Reilly, I was introduced to another slogan (for O’Reilly Media), “Create more value than you capture.” The slogan has stuck with me since I originally heard it on the podcast.
The real implications of “create more value than you capture” extends beyond a company slogan and can really be used as a guiding value in your personal and professional life. It can influence the choices you make, the projects you pursue, the recognition you strive for, and how you treat others.
We’re making progress! In the third part of this six part series, we started getting some content on the page by creating the header component that will sit at the top of our home page and single photo pages. Right now, if you change into your photo directory and run gatsby develop, you should see something like this:
In this fourth part, we’ll put together the grid layout for the homepage. Then, all we’ll have left to do is build the individual photo pages, add social tags, and deploy.
In Part 2 of this series, we mocked up the layout we’re looking to achieve and walked through how GatsbyJS handles data with GraphQL. We then practiced running a GraphQL query in the IDE to make sure data was returning.
In Part 3, we’re going to start building. We’ll put this thing together in three parts:
Header component present on all pages
Grid photo layout for the homepage
Individual photo layout for single pages
Let’s start working on the header component.
Oh – also, if you happen to be following along and building this thing while we go through it, would you mind tweeting me (@jeremeyd) and just showing off what you have so far? I’ve received a few DMs from folks, which is pretty awesome!
I’m in the process of creating an Instagram-esque clone using GatsbyJS and WordPress.com. We’re walking through the process in a series of steps.
Previously, we got the basics setup and installed some dependencies we’ll need later on. Today, we’re going to walk through the desired layout and talk a bit about how GatsbyJS handles data using GraphQL.
In a recent post, I talked about some recent experimentation I did with GatsbyJS and the WordPress.com API. While it wasn’t quite a fit for rebuilding my personal site, I wanted to build something else with it. So, I elected to build an Instagram-esque photo sharing site. I thought it might be helpful to share a bit of the process so I’ll be walking through the following steps:
If you’re not familiar with Gatsby, it bills itself as a “blazing-fast static site generator for React.” Having used React to work on Calypso and build some other small projects here and there, I figured it would be a pretty fun experiment.
Obviously, November has come and gone, and yet, you’re still seeing a traditional WordPress theme on my personal site. I ended up not launching my GatsbyJS site (although it is more or less built!) for a few reasons. I’ll touch on those reasons as well as my experience working with GatsbyJS.
Back in January of 2016, I wrote about how I was applying Cal Newport's concepts from Deep Work to my own routine. I still think it's the single best book on the market related to productivity and meaningful work.
Since that original post, I've made some tweaks here and there to how I plan and set out my day. Over the past few months in particular, I've felt pretty on top of things. I'm able to get in some solid coding time every day. I don't feel behind on anything work-related. I'm still able to find some time to read every day.
I've shared this updated system with a few folks, and they've found it helpful so I thought I would share it here.