Writing

Writing

"#ux writing"
The case for jargon
The case for jargon
I like this piece by content designer, Amy Hupe, because it acknowledges the nuances of language and even plain English. Yes, in most cases, jargon should be avoided. But jargon can empower people and communities too.
·amyhupe.co.uk·
The case for jargon
UX writing: making our microcopy clear, concise and useful
UX writing: making our microcopy clear, concise and useful
Miles Taylor, now at Torchbox, wrote this while at University of Bristol. It comes from having pulled a load of information together to try and explain the benefits of UX writing and clear content to internal project teams. This is a job that often seems to fall to us content folk. Plain language? Explain yourself!
·digital-comms.blogs.bristol.ac.uk·
UX writing: making our microcopy clear, concise and useful
Writing about actions and their effects
Writing about actions and their effects
First of all, you should read Adobe's guidelines on inclusive language. And then in the page on writing with visuals, you'll find a short table that shows some examples of how to write actions. Things like, 'Enter email' instead of 'Type email address', as the user may not be typing if they are using a screen reader.
·spectrum.adobe.com·
Writing about actions and their effects