deployments: https://zeit.co/suddjian/suddjian-blog

This project uses gatsby.

You may want to check out Gatsby's vibrant collection of official and community-created starters.

💡 Blog Post Ideas

• Philosophy of AI and hyper-intelligence: We're bringing forth our own decline as a species and maybe we should just accept that the greatest destiny we could hope for is to create something greater than ourselves.

• Cloud software and the death of the charming bug

• Toxic Positivity

• How to write good pull requests

• Started working at Preset

• Cryptographic secret recovery via partially trusted parties

• A short story narrating a creature transporting its young to a safe - but barren - place, then sacrificing itself as food for them

• That shadertoy ripple effect that I made

• Artisanal Engineer Hiring

• Software as an artistic medium (and how to realize art at work)

• Every moment is a choice

• The old Japanese bedridden lady

• It's easier to work with it than against it

• Automating Dotfiles

• eventually.run

• Menlo Park's shitty overnight parking rules

• We are just animals that can communicate

• Filling the void of community as an atheist

• I don't believe in deleting information

• Every story is the author

• The almost perverse devotion I often have to programming, often driven by reading the tech legends

• The benefits of indulging heartily in nerdiness

• Working on open-source for free is usually not the best way to spend your time

• "Should" is poison

🚀 Quick start

Navigate into the site’s directory and start it up.

gatsby develop

Your site is now running at http://localhost:8000!

Note: You'll also see a second link: http://localhost:8000/___graphql. This is a tool you can use to experiment with querying your data. Learn more about using this tool in the Gatsby tutorial.

Open the awesome-blog directory in your code editor of choice and edit src/pages/index.js. Save your changes and the browser will update in real time!

🧐 What's inside?

A quick look at the top-level files and directories you'll see in a Gatsby project.

.
├── node_modules
├── src
├── .gitignore
├── .prettierrc
├── gatsby-browser.js
├── gatsby-config.js
├── gatsby-node.js
├── gatsby-ssr.js
├── LICENSE
├── package-lock.json
├── package.json
└── README.md

1. /node_modules: This directory contains all of the modules of code that your project depends on (npm packages) are automatically installed.

2. /src: This directory will contain all of the code related to what you will see on the front-end of your site (what you see in the browser) such as your site header or a page template. src is a convention for “source code”.

3. .gitignore: This file tells git which files it should not track / not maintain a version history for.

4. .prettierrc: This is a configuration file for Prettier. Prettier is a tool to help keep the formatting of your code consistent.

5. gatsby-browser.js: This file is where Gatsby expects to find any usage of the Gatsby browser APIs (if any). These allow customization/extension of default Gatsby settings affecting the browser.

6. gatsby-config.js: This is the main configuration file for a Gatsby site. This is where you can specify information about your site (metadata) like the site title and description, which Gatsby plugins you’d like to include, etc. (Check out the config docs for more detail).

7. gatsby-node.js: This file is where Gatsby expects to find any usage of the Gatsby Node APIs (if any). These allow customization/extension of default Gatsby settings affecting pieces of the site build process.

8. gatsby-ssr.js: This file is where Gatsby expects to find any usage of the Gatsby server-side rendering APIs (if any). These allow customization of default Gatsby settings affecting server-side rendering.

9. LICENSE: Gatsby is licensed under the MIT license.

10. package-lock.json (See package.json below, first). This is an automatically generated file based on the exact versions of your npm dependencies that were installed for your project. (You won’t change this file directly).

11. package.json: A manifest file for Node.js projects, which includes things like metadata (the project’s name, author, etc). This manifest is how npm knows which packages to install for your project.

12. README.md: A text file containing useful reference information about your project.

🎓 Learning Gatsby

Looking for more guidance? Full documentation for Gatsby lives on the website. Here are some places to start:

• For most developers, we recommend starting with our in-depth tutorial for creating a site with Gatsby. It starts with zero assumptions about your level of ability and walks through every step of the process.

• To dive straight into code samples, head to our documentation. In particular, check out the Guides, API Reference, and Advanced Tutorials sections in the sidebar.

💫 Deploy

On push to master Zeit's now automatically deploys to prod. Branches and PRs are similarly deployed on push.