emacs-ox-atom

Each top-level headline becomes one <entry>. File-level keywords supply the feed metadata.

 #+TITLE: My Blog
 #+ATOM_ID: https://example.org/feed.xml
 #+ATOM_LINK: https://example.org/
 #+ATOM_SELF: https://example.org/feed.xml
 #+ATOM_AUTHOR: Alice <alice@example.org>
 #+ATOM_LOGO: https://example.org/logo.png
 * My first post
 :PROPERTIES:
 :ATOM_ID: https://example.org/posts/first.html
 :ATOM_LINK: https://example.org/posts/first.html
 :ATOM_UPDATED: [2026年02月12日]
 :ATOM_PUBLISHED: [2025年11月23日]
 :ATOM_SUMMARY: A short teaser shown in feed readers.
 :END:
 Body text here becomes =<content type​=​"html">=.

Export via the menu (C-c C-e a) or programmatically:

 ;; To a file (e.g. feed.xml):
 (org-atom-export-to-atom)
 ;; To a buffer for inspection:
 (org-atom-export-as-atom)

Or as an ox-publish publishing function:

 (add-to-list
 'org-publish-project-alist
 '("my-feed"
 :base-directory "~/blog/"
 :publishing-directory "~/blog/public/"
 :include ("feed.org")
 :publishing-function org-atom-publish-to-atom))

Each .org file in a directory is an independent post. After exporting the files to HTML, call org-atom-write-feed to assemble the feed:

 (org-atom-write-feed
 :file "public/feed.xml"
 :title "My Blog"
 :id "https://example.org/"
 :link "https://example.org/"
 :self "https://example.org/feed.xml"
 :authors '(:name "Alice" :email "alice@example.org")
 :entries (org-atom-entries-from-files
 (directory-files "org/posts" t "\\.org$")
 :base-url "https://example.org/posts/"
 :html-dir "public/posts/"
 :exclude-drafts t))

This is the recommended approach when using ox-publish for a blog with one post per file; call org-atom-write-feed from a :completion-function in your posts project.

These #+KEYWORD: lines go at the top of your feed .org file.

These go in the :PROPERTIES: drawer of each top-level headline.

Org tags on the headline (* My post :tag1:tag2:) become <category term​=​"..."/> elements automatically.

Sub-headlines are delegated to the HTML back-end and included in <content type​=​"html">.

These keywords are read from each individual post .org file by org-atom-entries-from-files.

Top-level Org tags in the file become <category term​=​"..."/> elements.

Wherever a text construct is accepted (:title, :subtitle, :summary, :rights, and feed-level equivalents), you may pass:

Wherever a person construct is accepted (:authors, :contributors), pass a plist with:

A list of such plists produces multiple <author> / <contributor> elements. Author strings of the form "Name <email>" are parsed automatically when read from Org keywords and properties.

Wherever a link is accepted (:link, :self, :links), pass a plist with:

The :link and :self shorthand arguments also accept a plain string, which is wrapped in the appropriate rel and type attributes automatically.

The :content key of an entry plist accepts:

M-x customize-group RET org-atom RET