Post

Andri Óskarsson
@andri.dk

I've tried migrating my blog to a CMS multiple times, but always end up going back to Markdown files. Then it occurred to me that my PDS is the perfect place to store this stuff. I don't need to host anything, but I can if I want to. So, I'm working on "atcms" in my spare time. #atproto

Andri Óskarsson
@andri.dk

I never built a CMS in the 2000's like everyone else. So here goes 🙃 - Browser only (no backend to run) - Syncs through service worker - Built-in layouts for CMS related collections - Supports all lexicons (fallback if no layout) - Asset previews/browsing

Andri Óskarsson
@andri.dk

I still haven't figured out how to handle Markdown since every other publishing provider is using a custom rich text schema. I'm open to suggestions. Right now I'm leaning towards publishing my own lexicon.

0 reposts3 likes

boltless
@boltless.me

Every implementation has their own spec. Even if you follow exact CommonMark or GFM or both specs (idk how that's even possible but some do), there is something called *extensions* which creates N dialects of each of those spec. So you should really specify "which markdown" when you say markdown.

Swipht Group
@swiphtgroup.bsky.social

Publishing your own lexicon feels like the cleanest way to keep Markdown as the source of truth and still round-trip. Are you mainly aiming for other AT clients to render it, or for your own publishing pipeline to stay in control?