From: "Eric Schulte" <email@example.com>
To: 'Mash <firstname.lastname@example.org>
Cc: William Gardella <email@example.com>,
Emacs Org mode mailing list <firstname.lastname@example.org>
Subject: Re: Publishing notes to a website
Date: Tue, 26 Apr 2011 18:41:18 -0600 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <firstname.lastname@example.org> (Mash's message of "Wed, 27 Apr 2011 00:02:25 +0100")
[-- Attachment #1: Type: text/plain, Size: 3715 bytes --]
Having not read the whole thread I apologize if I'm retracing already
covered ground. I've had success using Org's built in projects .
Although this results in a flat html web-site it is easy to impose a
consistent theme, and to publish large numbers of files.
To give some personal examples my homepage , and even the wiki for my
lab  are both published using Org-mode's publishing facilities, the
latter with a git repository backend and some fancy post_update hooks.
For smaller sites (like my home page) I just include the project
definition in an elisp block in a commented heading of the main Org-mode
file (e.g., ), and for larger efforts I define the projects in a
separate elisp file, or even in an external script which can be run with
an Emacs batch instance.
Hope this helps. Best -- Eric
'Mash <email@example.com> writes:
> Quoting William Gardella <firstname.lastname@example.org>:
>> 'Mash <email@example.com> writes:
>>> Quoting Thomas Herbert <firstname.lastname@example.org>:
>>>> 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.
>>> 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!).
>>> The Orgile PHP flat file CMS (currently used for http://toshine.org).
>>> The Orgile PHP flat file CMS (fully commented code).
>>> Well I hope it is at least interesting for someone on this list.
>> 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 :)
> 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.
 the attached snippet of org-mode is adapted from my homepage.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: publishing-example.org --]
[-- Type: text/org, Size: 1676 bytes --]
** COMMENT publishing
This code is used to publish this page to the cs.unm.edu webserver.
For more information on publishing Org-mode pages see the [[http://orgmode.org/manual/Publishing.html#Publishing][Publishing
section]] of the [[http://orgmode.org/manual/index.html#Top][Org-mode manual]].
#+begin_src emacs-lisp :results silent
(setq homepage-dir (file-name-directory (or load-file-name buffer-file-name)))
(unless (boundp 'org-publish-project-alist)
(setq org-publish-project-alist nil))
;; the main html page
:html-postamble ; replaces the auto-generated postamble
"<div class=\"clear-fix\"></div> custom-postamble </div>"
:style "<link rel=\"stylesheet\"href=\"data/stylesheet.css\"type=\"text/css\">"))
;; the contents of the data/ directory, css, images, etc...
:base-directory ,(expand-file-name "data" homepage-dir)
;; a single combined project to publish both html and supporting materials
[-- Attachment #3: Type: text/plain, Size: 48 bytes --]
next prev parent reply other threads:[~2011-04-27 0:41 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
2011-04-27 0:41 ` Eric Schulte [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-03-11 20:04 Kyle Sexton
2011-03-11 20:22 ` Bernt Hansen
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 \
* 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).