![]() ![]() Add layers of content to your text, like comments, footnotes, highlighting, translations, and let the consumer choose which layers they want to get out of the API.Don’t put maps in your copy, put a long/lat, and a zoom that you can render as a static map on mobile and a slippy map on the desktop. Embed editable data as drag-and-droppable blocks in inline text.The specification can be found on and we have open-sourced all the frontend tooling for it. When building Sanity we made Portable Text a priority as it allows for familiar editorial word processing experiences at the same time as producing data structures that easily can be translated and adapted to different uses. We needed to save and structure content in a much more versatile way. They are two perfectly good syntaxes that we love and use ourselves, but they both come with limitations that would put heavy constraints on Sanity as a headless platform. This is why we didn’t use a WYSIWYG rich text editor that stores either HTML or Markdown. How do designers control what formatting is allowed, where?. ![]() How do you display your rich text in different technologies?.How can you write software to transform text that isn’t structured?.This leaves you with a series of problems though: How do you represent it? How do you make it easily editable? How do you render it? People can just learn markdown, right? It’s tempting to just pass up on the challenges presented by handling rich text as structured data. ![]()
0 Comments
Leave a Reply. |