emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Eric Schulte" <schulte.eric@gmail.com>
To: Matthew Lundin <mdl@imapmail.org>
Cc: Rustom Mody <rustompmody@gmail.com>,
	emacs-orgmode <emacs-orgmode@gnu.org>
Subject: [ANN] blorgit: org-mode blogging engine
Date: Sun, 22 Mar 2009 11:00:03 -0700	[thread overview]
Message-ID: <874oxle8v0.fsf_-_@gmail.com> (raw)
In-Reply-To: <m2skl5fz9j.fsf@fastmail.fm> (Matthew Lundin's message of "Sun, 22 Mar 2009 08:44:24 -0500")

Matthew Lundin <mdl@imapmail.org> writes:

> I just discovered that there is ruby blog engine in development that
> uses org files as a back end:
> - http://github.com/eschulte/blorgit/tree/master
> (Looks really promising, Eric!)

Thanks Matt,

I've been using this myself for a couple of weeks now for sharing my
notes at work, and to convince my girlfriend (a sworn enemy of Emacs) to
help maintain a large org-mode formatted recipe catalog, by editing
pages through the blorgit web interface.  I think this should now be
ready for public consumption.

Blorgit is a simple blogging engine.  Features include...

- comments :: Comments can be left through the web interface, and they
              will be appended to the org-mode file under a "Comments"
              header.  They can be turned on or off globally, or through
              the properties of the "Comments" header

- editing :: optional editing through the web interface can be turned on
             or off, and can be password protected

- themes :: there are a couple of default themes distributed with
            blorgit (try the 'org' theme using Tim Burt's folded

- runs directly from .org files :: this is designed to run off of a
     directory of org-mode formatted files, all exportation is handled
     by blorgit, so you should be able to point this to an existing
     directory of org-mode files, fire up the browser and get going.
     This also means that it is easy to add content or make
     configuration changes through git or any VC system.

- exportation :: all pages can be downloaded in org-mode or LaTeX

The goal was to be relatively simple/hackable.  The look and feel should
be largely malleable through css, and if you want to dig deeper, all of
the views and logic are located inside the blorgit.rb file.

See http://github.com/eschulte/blorgit/tree/master for instillation and
configuration instructions.  If anyone has any feedback, or wants to add
new default themes I'm all ears.

Thanks -- Eric

Also, for a slightly more ambitious (if less mature) effort see orGit.
It an org-mode formatted wiki, backed by a git repository (edits are
automatically committed to git, some git actions (reversion of pages,
etc...) can be handled through the web interface, and the git history
can be browsed through the wiki) see http://github.com/eschulte/orGit/tree/master

  parent reply	other threads:[~2009-03-22 17:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-21 10:44 blorg?? Rustom Mody
2009-03-22 13:44 ` blorg?? Matthew Lundin
2009-03-22 14:10   ` blorg?? Alex Ott
2009-03-22 18:00   ` Eric Schulte [this message]
2009-03-22 14:21 ` blorg?? David Bremner

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=874oxle8v0.fsf_-_@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mdl@imapmail.org \
    --cc=rustompmody@gmail.com \


* 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).