Toimituspolitiikka

Viimeksi tarkistettu:

This page explains how TTSWP creates, reviews, and updates the content on ttswp.com. We publish it because trust is built on transparency, not on claims, and because both readers and AI search engines need to know how to verify what they read here.

Scope

This policy applies to every public-facing piece of content produced by TTSWP. That includes blog posts, product documentation, marketing pages, changelog entries, and any FAQ or comparison page on ttswp.com. It does not cover customer-generated content like audio files our plugin produces from your own posts.

How articles are created

Every article starts with a topic and an outline drawn from real questions our customers ask. Articles are drafted with AI tools and reviewed by Thomas Alling, founder of TTSWP, before publication. The review pass is where we add real product knowledge, flag claims that need a citation, and rewrite anything that sounds generic or marketing-driven.

Nothing publishes until that review pass is complete. We do not auto-publish AI drafts.

Approved AI tools

We use a small, deliberate set of AI tools and disclose them here so readers can judge our process.

  • Drafting and editing - AI tools for first drafts, restructuring, and outline work
  • Translation - AI tools with our own glossary and locale-specific style guides
  • Audio narration - the TTSWP plugin itself, running on the same ElevenLabs-powered engine our customers use
  • Image inspiration - reference boards in Figma and brand-aligned stock from Unsplash, never AI-generated images of people or products

In practice, "AI tools" here covers ChatGPT, Claude, Gemini, and Perplexity, used interchangeably depending on the task. We do not name specific model versions because they change often. The tool category and the editorial process around it matter more than any version number.

Fact-checking

Every claim, statistic, and code example is verified before publication. Statistics link to a primary source we have read directly. Code samples are tested in the WordPress version and the browser they target. Plugin behavior claims are checked against the current release of TTSWP.

If we cannot verify something, we remove it or rewrite it as a clearly labeled opinion or first-hand experience. We do not paraphrase numbers from SEO aggregator sites.

Audio narration

Every blog post on ttswp.com includes an MP3 narration generated with the TTSWP plugin itself. We use the same ElevenLabs-powered engine our customers use, with no special settings or premium voices we hide from the product. If you can hear it on a TTSWP blog post, our customers can produce the same result on their own WordPress site.

This is intentional dogfooding. Every regression in voice quality, pacing, or audio file size shows up in our own publishing workflow before it ships to customers.

Citations and sources

We link to primary sources and skip aggregators. That means W3C and WCAG specs for accessibility, MDN and browser vendor docs for web behavior, official ElevenLabs and WordPress documentation for product details, and peer-reviewed papers when we cite research. We avoid linking to SEO blogs that summarize other SEO blogs.

Every external link uses a standard anchor tag with no hidden redirects. The only affiliate link on this site is our ElevenLabs partner URL, which we use because we genuinely recommend the engine our plugin runs on.

Privacy and customer data

TTSWP customer data is never sent to AI services for training or analysis. Editorial drafting only uses publicly available information and our own product knowledge.

The text our plugin processes for audio narration on customer sites passes through ElevenLabs only at generation time. It is not retained by us beyond the cached MP3 file we store on the customer's behalf.

Corrections

If you spot an error, email [email protected] and we will fix it within two business days. We update the article in place and add a date-stamped note at the bottom describing what changed and when. Major corrections also get a separate entry in our changelog.

We do not silently revise articles. The web archive should show our edits, not our cover-ups.