Karl Voit

Hi, Here, we do have the issue that Org-mode is implemented in a clever way but not in a way that translates well to valid HTML/XML. For example: `Foo [[https://karl-voit.at][description*]]*...

Off-topic: I understand the issues here and implications. However, me and the Orgdown initiative are not in the position of defining something that differs from the GNU Emacs implementation of...

> > I would assume that it's a similar format to Atom (which is already implemented): a static text page that contains the most recent articles. > > Nope, you...

This can be tested with https://karl-voit.at/2017/09/23/orgmode-as-markup-only/ Please also remove workaround and workaround explanation on that page after implementing this feature.

See comment https://github.com/novoid/lazyblorg/issues/43#issuecomment-715985343 for an implementation approach!

Depends on outcome of #24 since I would like to have the full feed instead of headings-only.

Is it worth adding a new feature for this instead of doing this manually with the usual Org mode syntax elements like lists and so forth? Pro: - standardized look&feel...

Example: https://github.com/arp242/battray/blob/master/battray/__init__.py So far, I don't understand all the code here with args: ``` def source_default(): exec(open(self.default_config, 'r').read(), args) args.update({'source_default': source_default}) exec(open(self.configfile, 'r').read(), args) ```

- [x] decide: accept duplicated entries for combinations and/or URLs only? - [x] decide: only as a by-product of a normal lazyblorg generation run or also as a stand-alone feature?

An approach could be to combine this with #44 in the following way: A command line option results in multiple files generated in parallel to a normal blog generation run:...