The documentation is generally pretty good, but they didn’t really explain one fundamental thing. It’s pretty simple once you dig into the
Rakefile, but here’s a quick explanation if you just want to get up and running.
WTF is going on with the branches?
On github, you will have two branches:
master. But locally:
Huh. Interesting. Locally, you only have one branch:
source holds your posts in Markdown and other files before they are transmogrified into HTML. Once you run
rake generate, Octopress will generate all the HTML & CSS and put it all in
And when you run
rake deploy, Octopress pushes the contents of
/public (on local branch
source) to the home directory (on remote branch
So: each time you finish a post, run BOTH
rake deploy to deploy and
git push origin source to back up your source files to github.
Sublime Text <3 Markdown
So you’re writing your blog posts in Markdown like a boss. There are a few things you can do to make Sublime Text 2 a lean, mean blogging machine:
Custom themes. For example, MarkdownEditing, a series of custom themes and shortcuts for Markdown. (Hint: installing Package Control first will make this easier)
Spell check. Sublime Text 2 uses Hunspell for spell checking, the same library used in Word. This process was a bit more convoluted:
- Command-shift-p in ST2 to open Package Control
- Choose “Add Repo”. Paste in
- Command-shift-p again. Choose “Install Package,” then “Dictionaries”
- Find your preferences in Preferences > Package Settings > Markdown Editing > Markdown Settings - User
- Add the following to the settings file:
"spell_check": true, "dictionary": "Packages/Language - English/en_US.dic"
- Restart Sublime Text. Observe red squigglies when you edit Markdown.