Samuel
this is the result of me taking Opus 4.8 for a test drive. conclusion: pretty good! currently it only supports markpub.at, but I'd like to support more richtext formats in future. and maybe even make my own one?
1 18
Samuel
future things I may or may not do - allow setting up a publication from scratch. currently it assumes a preexisting format - more richtext formats! - I lowkey wanna make my own one - more standard.site fields like contributors, bskyPostRef - more publish-y features like previewing the bsky embed
2 12
Jack Platten
fun fact: i was actually looking for something exactly like this, and the local development I was working on was tangly. so I canceled my plan to do the "main" storage of my site being in @standard.site, but i was struggling with getting it to work right so I rolled back the plan
2 1
Jack Platten
now you nerd sniped me and I almost want to try moving it back to being loaded like that
1
Jack Platten
like my search history includes a lot of “batteries included markdown editor” “how to store markdown content”
leah 🛸
it's very intentional not to standardize the rendered content precisely because it allows much variation in how content is organized and structured. you can make a lexicon that is just a string of html content, or you can store it as a json block format with facets and so on
1 1
Kevin Marks
I know that's the goal, but it is an interop failure. As you have a textContent, why not have an htmlContent? We have a rich text representation standard already with billions of active clients.
1