Re:Why Markdown Is Not My Favourite Language (2012)
by TazeTSchnitzel on Saturday November 29, 2014 @04:24PM
(#8675133)
>Github can render org-mode files to HTML directly if checked into a repo
They also support ASCIIDoc, ReST, MediaWiki markup, Creole, etc.
Re:Why Markdown Is Not My Favourite Language (2012)
by donniezazen on Sunday November 30, 2014 @03:59AM
(#8676391)
I really wish that other services would be like this. You enter text in a few popular markup languages and not one specific language.
Re:Why Markdown Is Not My Favourite Language (2012)
by pyre on Saturday November 29, 2014 @02:45PM
(#8674826)
> A little known fact, even among most org-users: Github can render
> org-mode files to HTML directly if checked into a repo, thus you can
> write your README files as org-files.
I recently stumbled across the tidbit. The Ruby library Github uses to generate it though isn't 100% though. If you want to use org-mode properties for style customization of html output your SOL.
Original project:
https://github.com/bdewey/org-ruby
Currently, you cannot do much to customize the conversion. The
supplied textile conversion is optimized for extracting “content”
from the orgfile as opposed to “metadata.”
It does say that developement has moved to:https://github.com/wallyqs/org-ruby
Which has no such note, but doesn't say anything about supporting it.
A little known fact, even among most org-users: Github can render org-mode files to HTML directly if checked into a repo, thus you can write your README files as org-files.
Shameless example: https://github.com/josteink/csharp-mode/blob/master/README.o...
This alone was enough to make me drop Markdown as my go-to format for semi-formatted text-files.
A subtle killer feature here is org-babel. You can embed proper code in your text-files and have your editor (at least Emacs) understand them as such. Which makes it excellent for writing technical documentation for projects where code is involved.