RED HAT
An internship like no other.
Piloted a new system of UX writing at Red Hat and embedded within a global apps team to guide copy, UI decisions, and design reviews.
Wrote thought leadership articles, web content, product info, tweets, and Medium submission guidelines; migrated the PatternFly blog; tracked metrics and responded to team requests.
SAMPLE OF WORK
Thought leadership articles: Medium & RH blog
Published blogs on UX design & design thinking
Statistics updated 6/24/25
Website editing: PatternFly Design Guidelines
Used GitHub and markdown on Visual Studio to edit copy for brevity, clarity, and usability
Typography guidelines
Example:
Use our typographic styles to communicate visual hierarchy. A consistent and logical hierarchy provides a clear pattern for users, making it easier to quickly scan and understand information on a page.
↓
Use typography to create visual hierarchy. A consistent and logical hierarchy makes it easier for users to quickly scan and understand information on a page.
Example:
Let users know when a login field submission results in an error. Always present error states on the login screen, and use inline errors whenever possible. The error state you use will depend on whether the validation happens on the client or the server.
↓
Always present error states on the login screen if a login field submission results in an error, and use inline errors whenever possible. The error state you use will depend on whether the validation happens on loss of focus (the client's end) or submission (the server's end).
Blog Migration: PatternPast
PatternPast blog migration from Wordpress to Medium
Submission guidelines
Instructions for contributions to open source projects
Product writing: AMQ Internet of Things setup
Microcopy improvements made to 35 components of the set up process for Red Hat's AMQ (Advanced Message Queuing) IoT (Internet of Things)
TOOL TIPS
Microcopy on tool tips to help users understand complicated processes and descriptions.
Example: The system uses default properties to add metadata to messages sent by the device.
Product writing: OpenShift 4.7 guided tours
Creating and improving to familiarize new users with the Developer perspective in the OpenShift 4.7 update
RENAMING TOURS
Guided tours on OpenShift were initially called "getting started." To create a name that was more recognizable and understandable for users, I initiated a change to have the name surveyed by the research team.
Product writing: OpenShift 4.6 Quick Starts
Microcopy improvements made through iterative, multi-team Google Doc editing to seven quick starts (embedded product feature walkthroughs). Edited for clarity, consistency, and usability.
QUICK START #1: SETTING UP OPENSHIFT SERVERLESS
Four panels edited
Renamed to become holistic
Copy improved for clarity
Added failure messages and documentation
Adhered to documentation standards with links and interface components
(Image is existing copy; the text besides it are the improvements)
Product writing: Eventing terminology
Defining terminology for OpenShift 4.6
A RESEARCH-BASED APPROACH
Alongside a designer, I used several pages of research to create succinct and holistic definitions for terms used in the eventing processes.
Product writing: Warning messages
Confirmation dialogues for OpenShift 4.6
A RESEARCH-BASED APPROACH
Edited four confirmation dialogues to succinctly
and clearly alert users of action repercussions.
Social writing: Tweets
Tweets composed and coordinated for the now-defunct Red Hat UXD Twitter account
Tweet process
-
Queued tweets in a collaborative Google Sheet
-
Balanced UX topics: design, development, research, and writing
-
Balanced methods: External articles, quotes, tips, and occasionally Red Hat announcements
