Orgmode format render test

This page contains org-mode constructs as a test to see how they get rendered to html. It's the visual last test to see if I have gotten the css stuff right. The page will be updated each time a css change is made so it can be checked without having to hunt for content which uses a special construct.

This paragraph was started with a begin_quote construct

Pull quotes are provided by a plugins and thus require a liquid template construct. This only works when you surround the complete paragraph in an begin_html / end_html construct.

The documentation of org-ruby mentions support of footnotes, but the one¹ I created here does not render very nicely I think. I would have expected there to be a link.

Orgmode can do inline footnotes ²

• Level 1

  • Level 2

    • Level 3

• Level 4

  • Level 5

    • Level 6

  • orgmode has checkbox like list items

    • but these don't do anything special
  • term1 :: defined;
  • term2 :: defined;
  • term3 :: defined with http://example.com link

Code blocks can be produced in the usual way with #+BEGIN_SRC blocks in org-mode. Highlighting is automatic when a pygments lexer is available.

1def foo
2  puts 'foo'
3end

Same construct with the -n switch, which should turn on line numbers:

1def foo
2  puts 'foo'
3end

and the same construct with the +n switch, which should continue the linenumbering from the previous snippet

1def foo
2  puts 'foo'
3end

Other code related embedding is for githubs gist facility

In orgmode a line on its own with nothing else but at least 5 dashes is considered a rule.

So, when we use 4 we should just get 4 dashes: —-

Orgmode has a verse construct, but that does not give output (at the time of writing):

The center construct gets a text-align:center attribute, so this should work, given correct CSS.

The example block format from orgmode

  Some example from a text file.

Orgmode has extensive support for LaTeX fragments, but this doesn't transfer well with the exporter in use.

If $a^2=b$ and \( b=2 \), then the solution must be either $$ a=+\sqrt{2} $$ or \[ a=-\sqrt{2} \].

description

http link with description

http://example.com

Examples - internal link to header

<<Orgmode>> - the text 'Orgmode' would link to here from everyhwere (radio target) in Orgmode

Orgmode has a way to define linkword, which I have done for this file linkword 'google' used

Image links are just normal links in orgmode, which just happen to link to an image.

link is to image, this is the description

Typically my images will be hosted at either a site like flickr or at my own media-site running mediagoblin, so let's take an image from there.

Just linking to an image source will produce an image tag, unstyled. Typically in blog posts a more or less standard set of image types are needed:

1. Things that liven up the text, typically pull-left or pull-right in my blog. Images will not be that large;
2. Photographs which are the subject or part of the subject of the content. Typically larger and detailed, there may be a need to be able to zoom into these pictures
3. Pictorial elements, part of the theme, perhaps a one-off solution.

Strategies for getting images into a blog, given that we use org-mode our options are rather limited. I'd want to stay away as much as possible from using specific jekyll constructs, that is if we want the blog posting to be useful outside of jekyll.

The price for that is that we then cannot use liquid tags, unless wrapped in an html block and the only way we would make distinctly different images would be using a #+ATTR_HTML: construct.

How I want it to look:

Doing the same image in an orgmode way is cumbersome, so I'm using a plugin to do this. The goal is to have all media on media.mrblog.nl, which is probably too strict a limitation, but it allows to have very concise image definitions with a short liquid tag.

Here's how the tag looks:

1{%raw%}
2{% gmg shadowed 168 %}
3{%endraw%}

The plugin does a request (on building) to the media site and retrieves some json data which we could use. (For the caption for example)

Result:

1{% raw %}
2Sitename taken from the variable site.name :: {{site.name}}
3{{'this will be upcased by a filter' | upcase }}
4{% endraw %}

1Sitename taken from the variable site.name :: {{site.name}}
2
3{{'this will be upcased by a filter' | upcase }}