MDX translation with Crowdin

MDX is a natively supported file format, you can use it without an additional installation. Just upload it to your projects and start the localization.

Available Configurations

The MDX file format can be configured to optimize its use with Crowdin for better content handling. The following is a list of available configuration options.

• Change file type (only for MDX(v1)).

• Enable content segmentation.

• Custom segmentation rules.

• Exclude code blocks.

• Excluded front matter elements.

File Format Details

Sample File

# Crowdin *MDX* Sample

The paragraph with font styles: a **bold** word, an _italicized_ word, and a ~~strikethrough~~ word.

Below is an example of JSX embedded in Markdown. <br />

<div style={{ padding: '10px', backgroundColor: '#43a047' }}>
  <h3>JSX Example</h3>
</div>

Translating MDX

Note: By default, MDX files are uploaded as MDX(v1). To upload MDX as MDX(v2), use API or CLI specifying the localization type: "mdx_v2". Alternatively, go to the project Settings > Parser configuration, open the MDX(v1) parser settings and select MDX(v2) for the Change file type option.

Sample of MDX with YAML Front Matter

---

layout: article

title: Article Title

---



# Level 1 Section Title



The paragraph.

Sample of MDX with TOML Front Matter

+++

date = 2077-01-01T03:22:45-02:00

draft = false

title = 'Article Title'

weight = 10

[params]

  author = 'Michael Ross'

+++



# Level 1 Section Title



The paragraph.