emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Thomas Herbert <mashdot@toshine.net>
To: emacs-orgmode@gnu.org
Subject: Re: Publishing notes to a website
Date: Tue, 15 Mar 2011 00:28:42 +0000	[thread overview]
Message-ID: <20110315002842.97947dzdm85pn484@webmail.tuffmail.net> (raw)

Kyle Sexton <ks <at> mocker.org> writes:

> I'm looking for advice on ways people are publishing their org notes
> to a website.  So far I've looked at blorgit and it's really nice, but
> the dependency for a backend emacs session and running through sinatra
> makes me wary of putting it out on my server for the world.
> 1.  What methods are people using to publish their org notes?
> 2.  Anyone have sample sites that I can see what the output looks like?


I have been actually been working on a simple clean solution for  
writing in org-mode and keeping the file as org-mode. What I have come  
up with is a "Textile" like PHP class that translates org-mode files  
into HTML.

It is still very very alpha and hope to release the code soon for  
people to look at, work and improve or completely scrap and take my  
idea and do it better.

You can see it in action at http://toshine.org  where I have built a  
simple flatfile CMS that reads .org files in a folder, reads the  
org-mode header, and creates menus, creates post titles, meta  
descriptions, dates etc and is then passed through my "orgile" php  
class that spits out HTML. My aim was to simply keep the files as  
org-mode and stick them in a folder and let the CMS deal with the  
rest. Also I didn't like the complexity of "Jekyll"  
http://jekyllrb.com/ installing ruby gems, YAML and all that. I have a  
single php file for the CMS and a single php file for the "orgile"  
class. The class is totally independent of the CMS, like "textile" and  
the "textile class".

If you look at the bottom of a website article you can see the .org  
file. I still have a lot to do and currently I have just added the  
features that I needed like basic HTML markup, footnotes and  
blockquotes. My aim really was to spend time writing my articles and  
throwing them into a folder. Most of the time I correct the file via  
"Tramp" in Emacs and don't have to republish anything as the file is  
just read.

I have though added PHP cache_lite in my CMS so the pages are created  
as HTML via "orgile" but served as the cached HTML page. Saves PHP  
processing for pages that don't change the whole time. I just remove  
the page from cache if I make a edit later.

Anyway have a look and just to say I am totally focused on staying,  
working and dealing only with org-mode files so I can concentrate on  
the writing. Hopefully "orgile" will become useful for people or at  
least spark some better programmers writing a better version of it.



             reply	other threads:[~2011-03-15  0:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-15  0:28 Thomas Herbert [this message]
2011-03-17  9:21 ` Publishing notes to a website Bastien
2011-04-26 15:36 ` 'Mash
2011-04-26 21:01   ` William Gardella
2011-04-26 23:02     ` 'Mash
2011-04-27  0:41       ` Eric Schulte
  -- strict thread matches above, loose matches on Subject: below --
2011-03-11 20:04 Kyle Sexton
2011-03-11 20:22 ` Bernt Hansen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110315002842.97947dzdm85pn484@webmail.tuffmail.net \
    --to=mashdot@toshine.net \
    --cc=emacs-orgmode@gnu.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).