portabletext/portabletext : Portable Text is a JSON based rich text specification for modern content editing platforms.

cy_altern @cy_altern CC BY-SA 22/02/2022

3

3

portabletext/portabletext: Portable Text is a JSON based rich text specification for modern content editing platforms.
►https://github.com/portabletext/portabletext
Portable Text is a JSON based rich text specification for modern content editing platforms.
Portable Text is an agnostic abstraction of rich text that can be serialized into pretty much any markup language, be it HTML, Markdown, SSML, XML, etc. It’s designed to be efficient for real-time collaborative interfaces, and makes it possible to annotate rich text with additional data structures recursively.
Portable Text is built on the idea of rich text as an array of blocks, themselves arrays of children spans. Each block can have a style and a set of mark definitions, which describe data structures distributed on the children spans. Portable Text also allows for inserting arbitrary data objects in the array, only requiring _type-key. Portable Text also allows for custom content objects in the root array, enabling editing- and rendering environments to mix rich text with custom content types.
#Portable_Text #rich_text #json #block #contenu_structuré

cy_altern @cy_altern CC BY-SA
- BigGrizzly @biggrizzly CC BY-NC-SA 22/02/2022
  
  #un_de_plus :-)
  
  BigGrizzly @biggrizzly CC BY-NC-SA
Écrire un commentaire
b_b @b_b PUBLIC DOMAIN 21/02/2022

6

6

Thoughts On #Markdown — Smashing Magazine
▻https://www.smashingmagazine.com/2022/02/thoughts-on-markdown
If you’re going for markdown, at least consider the following trade-offs:
– Markdown is not great for the developer experience in modern stacks
– Markdown is not great for editorial experience
– Markdown is not great in block content age, and shouldn’t be forced into it. Block content needs to
Article intéressant sur l’histoire de MD et de ses dérivés, leurs usage, etc. (avec une mention à propos des #block_content).

b_b @b_b PUBLIC DOMAIN
- RastaPopoulos @rastapopoulos CC BY-NC 22/02/2022
  
  Today, I will argue that Markdown’s primary users are developers and people who are interested in code. It’s not a coincidence that Slack made the WYSIWYG the default input mode once their software was used by more people outside of technical departments. And the fact that this was a controversial decision, so much that they had to bring it back as an option, shows how deep the love for markdown is in the developer community. There wasn’t much celebration of Slack trying to make it easier and more accessible for everyone. And this is the crux of the matter.
  […]
  The portability of content has much more to do with how you structure that content in the first place. Take WordPress, it’s fully open-source, you can host your own DB. It even has a standardized export format in XML. But anyone who has tried to move out of a mature WordPress install knows how little this helps if you’re trying to get away from WordPress.
  […]
  Ça on le dit depuis le début :
  Embedding specific presentation concerns in your content has increasingly become a liability and something that will get in the way of adapting, iterating, and moving quickly with your content. It locks it down in ways that are much more subtle than having content in a database. You risk ending up in the same place as moving out of a mature WordPress install with plugins. It is cumbersome to unmix structure and presentation.
  On retrouve ►https://github.com/portabletext/portabletext que j’avais déjà évoqué autour de SPIP il y a 3 ans :
  ▻https://git.spip.net/spip/porte_plume/issues/3720#issuecomment-21130
  #web #développement #intégration #édition #contenu #rédaction #portabilité #interopérabilité #structured_data
  
  RastaPopoulos @rastapopoulos CC BY-NC
Écrire un commentaire