This is the data for my blog from Tom Preston-Werner, and thanks Tom Preston-Werner codes and Jekyll
origin codes readme followed:
# This is the data for my blog
It is automatically transformed by [Jekyll](http://github.com/mojombo/jekyll)
into a static site whenever I push this repository to GitHub.
I was tired of having my blog posts end up in a database off on some remote
server. That is backwards. I've lost valuable posts that way. I want to author
my posts locally in Textile or Markdown. My blog should be easily stylable and
customizable any way I please. It should take care of creating a feed for me.
And most of all, my site should be stored on GitHub so that I never lose data
again.
## License
The following directories and their contents are Copyright Tom Preston-Werner.
You may not reuse anything therein without my permission:
* \_posts/
* images/
All other directories and files are MIT Licensed. Feel free to use the HTML and
CSS as you please. If you do use them, a link back to
http://github.com/mojombo/jekyll would be appreciated, but is not required.
You can use the editor on GitHub to maintain and preview the content for your website in Markdown files.
Whenever you commit to this repository, GitHub Pages will run Jekyll to rebuild the pages in your site, from the content in your Markdown files.
Markdown is a lightweight and easy-to-use syntax for styling your writing. It includes conventions for
Syntax highlighted code block
# Header 1
## Header 2
### Header 3
- Bulleted
- List
1. Numbered
2. List
**Bold** and _Italic_ and `Code` text
[Link](url) and For more details see GitHub Flavored Markdown.
Your Pages site will use the layout and styles from the Jekyll theme you have selected in your repository settings. The name of this theme is saved in the Jekyll _config.yml configuration file.