You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Their repo description "Portable Text is a JSON based rich text specification for modern content editing platforms."
I'm curious if the core team has seen/considered it? Maybe it could be interesting to collaborate as I think they're also still pre v1 and looking into what works, what's missing etc, feedback could help them too, maybe even get them interested in adopting lexical for sanity or elsewhere and they already have tooling around rendering for react, vue, svelte and other languages, it seems there's potential for it to become something in the likes of unifiedjs
Tho regarding my initial question about HeadingNode, they are also not exactly clear about best portable representation of headings, portabletext/portabletext#5 has interesting thoughts
Also just stumbled upon this issue portabletext/portabletext#17 about making it more compact, which I think could be great for saving bandwidth, storage and be a little addition in making things more eco-friendly 🌱
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Asked couple weeks back on Discord about "why do HeadingNodes not store their level directly as integer level prop but only as tag like h2, h3?"
I totally forgot about Portable Text which I came across couple years ago I think and just today re-discovered after reading https://www.smashingmagazine.com/2022/02/thoughts-on-markdown
https://github.com/portabletext/portabletext
Which I think is currently mostly developed and used by Sanity CMS
Their repo description "Portable Text is a JSON based rich text specification for modern content editing platforms."
I'm curious if the core team has seen/considered it? Maybe it could be interesting to collaborate as I think they're also still pre v1 and looking into what works, what's missing etc, feedback could help them too, maybe even get them interested in adopting lexical for sanity or elsewhere and they already have tooling around rendering for react, vue, svelte and other languages, it seems there's potential for it to become something in the likes of unifiedjs
Tho regarding my initial question about HeadingNode, they are also not exactly clear about best portable representation of headings, portabletext/portabletext#5 has interesting thoughts
Also just stumbled upon this issue portabletext/portabletext#17 about making it more compact, which I think could be great for saving bandwidth, storage and be a little addition in making things more eco-friendly 🌱
Beta Was this translation helpful? Give feedback.
All reactions