A content format is portable when you can take it from one tool to another without losing anything important. Markdown is one of the most portable formats for writing, because underneath it is just text.
What makes Markdown portable
- It’s plain text. Any editor on any system can open it. There is no binary format to decode.
- The source is readable.
# Title,**bold**and- itemread naturally even without rendering. - Tools everywhere support it. Note apps, code editors, static site generators and publishing platforms all read Markdown.
- It diffs well. Changes show up line by line in Git, which makes reviews and history easy.
Where portability breaks
Markdown has a common core and many extensions. The core travels everywhere; extensions don’t always:
- Editor-specific syntax — wikilinks, embeds, content blocks, block references — works in the app that invented it and may not render elsewhere.
- Metadata lives in front matter, and each tool names fields differently: one uses
title, anothername. - Media paths depend on where the images are relative to the file.
Keeping your files portable
- Prefer standard syntax. Headings, lists, emphasis, links, images and code blocks work everywhere.
- Use relative paths for images, kept in a folder next to the file — for example
./attachments/. - Keep front matter small. A few clear fields are easier to map between tools.
- Treat extensions as local conveniences. Use them while you think; convert them before you publish.
Portability and publishing
When the published site is built from your Markdown files, the files stay the source of truth. With Sentilis, the folder you publish is plain Markdown in the layout Sentilis expects — press/, bio/, market/ and so on — with a short front matter block per file. The same files remain readable in any editor you use next.