Editorial policy
How we create, test, and maintain our content
Every article on EchoWave — every guide, tutorial, and tool page — follows the same rules: it must be tested in the real editor, kept current, and written to get you to a result. This page explains how that works.
Tested, not aggregated
Guides are written in the EchoWave editor, not rewritten from other articles. If a tutorial says a button exists, someone on the team clicked it in the current release before publishing.
Kept current
The editor ships improvements every month, and content is re-checked against product changes. Articles show when they were last updated, and outdated steps are treated as bugs: report them and we fix them.
Claims you can check
Feature statements — export resolutions, format support, language counts — are verified against the live product before they go up. If we can't verify a number, we don't publish it.
Clear about AI
English is our source of truth. The 16 other languages are translated from it with AI assistance and reviewed for terminology and layout. Where a translation is ambiguous, the English page is authoritative.
The authors
Who writes EchoWave
EchoWave's content is written, reviewed, and maintained by the EchoWave team — the same small group that designs, builds, and supports the product. We publish under a team byline instead of personal names. That is a deliberate choice: we are a small independent company and we keep our people out of the spotlight. It also means nothing here is outsourced content published under a stranger's name — every article is the responsibility of the whole company.
The team behind the content is the team behind the code. When a guide explains how subtitle styling works, it was written by people who built the subtitle engine and answer the support tickets about it. You can read more about the company on our about page.
The process
How a guide gets published
- 1
Start from a real task
Every guide starts with something people actually try to do, sourced from support conversations, feature requests, and the questions creators search for.
- 2
Do the task in the editor
The workflow is performed start to finish in the production editor. Steps and screenshots come from that session, not from mockups.
- 3
Check every claim
Numbers and feature statements are verified against the live product on the day of publishing.
- 4
Publish with a date, then keep it honest
Articles display when they were last updated. When the product changes, affected guides are updated — or corrected in place.
Corrections
If anything on this site is wrong, outdated, or misleading, email hello@echowave.io with a link to the page. Verified factual errors are corrected promptly — typically within a few business days — and material corrections update the article's last-updated date.
Accountable to you
More about how we operate
- Publisher
- EchoWave (Lemon Vault LLC)
- Contact
- hello@echowave.io
- Publishing since
- 2018
- Languages
- 17
