Org Web Adapter

Editing pages/blogging_in_emacs.org

:PROPERTIES:
:ID:       b2a7bd38-1502-4dc7-96c7-1a8b6765efb1
:END:
#+TITLE: Blogging in Emacs

- tags :: [[id:3ad0bd94-3b04-40ea-9beb-01b10f650872][Emacs]]

* ox-hugo
- This is what a I currently do
- I like being keeping all posts in an org mode tree, but I can see the value in
  per-file posts as well
- My posts are not usually terribly long, but perhaps I should try to change that
* Pure emacs bloging?
- Note taken on [2020-10-25 Sun 00:23]
  The real question here is whether a blog should live in a separate repo or be some how kept track of via my org files. I kind of like the idea of keeping specific topic blogs elsewhere, and leaving long-form posts from Roam to be exported into a separate subdirectory of unblink. I need to think about this structure a bit.

With this format, new topic-focused blogs can be introduced at subdomains with very little effort, and folks can subscribe to RSS feeds for ones that make sense to them. Right now I think I see:

+ /verse - what unbl.ink currently is
  + /blog - occasional and random observation posts
  + /emacs - topics on emacs configuration and projects
  + /running - topics on the nature of running
  + /baking - I don't think enough about what I do for this to make much sense

What if I setup a PixelFed federated account where I just post pictures of my bread?

https://opensource.com/node/61211