emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jon Anders Skorpen <jaskorpe@mindmutation.net>
To: emacs-orgmode@gnu.org
Subject: Blog-like sitemap for org-publish
Date: Sat, 6 Aug 2011 21:57:35 +0000	[thread overview]
Message-ID: <20110806215735.GA19596@facies.mindmutation.net> (raw)

Hi.

I have made a function which creates a blog-like sitemap. It works as
an alternative sitemap function to org-publish. The second commit adds
a list of blog entries by year and keyword. The commit-diffs can be
viewed here:

http://git.mindmutation.net/?p=org-mode.git;a=commitdiff;h=2448e4d5dfa0dca8f5126b2e12f8ad6f96ba48dc

http://git.mindmutation.net/?p=org-mode.git;a=commitdiff;h=cbd90e570c2f64ddd279603acc78af51f6b3f458

Some of the functionality is overlapping with code in org-publish. To
use it simply set :sitemap-function to org-blog-export. It is similar
to the default sitemap function, but :sitemap-file-entry-format and
:blog-entry-format is semantically different.

I hope this can be of use to others, and I therefore submit it here
for comments and feedback, and maybe eventually inclusion. My main
question is what kind of copyright notices should be at the top of the
file? Some parts of the code is almost verbatim from
org-publish. There is also no license information at the top yet.

I am open to signing copyright assignment to FSF if at some point
someone thinks it should be merged into org-publish, but it can also
live happily in contrib/.

Best regards
Jon Anders Skorpen

             reply	other threads:[~2011-08-06 21:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-06 21:57 Jon Anders Skorpen [this message]
2011-08-18 17:09 ` Blog-like sitemap for org-publish Bastien
2011-08-23 14:44   ` Jon Anders Skorpen
2011-08-24 18:25     ` Bastien
2012-01-28 13:14       ` Steinar Bang
2012-01-28 22:30         ` Bastien
2011-08-24 19:18     ` Achim Gratz

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=20110806215735.GA19596@facies.mindmutation.net \
    --to=jaskorpe@mindmutation.net \
    --cc=emacs-orgmode@gnu.org \
    /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).