Introduction to the New Format

This is a test article written in Markdown instead of JSON. The goal is to make content authoring much simpler and more natural.

With this approach, you can write content using standard markdown formatting:

Why Markdown?

Markdown offers several advantages over pure JSON:

Natural writing flow - no need to escape quotes or worry about JSON syntax
Better version control - diffs are actually readable
Editor support - syntax highlighting, spell check, preview all work out of the box
Faster authoring - focus on content, not structure

"Moving to markdown reduced our content authoring time by 70% and made it accessible to non-technical team members"

Jane Smith

While most content is plain markdown, we can still embed complex elements using JSON code blocks. This gives us the best of both worlds.

Here's a regular markdown code block:

const pim = new PIMClient({
  apiKey: 'your-api-key'
});

const products = await pim.getProducts();

And here's a more advanced code element with additional metadata:

javascript

const pim = new PIMClient();
await pim.enrichProduct(productId, {
  description: 'Enhanced product data'
});

The old way required writing everything in JSON with escaped quotes and careful syntax. It looked like this:

{
  "content": {
    "en": "This is a **test** with [links](https://example.com)"
  }
}

The new way is just natural markdown:

This is a test with links

Much better!

Comparison table data is incomplete. Please check the content configuration.

This prototype demonstrates that we can maintain our structured content system while dramatically improving the authoring experience.

The parser transforms these markdown files into the existing JSON schema at build time, so no changes are needed to the rendering components.

Ready to make content authoring great again!