emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Hanno Perrey <hanno@hoowl.se>
To: Benoit Bidoggia <benoit.bidoggia@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Publishing a project and selecting files (possibly with tags)
Date: Fri, 22 Jul 2022 21:32:02 +0200	[thread overview]
Message-ID: <87v8roncnk.fsf@hoowl.se> (raw)
In-Reply-To: <CAGsLRvYYtaYK+kMJXuf=wViC2_Guvkc3=1DQnmYvLnWVcgDKJg@mail.gmail.com>

Dear Benoit,

this does sound like what I have done for my blog: I write all blog
posts as org files in a single directory called "posts" and publish them
through org-publish. In each file, I define tags via the =FILETAGS=

Upon publishing, I set =:sitemap-format-entry= in
=org-publish-project-alist= to a custom function which creates new org
files corresponding to the tags being used in the posts. These org files
are then published as well, giving me a sitemap with all posts and a
sitemap for each individual tag (with short teaser text).

This is not exactly what you asked for and maybe not as straightforward
as what you envisioned, but I think that you could customize this
approach to fit your use case.

The code for my blog is available here: https://gitlab.com/hperrey/hoowl_blog

(Please note that I copied it together from various sources back when
without always understanding every detail and I am afraid that it shows.)

The resulting html you can find here: https://www.hoowl.se

Let me know should you have questions concerning the code!

Best wishes,


Benoit Bidoggia <benoit.bidoggia@gmail.com> writes:

> Dear list,
> This is my problem: I have a large set of org files (created with
> org-roam), which contains all my thoughts on different topics (for
> example "work1", "work2", "personal1"...)
> I would like to create different projects (for example "work1",
> "work2", "personal1") to be able to publish these files under
> different folders (for example "./pub_work1", "./pub_work2",
> "./pub_personal1") for which I could define some filters to decide
> what goes where.
> The rules should be something likes this:
> - nothing is exported, except that
> - files with tag "WORK1" are exported in "./pub_work1"
> - files with tag "WORK2" are exported in "./pub_work2"
> - files with tag "PERSONAL1" are exported in "./pub_personal1"
> I cannot use the file name to filter the files, which seems to exclude
> the possibility of using the options ":exclude" and ":include" of
> org-publish-project-alist.
> Ideally I would like to use tags (or some descriptors I can include
> directly in the org file), but I did not have much success using the
> options ":with-tags" or ":select-tags".
> Can this be done? If so, how?
> Thank you very much, best regards.
> Benoît

Hanno Perrey

      parent reply	other threads:[~2022-07-22 19:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-18 11:11 Publishing a project and selecting files (possibly with tags) Benoit Bidoggia
2022-07-20 20:38 ` Munyoki Kilyungi
2022-07-22 19:32 ` Hanno Perrey [this message]

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=87v8roncnk.fsf@hoowl.se \
    --to=hanno@hoowl.se \
    --cc=benoit.bidoggia@gmail.com \
    --cc=emacs-orgmode@gnu.org \


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