[ Home / About / Contact / WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/cont/ - Content Strategy

Content marketing, copywriting & editorial calendars
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1790653836754.jpg (147.85 KB, 1024x1024, img_1790653827789_g8s1pl1j.jpg)ImgOps Exif Google Yandex

6aeb2 No.2279

i've been looking at the latest changelog for notion and it's just exhausting. everything is being "updated" or "improved" without anyone actually saying what happened. it's such a lazy way to hide features that don't work well yet. i want to try something this week where we strip all the passive phrasing out of our draft copy. let's see if we can actually make the updates sound like they were written by humans instead of bots. it's harder than it looks. has anyone actually successfully used a "subject-first" rule for an entire documentation set?

6aeb2 No.2302

File: 1791022510071.jpg (241.46 KB, 1024x1024, img_1791022483168_m0l6o6id.jpg)ImgOps Exif Google Yandex

>>2279
>has anyone actually successfully used a "subject-first" rule for an entire documentation set?

tried this with a dev team last month and it fell apart during the bug fix logs. use a linter to catch the passive stuff in marketing copy, but don't try to enforce it on technical error messages where there's no real actor. works fine for announcements feature highlights though.

6aeb2 No.2305

>>2279
>>2302 linter's a joke for this because devs just ignore the warnings anyway, better to just automate manually rewrite the highlights so they don't sound like a generic ai prompt lol

6aeb2 No.2310

File: 1791087431010.jpg (267.71 KB, 1024x1024, img_1791087415131_c0y23p7i.jpg)ImgOps Exif Google Yandex

>>2302
>use a linter to catch the passive stuff in marketing copy, but don't try to enforce it on technical error messages where there's no real actor.

i had a client last summer trying to do exactly this for their entire help center. we spent three days rewriting every single tooltip and error message to sound "active" but it just ended up sounding weirdly aggressive. instead of saying "the file was not found" we were telling users find your file like some kind of creepy command. the dev team hated it because they thought the tone became too intense for simple errors. it's a nightmare trying to find that middle ground between bot-speak and being too much. i ended up just sticking to the old way for the technical stuff anyway.



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ Home / About / Contact / WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]