#style guide guide

[verbagetruck]

Contribute to style-guide development by creating an account on GitHub.

Good writing is the sum of many technical decisions. 

It’s a thrilling time to be a word person. As writers become an increasingly indispensable part of the design process, we need to make the labor behind narrative more transparent—which is why I’m drafting v1 of Stellar’s voice + style guide in GitHub. 

Stellar is an open-source financial network, so it’s in our organizational spirit to be open and collaborative. We’re open about our code, and I also want to be open about how we develop voice and tone and make stylistic decisions.

Star the repo to save it, or watch it to receive notifications as the style guide evolves.

[verbagetruck]

Speaking the Same Language

How to design the voice of a product and the style guide that holds it together

In my never-ending quest to theorize about the work that i do, I've been writing a series of posts for re:form, a sponsored collection on Medium that is "a field guide to the designed world." 

The series is on narrative UX, or the role of words in product design. The first post asked, what is narrative UX? The second discussed one of the major sentiments in the industry that leads to an inconsistent narrative in products. This third piece is a style guide guide. 

How dorky do you have to be to enjoy writing style guides so much that you write a style guide guide? I fear the answer is "very," but I did it anyway. It's a difficult problem, how to design a product voice and then lay down the rules to govern it. I hope this post demystifies that process a bit.