-
Notifications
You must be signed in to change notification settings - Fork 17
Create ux-writer-role.md #202
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| @@ -0,0 +1,97 @@ | ||||||||||||||||||||||||||||||||
| --- | ||||||||||||||||||||||||||||||||
| sidebar_position: 3 | ||||||||||||||||||||||||||||||||
| sidebar_label: UX writer role | ||||||||||||||||||||||||||||||||
| title: UX writer role | ||||||||||||||||||||||||||||||||
| title: UX Writer role | ||||||||||||||||||||||||||||||||
| doc-type: 'banner' | ||||||||||||||||||||||||||||||||
| component-tabs: [''] | ||||||||||||||||||||||||||||||||
| no_single_tab: true | ||||||||||||||||||||||||||||||||
| description: UX writers shape the language that bring our digital products to life. Through clear, consistent and accurate microcopy (the small, functional pieces of text within a digital interface that guide, support and reassure users), UX writers help users move through complex workflows with ease. | ||||||||||||||||||||||||||||||||
| --- | ||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||
| # | ||||||||||||||||||||||||||||||||
tokyojen marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||
| ## UX writer role | ||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||
| UX writers strengthen usability, reduce friction and ensure every interaction across our software feels supportive and human-centered.<br/> | ||||||||||||||||||||||||||||||||
| They shape in product language that supports a clear, seamless and intuitive user experience. | ||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||
| UX writers strengthen usability, reduce friction and ensure every interaction across our software feels supportive and human-centered.<br/> | |
| They shape in product language that supports a clear, seamless and intuitive user experience. | |
| UX writers strengthen usability, reduce friction and ensure every interaction across our software feels supportive and human-centered. | |
| They shape in product language that supports a clear, seamless and intuitive user experience. |
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The style guide requires using the typographically correct apostrophe (β, U+2019) instead of a straight quote (').
| ### What's included | |
| ### Whatβs included |
References
- Style guide line 35: 'Apostrophe: Always use the symbol β (U+2019, "right single quotation mark"), not ''' (link)
tokyojen marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This list is not formatted correctly for Markdown. The <br/> tags are unnecessary and incorrect. Please format this as a standard Markdown bulleted list, with an empty line after it to separate it from the following paragraph.
| Integrate UX writing throughout all Scrum phases to allow product language to evolve with the design.<br/> | |
| * Sprint planning: Identify content needs and terminology early in ideation | |
| * Daily standups: Stay aligned on interaction changes that affect microcopy | |
| * Refinement: Collaborate with designers and product owners on wording decisions | |
| * Development: Ensure accurate implementation and consistency | |
| * Retrospectives: Refine the writing process based on team feedback<br/> | |
| Continuous collaboration prevents terminology gaps, reduces rework and improves clarity throughout the product. | |
| Integrate UX writing throughout all Scrum phases to allow product language to evolve with the design. | |
| * Sprint planning: Identify content needs and terminology early in ideation | |
| * Daily standups: Stay aligned on interaction changes that affect microcopy | |
| * Refinement: Collaborate with designers and product owners on wording decisions | |
| * Development: Ensure accurate implementation and consistency | |
| * Retrospectives: Refine the writing process based on team feedback | |
| Continuous collaboration prevents terminology gaps, reduces rework and improves clarity throughout the product. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The frontmatter has a duplicate
titlekey, which is invalid YAML and can cause parsing issues. Additionally, the valueUX Writer roleviolates the style guide's rule for sentence case in titles.References