WEBSITE EDITING
Content editing for various local businesses and the PatternFly design guidelines.
LOCAL BUSINESS WEBSITE EDITING & CREATION
Edited content for the "About" page:
​
restructured and reorganized
edited existing content for clarity, brevity, and persuasion
created new, compelling content to captured voice, tone, and brand
highlighted facets of company (new physical location, catering, chef bios, and nonprofit foundation)
Edited content for landing page, "Essential Oils Statement," "Land Acknowledgement," and about page ("Shiny & The Farm"):
​
created snappy, voice-driven blurbs for landing page
edited "Essential Oils Statement" and "Land Acknowledgment" for tone, clarity, and brevity
centered voice and tone for about page
held extensive interview to infuse personality into the site
helped restructure website for better user movement
Created "Peer Groups" page from new and existing content:
​
combined four pages into one
complete layout overhaul; restructured for organization, clarity, and efficiency of reading
edited existing copy for clarity and brevity
added content to highlight program details and benefits
Created wholly new content for home, "Fencing & Decking," "Landscaping," and "Hardscaping" pages.​
​
Dictated page layouts and used SEO writing to ensure pages would be easily findable on the web.
PATTERNFLY DESIGN GUIDELINES
via Red Hat
Editing copy for brevity, clarity, and usability.
​
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.
Editing copy for brevity, clarity, and usability.
​
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).