org-du VS lazyblorg

https://github.com/novoid/org-du is a really simple parser to extract some basic information on headings and their number of lines.

Another method is used via Memacs filename module: it generates a text file with all files that start with a date- or time-stamp. This file can then be used for all sorts of workflows for retrieving files. For example, this is how I include images in my blog using lazyblorg and its "Smart tsfile Image File Search".

For my own Python tools, I wrote multiple naïve parsers myself (not following the usual lexical/syntactical parsing model from the books) in order to get something working. While my parsers are not considered general purpose parsers, they get the job done on my side. You might take a look at https://github.com/novoid/lazyblorg/blob/master/lib/orgparser.py for a dirty but fairly complex example. It's also using pypandoc as a fall-back for stuff I didn't parse on my own. It runs my static web blog generator.

Minimal preferred? Then lazyblorg might be an option, although it's just a works-for-me project with a few restrictions such as an empty line between different syntax elements like a paragraph and a list.

Between the first idea and the actual start of the implementation of lazyblorg there was a time span of several years. ;-)

My website is generated by lazyblorg which is using DuckDuckGo for searches. A query looks like that:

Shameless plug: I blog about Emacs but since I was too lazy to implement topic-specific feeds yet, you could add my general feed to get my Emacs-related articles as well. I'm sure that decent feed aggregators are able to filter for specific topics/words.

When your focus is "fast and easy creating a blog entry anywhere in my Org files" and you don't have special needs for JavaScript-foo, you might love https://github.com/novoid/lazyblorg which I built for https://karl-voit.at/

I've seen Weblorg, which is Native Elisp, but rewrites me to create a new file for each blog-post. Then there's Lazyblorg, but it's written in python, and also searches across all your .org files, not just a single one.

Therefore, I implemented my own (very naïve and nasty) Org parser for lazyblorg.