Most people who publish online don’t hold the master copy of their own work. The posts live in a platform’s database, the formatting lives in its editor, and leaving means exporting whatever the platform lets you take. Owning your content means reversing that: the original is yours, and platforms get copies.
What “owning” means in practice
- You hold the original. The source of your writing is a file you control, not a record in someone else’s system.
- It’s in an open format. You can read and edit it without the platform, today and years from now.
- You can move. Changing tools is a matter of pointing a new one at the same files.
What you risk when you don’t
- Lock-in. Content that only exists in a platform’s editor is hard to take elsewhere intact.
- Policy and pricing changes. The terms under which your work is published can change without your input.
- Shutdowns. Services close, and exports are not always complete.
- Format loss. Rich formatting stored in a proprietary format may not survive an export.
None of this means platforms are bad — they do real work: hosting, design, payments, discovery. The question is who holds the original.
Practical steps
- Write in plain text. Markdown files open in any editor and convert cleanly to the web.
- Keep your files where you choose. Your disk, a synced folder, a Git repository.
- Back them up like any other file. Plain text is small and easy to copy.
- Publish copies, not originals. Use tools that read your files instead of asking you to move them in.
How Sentilis fits
Sentilis publishes Markdown files you keep on your computer. You write in Obsidian, Typora, VS Code or any editor; the Sentilis CLI or Obsidian plugin publishes the files; your originals stay where they were. To change a page, you change the file and publish again.
Owning your content is also the idea behind local-first software — and the reason Markdown works well as a portable format.