Each .md file will be turned into a page on the site, so it should be very easy to add new top-level pages. See the contact page for a super simple example to copy. .html will also work if you want to customize more.
The social links at the bottom and the nav links at the top are all controlled via the _config.yml. The syntax is a little confusing, but there's probably tools to make it more straightforward.
The gist is that social is a bunch of key-value paris while nav is a list of key-values, where most entries only have the one key (name). The kdy difference is which lines start with a -. We can probably move this bit of the customization into json if that's easier.
Anything in the _posts directory is a new, independent post. They should be titled YYYY-MM-DD-url-slug.md (where the slug is how people will get to it). They'll need a title in the frontmatter (the data in between --- at the top of files:
---
title: This can be anything, woo title!
fun trivia, the lack of that frontmatter in this file is why you can see it on github, but not on the site itself!
After that, just ship plain markdown.
There's also a hidden page at /styles that shows you what the css will look like w/ different constructs. Feel free to delete that page once you don't feel like you need it (or don't, whatever. It's hidden).
- Fork this repo
- (assuming you're hosting the site on Github, which you should) rename the repo to
cgordini.github.io - Address
FIXMEcomments in_config.ymlto customize the site to your liking - Add a
CNAMEfile withcorygordinier.com(aka follow these instructions - Probably remove the posts in
_postsand replace them with items of your choosing. - Make sure your github pages settings are as you want them (you're deploying from the
masterbranch if it asks - Push! The production site will correspond with whatever's in master.
- Edits can also be made in the Github UI. You know the drill.