3 ms·
Some content tools have to be for the many and not the few. Technical writing for example is very regularly done by non technical people who are very astute wi
by j45 3y ago
Some content tools have to be for the many and not the few.
Technical writing for example is very regularly done by non technical people who are very astute with processes, steps, input and output parameters. Kind of like a power user who can also simplify and explain.
Writing things only for a personal kanban or notebook makes it harder to invite, request or actively have some collaboration. I’m increasingly using the kanban in gitlab for this reason - there are decent enough mobile apps, and it’s ready and actionable.
- spondylosaurus 3y ago> Technical writing for example is very regularly done by non technical people who are very astute with processes, steps, input and output parameters. Kind of like a power user who can also simplify and explain. While true, the tides are turning a bit here, at least for software technical writers. It's not uncommon to have a docs-as-code documentation toolchain where you're hosting all your docs in GitHub and serving them via static site. And most of the technical writers using these toolchains have no formal background in CS or previous programming know-how—myself included. Back in the day I earned an English degree and now I'm managing PRs, generating OpenAPI files, and building out CSS/React to customize our docs site :P