From: Puneeth Chaganti <punchagan@gmail.com>
To: news1142@karl-voit.at
Cc: emacs-orgmode@gnu.org
Subject: Re: Minimal overhead Org-mode blogging system
Date: Thu, 8 Dec 2011 09:59:08 +0530 [thread overview]
Message-ID: <CALnw1fRvOUvGwuA8MtrLcEvSNfiVz4kqYOf6URs_KgaerJwUog@mail.gmail.com> (raw)
In-Reply-To: <2011-12-08T01-25-36@devnull.Karl-Voit.at>
Hi Kurt,
On Thu, Dec 8, 2011 at 6:01 AM, Karl Voit <devnull@karl-voit.at> wrote:
> * Puneeth Chaganti <punchagan@gmail.com> wrote:
>> On 12/4/11, Karl Voit <devnull@karl-voit.at> wrote:
>>>
>>> Therefore I sat down and thought about a workflow that should be
>>> enough for writing simple weblog entries:
>>>
>>> - create an Org-mode heading (anywhere!)
>>> - make sure that there is an (uniq) :ID: property
>>> - add the tag :blog: to heading
>>> - <write content, subheadings, ...>
>>> - change state of top-heading to DONE
>>> - this enables blog entries «in the queue»
>>> - (manually) invoke generation-script
>>>
>>> This enables me quick blogging with a list of advantages:
>>>
>>> - a blog entry can be located anywhere in all of my Orgmode files
>>> - no extra formatting steps
>>> - very small (almost non-existent) overhead to create a blog entry
>>> - no duplicate information
>>> - updates only in Orgmode, not HTML or any in-between format
>>> - static (fast) pages
>>> - self-hosting without any fancy services behind like RDBS
>>
>> I have a system, that does most of what you are looking for.
>>
>> https://github.com/punchagan/blog-files
>
> ... I really do like your blog (and found several very interesting
> entries *g*) but I (can not and) do not want to use Wordpress.
I'm sorry that the repository doesn't have a README, but this solution
doesn't use Wordpress. It basically uses the publishing mechanism of
org-mode and is based on ideas (and code) from org-jekyll and
reprise.py (https://github.com/uggedal/reprise).
-- Puneeth
next prev parent reply other threads:[~2011-12-08 4:29 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-04 16:51 Minimal overhead Org-mode blogging system Karl Voit
2011-12-07 16:30 ` Steinar Bang
2011-12-07 17:20 ` Puneeth Chaganti
2011-12-07 20:11 ` Eric Schulte
2011-12-11 13:20 ` Bastien
2011-12-08 0:31 ` Karl Voit
2011-12-08 4:29 ` Puneeth Chaganti [this message]
2011-12-08 14:19 ` Karl Voit
2011-12-08 16:45 ` Puneeth Chaganti
2011-12-08 22:02 ` Karl Voit
2012-01-15 18:08 ` Steinar Bang
2012-01-16 22:54 ` Puneeth Chaganti
2012-01-19 22:15 ` Steinar Bang
2012-01-20 18:19 ` Chris Gray
2012-01-21 5:15 ` Scott Randby
2012-01-21 5:53 ` Nick Dokos
2012-01-21 6:26 ` Chris Gray
2012-01-17 18:50 ` tychoish
2012-01-18 3:06 ` Eric Schulte
2012-01-20 16:10 ` Bastien
2012-02-11 13:47 ` François Pinard
2011-12-11 4:33 ` Nathan Neff
2012-05-13 14:54 ` Neil Smithline
2012-05-15 2:24 ` Jude DaShiell
2012-05-16 0:48 ` Neil Smithline
2012-05-16 9:51 ` Jude DaShiell
2012-05-20 21:48 ` Neil Smithline
2012-06-17 8:09 ` Karl Voit
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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=CALnw1fRvOUvGwuA8MtrLcEvSNfiVz4kqYOf6URs_KgaerJwUog@mail.gmail.com \
--to=punchagan@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=news1142@karl-voit.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).