Browse code

Minor update to navigation, Updated Copyright, added beginning upgrade instructions.

Brandon Mathis authored on 16/07/2011 at 19:21:09
Showing 3 changed files
... ...
@@ -10,7 +10,7 @@
10 10
     <input class="search" type="text" name="q" results="0" placeholder="Search"/>
11 11
   </fieldset>
12 12
 </form>
13
-<ul role="main-nav">
13
+<ul role="navigation">
14 14
   <li><a href="{{ site.root }}/">Blog</a></li>
15 15
   <li><a href="{{ site.root }}/blog/archives">Archives</a></li>
16 16
 </ul>
... ...
@@ -122,7 +122,7 @@ Github will queue your site for publishing (which usually occurs instantly or wi
122 122
 ### Deploying to a Subdirectory (Github Project Pages does this)
123 123
 
124 124
 If you're deploying to a subdirectory on your site, or if you're using Github's project pages, make sure you set up your urls correctly in your configs.
125
-You can do this automatically:
125
+You can do this *almost* automatically:
126 126
 
127 127
     rake set_root_dir[your/path]
128 128
 
... ...
@@ -131,10 +131,10 @@ You can do this automatically:
131 131
 
132 132
 Then update your `_config.yml` and `Rakefile` as follows:
133 133
 
134
-    # Change the url in _config.yml
134
+    # _config.yml
135 135
     url: http://yoursite.com/your/path
136 136
 
137
-    # If deploying with rsync, update your Rakefile path
137
+    # Rakefile (if deploying with rsync)
138 138
     document_root = "~/yoursite.com/your/path"
139 139
 
140 140
 To manually configure deployment to a subdirectory, you'll change `_config.yml`, `config.rb` and `Rakefile`
... ...
@@ -162,7 +162,7 @@ To manually configure deployment to a subdirectory, you'll change `_config.yml`,
162 162
 ## License
163 163
 (The MIT License)
164 164
 
165
-Copyright © 2009 Brandon Mathis
165
+Copyright © 2009-2011 Brandon Mathis
166 166
 
167 167
 Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the ‘Software’), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
168 168
 
... ...
@@ -11,26 +11,6 @@ for a year and a half, I can see that it's far better for Octopress to be able t
11 11
 Some new features make the transition worth it. You can write your own [plugins](https://github.com/mojombo/jekyll/wiki/Plugins) which consist of generators, converters, and liquid tags.
12 12
 Now it's much easier to hack Jekyll without forking. I expect to see some great plugins emerge from the Jekyll community, and I'll be adding my favorites into Octopress.
13 13
 
14
-
15
-## More Than a Starting Point
16
-
17
-I initially saw Octopress as the fastest way to get started with a fairly nice Jekyll blog, but now that Jekyll is so hackable, I'm hoping that Octopress will also become a great introduction to hacking Jekyll and a place to find great plugins from the community.
18
-
19
-I've already been combing through plugins that other people are writing and I've found some gems. Octopress now has:
20
-
21
-- **Sitemap generator** - suitable xml for submitting to search engines
22
-- **Haml converter** - currently pages and posts can be converted, but not layouts
23
-- **Liquid tag Github gists** - embeds gists in a noscript tag for RSS readers and crawlers, then uses Github's javascript to display gists to site visitors
24
-
25
-Octopress also has custom filters which work through Liquid's filtering system. I've added these for now:
26
-
27
-- **Smart quotes** for posts and pages
28
-- **Title case** an adaptation of John Gruber's intelligent title capitalization script
29
-- **Absolute urls** using '/' as a url opener for relative paths gets converted to an absolute url for RSS readers
30
-- **Ordinal dates** dates are output like "October 5th" or "July 3rd"
31
-
32
-Of course Octopress still supports simple setup for Twitter, Disqus Comments, Google Custom Search, Google Analytics, Delicious Bookmarks, and now Pinboard Bookmarks.
33
-
34 14
 ## Upgrading
35 15
 
36 16
 Unfortunately upgrading isn't as smooth as I would like. Some things have changed that require a bit of fiddling on your part. It's less than ideal, but if you were adverse to fiddling, you'd be using Wordpress right?
... ...
@@ -44,8 +24,4 @@ If you want to keep the time-stamp data, you can now add dates to the post in th
44 44
 
45 45
 I've updated the new post rake task `rake post[title for your new post]` to correctly name new posts, and to automatically insert the time-stamp into the yaml front-matter for a new post. This way you can set the time when you want to publish without having to write out the whole post date.
46 46
 
47
-
48
-
49
-Here are some steps you can take to get your blog running again on this update:
50
-
51
-1.
47
+TODO: add more steps for upgrading