Filed under Misc

Test md

Markdown format test file, written by Greg Schueler,

Quick Markdown Syntax Guide

This guide shows you how to use Markdown instead of HTML when writing posts or comments.

Markdown is way easier to use than HTML. (But you can still use HTML at the same time if you really want to and you know how.)

Just write in the comment box the same way it's shown in this file, it's really that simple.

(See bottom for more info about Markdown itself.)


For a URL or email, just write it like this:


To use text for the link, write it like this.

You can add a title (which shows up under the cursor), like this.

Reference Links

You can also put the link URL below the current paragraph like this.

Here the text "link URL" gets linked to "http://url", and the lines showing "1: http://url" won't show anything.

Or you can use a shortcut reference, which links the text "shortcut" to the link named "shortcut" on the next paragraph.


Use * or _ to emphasize things:

this is in italic and so is this

this is in bold and so is this

this is bold and italic and so is this

Just write paragraphs like in a text file and they will display how you would expect. A blank line separates paragraphs.

So this is a new paragraph. But any text on adjacent lines will all end up in the same paragraph.


Use the > character in front of a line, just like in email. Use it if you're quoting a person, a song or whatever.

You can use italic or lists inside them also. And just like with other paragraphs, all of these lines are still part of the blockquote, even without the > character in front.

To end the blockquote, just put a blank line before the following paragraph.

Preformatted Text

If you want some text to show up exactly as you write it, without Markdown doing anything to it, just indent every line by at least 4 spaces (or 1 tab).

This line won't *have any markdown* formatting applied.
I can even write <b>HTML</b> and it will show up as text.
This is great for showing program source code, or HTML or even Markdown.
<b>this won't show up as HTML</b> but exactly <i>as you see it in
this text file</i>.

(In a normal paragraph, this will show up in bold just like normal HTML.)

Remember, you have to indent by at least 4 spaces to do it. This paragraph won't be preformatted.

And if you use [reference][] links, make sure the links are indented by fewer than 4 spaces.


(woops, that link didn't work, see? It just got displayed as preformatted text.)

As a shortcut you can use backquotes to do the same thing while inside a normal pargraph. This won't be *italic* or **bold** at all.


  • an asterisk starts an unordered list
  • and this is another item in the list
  • or you can also use the + character
  • or the - character

To start an ordered list, write this:

  1. this starts a list with numbers
  2. this will show as number "2"
  3. this will show as number "3."
  4. any number, +, -, or * will keep the list going.
    • just indent by 4 spaces (or tab) to make a sub-list
      1. keep indenting for more sub lists
    • here i'm back to the second level


This is a huge header

this is a smaller header

Just put 1 or more dashes or equals signs (--- or ===) below the title.

You might use the huge header at the very top of your text for a title or something (except weblog posts usually already have a title), and use the smaller header for subtitles or sections.

Horizontal Rule

just put three or more *'s or -'s on a line:

or you can use single spaces between then, like this:


Make sure you have a blank line above the dashes, though, or else:

you will get a header


To include an image, just put a "!" in front of a text link:

alternate text

The "alternate text" will show up if the browser can't load the image.

You can also use a title if you want, like this:

tiny arrow


What if you want to just show asterisks, not italics?

  • this shows up in italics: a happy day
  • this shows the asterisks: *a happy day*

The backslashes will disappear and leave the asterisks.

You can do the same with any of the characters that have a special meaning for Markdown.

More Headers

More ways of doing headers:

this is a huge header

this is a smaller header

this is even smaller

more small

even smaller
smallest still: <h6> header

You can use up to 6 # characters at the beginning of the line.
(You can optionally put them on the end, too, and they will disappear.)

HTML crap

Don't worry about special HTML characters. I can write an ampersand & a less-than sign, and they show up as I intend them to: 3 < 4.

(You can still write &amp; (& character) and &lt; (<) or &gt; (>) if you want. or ignore what I just said.)


This text file shows you how to use Markdown instead of crappy HTML when writing posts or comments.

Markdown is an easier way of making HTML pages from text, rather than having to know HTML.


Thanks to John Gruber and Aaron Swartz for creating Markdown.


No rights reserved, do with this what you like.

PS : Some new tests

Python :

for i in range(0, 5):
    print i

Java :

for(int i : Arrays.asList(1, 2, 3, 4, 5))
    System.out.println("" + i);

Some inline code, looks great.

Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.

A quote inside a quote.


Key Ctrl Ctrl-Shifted Notes
[ Subset of, Not subset of
] Superset of, Not superset of
Tagged , ,

Hello world

What an original title for a first post. But like a first test in a new language, it's always a good way to start. And you have to start somewhere...

It's been a long time since my last blog. One of the top reason I stopped was WordPress. WordPress is amazing. You can do almost anything with it. But because of that, it's too much when you just want to blog. My server (the one you're reading from now) had a hard time to support the charge even with the very small audience I had (hundred readers a day). I want to keep this hosting plan because it's really cheap (around 25€ a year, hosting and domain name included), and I don't really need more. I know that a lot has changed in the last years. You can now host your static site on GitHub, or even have some not totally static site on Google AppEngine or Heroku. Maybe even with Amazon, I don't really know their product. But I'm happy with my 25 gigas plan at OVH (a French hosting provider), and don't want to change.

I'm unhappy with WordPress, but I want to blog. So I started searching through the web for different solution, and I rapidly came to a solution : I want to blog using a static site generator. There is a lot out there, and it's not that simple to find the right one. It took me almost a month to choose, but I'm finally happy with my solution.


First, as I already use GitHub, I tried Jekyll. It's a really well built static site generator, relatively easy to configure, and with lot of examples and documentation on the web. It's coded in Ruby, and of course, open source.

I played with it almost a week, trying to make a design that pleased me. I started to being stuck when I wanted to play with categories and tags. It's not like I need it, and to improve it you need to add some plugins, or hack Jekyll yourself.

At this point, I started searching something else. Jekyll is a good start, and I would have happily get back to it if I didn't find something else. But for now, I don't want to learn Ruby, and relying only on the available plugins can cause some troubles.


Since I found Jekyll very interesting and promising, the next "toy" I tried was his Python port (at least, originally), Hyde. But because the site (first link on Google) isn't explicit enough, I started using a very old version, the 0.5.3. Yes, if I had read the README more carefully I would have seen the newer version. And yes, just by checking the age of the last commits (3 years ago) I also could have seen that's an abandoned project. But still, I didn't see it at the beginning.

I first played with it to create the site of my startup (LumApps), on-line soon as I wrote this lines. Then I tried to port my Jekyll site to Hyde. I did it so fast, I was impressed by the ease of it. But then, I started to be stuck again with the categories and tags. And although Jekyll has a lots of examples and documentation, there is a lot less for Hyde. And after some times of search, of hack and everything, I found the newer version of Hyde, the 0.8.5a14.

I switched my blog to this newer Hyde, and oh boy, it was way more difficult to do it than it was to switch from Jekyll and Hyde 0.5.3 :

  • The newer Hyde uses Jinja2 instead of Django
  • The configuration system is totally different
  • There is almost no examples
  • The documentation is a pain in the ass : hard to find, missing a lot of points, etc... The README tells it better than me, it's a work in progress
  • Even when you found examples, it may not work (I'm not entirely sure why)

After 4 days of hard work on this newer version, I decided to leave Hyde. The first goal of using a static site generator was to make my life easier... I already did too much work to just have a basic blog, I can't even imagine the work I'll have to put to had some advanced feature.


After the Hyde failure, I searched for static site generator made for blogging. Octopress rapidly came out of my Google search. It's an overlay of Jekyll, configuring it with plugins and theming. I tried it very briefly. On of the first thoughts I had was "Ok, it's really cool, but it's like WordPress, too much." And by playing with it, I kept thinking that over and over. And it's still in Ruby.


Then, by searching again, I found pelican. In Python, made by a French developer (cocorico !), simple, easy to install, easy to use, multiple theme already given. Sounds like a winner. And there is some good theme, like the one by tBunnyMan, pelican-chunk.

By the end of the night, I got my blog up, with everything that I wanted. Or almost. First I used my modified version of tBunnyMan's theme (wider, with the categories regroup in one menu item, and some other stuff), but that didn't pleased me enough. So I created the current theme the next week end, very easy to make (just a few hours, but yeah, almost all the design choices were already made during all my play-around). You can see the result on my Test page.

There is still some things to do though :

  • Sitemap
  • Robot.xml
  • Fix border "bug" on archives.html
  • Set markdown date with more precise data than just YYYY-MM-DD
  • Responsive design (for the moment, sorry for the mobile reader, especially those using Apple devices)
  • Put all in github