I stopped blogging several years ago. Over the last few years, I've been writing plenty of private essays. However, very recently I have been considering starting to publish my writing and, well, start blogging again publicly. I have no desire to waste time on templates, look-and-feel, visual stuff, etc. I just want to write a bog-standard html file, and then publish it...I do value leveraging html elements that help with meta data (e.g. microformats, etc.), but don't care about how things look - and these elements that i value are all invisible to most users anyway. I would be fine with just crafting html by hand, deploying it via sftp or some boring deployment pipleine, and that's it. But, then, I started thinking: what about having an RSS/Atom feed? I used to consume content via an rss reader, but have not done so in years. But, I don't want to manually craft that feed file; nope, sorry. But, I've heard a comment or two from acquaintances that rss/atom feeds and syndication are really something that people - like my potential audience - might really desire. So, I should really consider having one. This means that either I have to craft several things manually (from the blog post itself, the list of archived posts, the feed file, etc.), or use a static site generator that will handle all this for me, etc. I don't want to get trapped down a rabbit hole where I am spending so much on the tooling, the scaffolding, twiddling with templates, or the publish process itself. I just want the minimal for writing and publishing, I want it to live on my domain name, and that's it. Am I crazy or extremely lazy for not wanting to generate an RSS/Atom feed file?

So, here's my ask of you all nice people: are feeds like RSS/Atom feeds even worth it? If so, does anyone have recommendations for a manual process where i can craft the blog post's html by hand, but somehow leverage a portion of a static site generator (or some minimal tool) to only automate the creation of the RSS/Atom feed file? Thanks in advfance for any constructive feedback!

P.S. - One thing that re-ignited my desire both to write more in public, and keep it alive with minimal fuss was my re-reading of Jeff Huang's excellent "This Page is Designed to Last" post: https://jeffhuang.com/designed_to_last/

:wave: everyone, I've been thinking about where to put non-technical blog posts and what to call them since, so far, I have bookmark/, cheatsheet/, howto/, note/, snippet/ and tutorial/ folders already[1].

I think those cover most of the things I like writing about and I intend to share, but I also enjoy poetry, analyzing movies, political commentary and writing an essay here and there.

Following from that, I kept essay/, poem/ and commentary/ around for whenever I felt like sharing some of my non-technical writings, but I don't like those folders :smile:. They seem way too granular, more akin to tags than categories, both of which are contained in each file's metadata.

Tags, however, don't feel like a "pillar"/category of a Zettelkasten/ramblings/thoughts crate. They're empty at the moment and in draft/, so it's the perfect chance to do some re-structuring and avoid the issues I faced when I ditched blog/category and chose the current structure.

In case you're asking yourself why I didn't put everything in the same folder, as they reflect categories and each .md file has category metadata already, it's because the drafts in draft/ became unmanageable (+120). So, in an effort to give myself an easier way to navigate and edit, I decided /folders were going to reflect the categories that existed. I'm aware it can be that after note #50 or something I have the same problem, and thus it wouldn't have made a difference whether notes were together with tutorials or not. I've decided to deal with that problem when it arises :)

I'd be very interested in hearing your thoughts! Would you keep essay/, poem/ and commentary/ or merge them into something else? note/ are short and wouldn't feel right for longer ramblings. I am not a big fan of writings/ as everything is a "writing", prose/ also doesn't quite fit and so far the only one I've sort of liked is reflection/ since essays, poems, and comments on happenings are the result of reflecting.

/rant over, I know, I'm overthinking it. Let those not guilty throw the first stone :)

[1] I've removed quite a bit of the irrelevant stuff but kept what I believe is relevant, but feel free to ask away in case something necessary is missing.

.
├── bookmark/
│   └── sample.md
├── cheatsheet/
│   ├── sample.md
│   └── sample.md-data
├── commentary/
├── draft/
│   ├── bookmark/
│   │   └── sample.md
│   ├── cheatsheet/
│   │   └── sample.md
│   └── ...
├── essay/
├── extra/
│   ├── archive/
│   ├── blob/
│   └── robots.txt
├── howto/
│   └── sample.md
├── note/
│   └── sample.md
├── poem
├── private/
│   └── sample.md
├── snippet/
│   └── sample.md
└── tutorial/
    ├── sample.md
    └── sample.md-data/
        ├── sample.png
        └── ...

I used to use a random FOSS Python program to manage my blog. The software honestly wasn't the best (partially my own fault for not setting it up super well) and I stopped using it, lost my blog's source code, and haven't updated the blog in a long time because of that. So I'm looking for a static site generator that is simple, well maintained, and no-frills.