Skip to content

Commit

Permalink
New post. Some style changes.
Browse files Browse the repository at this point in the history
  • Loading branch information
Poita committed Jan 22, 2012
1 parent 13ca740 commit 1fa1c82
Show file tree
Hide file tree
Showing 4 changed files with 64 additions and 8 deletions.
2 changes: 1 addition & 1 deletion _layouts/post.html
Expand Up @@ -8,7 +8,7 @@ <h1>{{ page.title }}</h1>
{{ content }}

<div id="related">
{% if site.related_posts.length > 0 %}
{% if site.related_posts.length != 0 %}
<h2>Related Posts</h2>
{% endif %}
{% for post in site.related_posts limit:3 %}
Expand Down
2 changes: 1 addition & 1 deletion _posts/2012-01-22-homepage-2.0.md
Expand Up @@ -9,7 +9,7 @@ This time, I've gone for simplicity. I got sick of the incredible bloat
of Joomla and all its features that were unnecessary for what I wanted
to achieve: an essentially static website that I can easily configure.

This time, I've gone with [Tom Preston-Werner][1]'s excellent [jekyll][2]
This time, I've gone with [Tom Preston-Werner][1]'s excellent [Jekyll][2]
static site generator. I just write my posts in Markdown, run jekyll, and
it generates all the HTML for me. I have full control over the layout of
the site, and everything is there in plain text.
Expand Down
61 changes: 61 additions & 0 deletions _posts/2012-01-22-simplicity-in-everything.md
@@ -0,0 +1,61 @@
---
layout: post
title: Simplicity in Everything
tags:
- meta
- jekyll
- process
---
This website is now created using Jekyll. Originally, I had used Joomla,
a big, industrial-strength content management system.

Joomla worked well for a while, but I quickly reached a point where I
found myself unable to do, what should have been, simple things. For
example, I couldn't see any obvious way of extracting all the text from
my posts -- it was stored in a database somewhere. There was no simple
way to test changes to my site locally because I couldn't see how
everything pieced together. It was just too complex for something that
should have been very simple.

So I got thinking about what would be the simplest way to generate my
website.

Well, what is my website? It's just a collection of pages with the same
layout, but with different blobs of text inserted in the middle for each
post. I'd also like to generate some lists: recent posts, related posts,
that kind of thing.

Ideally, what I want is something that transforms this

{% highlight html %}
<body>
<h1>{{ "{{ page.title "}}}}</h1>
{{ "{{ page.content "}}}}
</body>
{% endhighlight %}

into this

{% highlight html %}
<body>
<h1>Simplicity in Everything</h1>
<p>This website is now created using Jekyll...</p>
...
</body>
{% endhighlight %}

That's *exactly* what Jekyll does. It just goes through all your pages
and uses [Liquid][1] to transform them into a static site. Don't believe me?
The entire source for this site is [on GitHub][2].

To test my website locally, I just run `jekyll --server` and head on
over to `http://0.0.0.0:4000`. To deploy, I just run `jekyll && rsync
...`, which generates the site and copies it over to my remote server.
That's it.

Why can't everything be this simple?

[1]: http://liquidmarkup.org/
[2]: https://github.com/Poita/poita.org


7 changes: 1 addition & 6 deletions style.css
Expand Up @@ -23,11 +23,6 @@ h2 {
padding: 16px 8px 8px 0;;
margin: 0;
}
tt {
font-family: courier new, courier;
font-weight: bold;
font-size: 10pt;
}
ul {
padding-left: 0px;
list-style-position: outside;
Expand Down Expand Up @@ -99,4 +94,4 @@ blockquote {
.highlight .s { color: #C00; }
.highlight .mi { color: #C09; }
.highlight .mf { color: #C09; }

.highlight .nt { color: #00C; }

0 comments on commit 1fa1c82

Please sign in to comment.