Post

Can you expand on the choice of block based document format over something human readable, and growing in popularity and usage because of #ai... why not Markdown? (i.e. like bsky posts, text+facets)

0 reposts2 likes

We don't define a content structure for documents. Platforms are are given the freedom to implement content in the way they see fit. For example, you could just create your own markdown lexicon, and use it in the `content` open union.

We do define a `textContent` (string) property as well, this should contain the text from the content body, used for search and I would imagine AI could easily tap into this if needed.

I understand I can do something different, in general, with lexicon. I'm curious to the choice to this specific block format for a proposed standard, over something like what Bsky did with text+facets My assumption is the choice is largely driven by the underlying pkgs/editors the apps here chose

We aren’t enforcing content type, document content can be block based, markdown, etc. Content is difficult to standardize because there are so many different ways to store it, each with their own benefits and drawbacks. The site.standard.document lexicon supports plaintext, markdown, etc.

probably bc leaflet probably? uses tiptap internally and that’s already really close to tiptap’s internal representation of data