notion-to-md VS Lektor

This is very cool! I recently started managing my Astro site content with Notion as a CMS, thanks to `notion-to-md` [1] and `@notionhq/client` [2] but media management is a hassle.

I had been planning to re-host Notion media files to Cloudflare R2 and rewrite content, but it might just be simpler to use Pages CMS due to built-in R2 support.

But also, I like using Notion apps on the go. Hmm.

[1] https://github.com/souvikinator/notion-to-md

I’ve never used it, but there’s a Notion to Markdown converter on GitHub: https://github.com/souvikinator/notion-to-md

Notion works with content blocks. Each paragraph and each formatted section is a block on its own. Fetching that from Notion gets me a load of nested objects that are cumbersome to work with. I'm using NotionToMarkdown to take care of that. This will give me a markdown string from a Notion page that's easy to work with. Beware it’s just a markdown string, though. Using it in a template will output the unrendered string. But if we put that into a markdown file, from which eleventy will generate pages, it will also render the markdown string to HTML.

One can add custom parsing logic for specific blocks. More details here

Thanks to everyone for using notion-to-md and actively contributing and reporting issues. It has now 200+ stars on GitHub and 1000+ weekly downloads on NPM.

Haven’t done that myself, but I do know there’s a Notion to markdown converter that seems like it might be worth checking out.

Github: https://github.com/souvikinator/notion-to-md

Guess I'm one of the annoying users who complained when armin's Lektor (https://github.com/lektor/lektor) started going dormant back when, but I loved it for a while. I'm on Astro now, but a big thanks for helping a younger version for me.

Lektor is a modern and flexible static content management system that utilizes Python as its core language. It comes with an intuitive web-based admin interface, making it easy for content creators to manage and update the site. Lektor supports a variety of content types and has an active community that contributes to its continuous improvement.

Lektor CMS is sort of a prototype-ish thing doing this: https://www.getlektor.com/

It has (used to have? Can't find them on the site now) pre-packaged binaries that you would drop into a folder structure generated by the technically-minded person, and the content editor can simply click on that binary, which opens the backend of the CMS in the web browser, make changes and click deploy.

There have been several Flask-based CMS's but I don't remember most of them. IIRC Lektor is based on Flask.

Static hosting could be enough for many sites and one could combine the technical and UX advantages of your dynamic interface with the advantages of static sites for security and distribution.

I found that useful when i worked with https://www.getlektor.com/ years ago. In lektor the dynamic part runs on a users desktop machine, but it of course wouldn't need to.

Lektor is Python based and Just Works, but it is far off the beaten track… https://www.getlektor.com/