emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: 'Mash <mashdot@toshine.net>
To: William Gardella <gardellawg@gmail.com>
Cc: Emacs Org mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Publishing notes to a website
Date: Wed, 27 Apr 2011 00:02:25 +0100	[thread overview]
Message-ID: <20110427000225.193337ai54abay80@webmail.tuffmail.net> (raw)
In-Reply-To: <877hag3exk.fsf@lw-wireless-pittnet-40-144.wireless.pitt.edu>

Quoting William Gardella <gardellawg@gmail.com>:

> 'Mash <mashdot@toshine.net> writes:
>> Quoting Thomas Herbert <mashdot@toshine.net>:
>>> 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?
>>> Kyle,
>>> 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.
>> As I mentioned earlier I have been playing around building a regex
>> parser in PHP for Org-Mode files. As you will see I am obviously an
>> amateur programmer and my hope is that if this is at all useful then
>> someone else will rewrite it. My site http://toshine.org uses both the
>> classOrgile and the Orgile CMS. If you look at the bottom of any
>> article you will see the link to the raw .org file that is
>> parsed/converted to HTML.
>> ---
>> The classOrgile PHP class (very limited currently!).
>> http://toshine.org/etc/files/classorgile.php.txt
>> The Orgile PHP flat file CMS (currently used for http://toshine.org).
>> http://toshine.org/etc/files/orgile.php.txt
>> The Orgile PHP flat file CMS (fully commented code).
>> http://toshine.org/etc/files/orgile-commented.php.txt
>> ---
>> Well I hope it is at least interesting for someone on this list.
>> 'Mash
> Limited though it may be, I'm extremely impressed with the results you
> are getting out of this little flat-file CMS :)
> It seems like a more "blog" (periodical literature)-like solution than
> Blorgit, which in spite of its name is really a wiki framework.  I think
> I'll be trying this in my sandbox soon :)
> Will

Thanks Will, and do let me know if you need any help deciphering my  
code. It looks a lot better in php-mode!
It really is actually a very simple program, and really easy to remove  
what you don't need and add what you want.
You have my email address so pop me a line whenever.



  reply	other threads:[~2011-04-26 23:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-15  0:28 Publishing notes to a website Thomas Herbert
2011-03-17  9:21 ` Bastien
2011-04-26 15:36 ` 'Mash
2011-04-26 21:01   ` William Gardella
2011-04-26 23:02     ` 'Mash [this message]
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=20110427000225.193337ai54abay80@webmail.tuffmail.net \
    --to=mashdot@toshine.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=gardellawg@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).