Voice and bylines
Describe your own voice, tune tone and style, and publish under real named bylines and an editor of record.
Every domain writes in a voice you set, not a generic default.
Describe the voice you want
There is no list of house styles to pick from. Describe the voice in your own words, name the audience it is written for, and add your own banned words and any standing instructions the writer should follow on every article.
Tune the details
Alongside that, set tone, reading level and point of view - preset pickers available on every plan - so every article reads like your publication wrote it, not a generic model with the volume turned down.
Worth knowing where the line is: these are instructions to the writer, not filters applied to the finished draft. The no-em-dash rule and the link allowlist are enforced in code after the draft comes back; a banned word is not, so one can still slip through.
Real bylines, and someone accountable
Articles publish under real named bylines, not an anonymous "staff" tag. Name as many authors as you like per domain and pick the byline per article in the editor; leave it unpicked and the article publishes under the domain's editor of record, the one person accountable for that publication.
Your voice travels with you
Switch your CMS destination later and your voice configuration stays exactly where you left it - templates, tone, and bylines all carry over. There's no reconfiguration tax for changing where the finished articles land.
Related: Quality gates and fact-checking · Languages