Accepted, Not Yet Planned

The idea of supporting a standardized data format for headless approaches aligns with our plans.

However, the core of the system, publishing, and the exposed APIs are based on an existing stack and standards (XML, XHTML, JSON, etc.).

In the latest versions of the Content Delivery APIs, implementers can further manipulate and transform responses over the GraphQL end-point.

This idea is marked as not planned, meaning it may still be a useful and interesting idea, but we don't have immediate plans to adopt a new field type based on mark-down. We may consider mark-down-like keyboard shortcuts if interesting to editors.

Feel free to comment or vote according to how you feel about markdown as a Content Manager-side storage format for rich text.

Add a markdown field

Adding a markdown field will make the lives of content editors and developers much easier imho.

Markdown also allows for custom plugins. Which delivers a specialized way of handling content in markdown fields.

A markdown field could show live preview of how the content could look like using a js parser (Also XPM ;)). 

Thijs Borst
Parents

  • Hey Thijs,

    Thanks for your suggestion!

    Could you explain why Markdown could make the lives of content editors and developers easier? Do you have a couple of example use cases?

    At the moment we are investigating improvements to RTF editing and this can provide some valuable input relating to this topic.

Comment

  • Hey Thijs,

    Thanks for your suggestion!

    Could you explain why Markdown could make the lives of content editors and developers easier? Do you have a couple of example use cases?

    At the moment we are investigating improvements to RTF editing and this can provide some valuable input relating to this topic.

Children
No Data