<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Hello there,</p>
<p>I am pasting below a draft for our internal launch of the
guidelines -- it also exist in a pad if you have suggestions to
the text please use the pad. <br>
</p>
<p>I think it will be better to define what is Tier 1 and Tier 2
during the meeting in Seattle. I added a suggestion of how we
could be defining it in the letter but I believe it will be better
for the community to do it together there. <br>
</p>
<p>I would like to send this email by the EOW - Sept 9th. For that
we would need the guidelines :) so can someone let me know how is
that going? Is it doable to have them by EOW?</p>
<p>Here is the pad url:<br>
</p>
<p> <a
href="https://storm.torproject.org/shared/6J1Gpy7BHN8SDPHUCUCbiKtYdF7XA9BYUmFH_hLxSPi"
class="copy-me" id="share-token-text">https://storm.torproject.org/shared/6J1Gpy7BHN8SDPHUCUCbiKtYdF7XA9BYUmFH_hLxSPi</a></p>
<p><br>
</p>
<p>Here is the letter draft:<br>
</p>
<p><br>
</p>
<p> </p>
<div class="primary-author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm"
id="magicdomid2"><span
class="author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm">Hello
Tor!</span></div>
<div class="primary-none" id="magicdomid3"><br>
</div>
<div class="ace-line
primary-author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm"
id="magicdomid158"><span
class="author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm">The UX
team is happy to announce that Tor now has </span><span
class="author-a-0z67zz70zwxz81zz88zz86z8ex3jlz88ze">its first
draft of a visual</span><span
class="author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm"> style
guide! Since this is a new thing at Tor we decided to do a short
Q&A to introduce the project.</span></div>
<div class="primary-none" id="magicdomid5"><br>
</div>
<div class="primary-author-a-0z67zz70zwxz81zz88zz86z8ex3jlz88ze"
id="magicdomid6"><span
class="author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm b"><b>What
is</b></span><span
class="author-a-z81zsz69zz71zz88zz85zz89zz65zz79zz82z9ez78z5z73zz65z
b"><b> </b></span><span
class="author-a-0z67zz70zwxz81zz88zz86z8ex3jlz88ze b"><b>a
visual style guide</b></span><span
class="author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm b"><b>?</b></span></div>
<div class="primary-author-a-0z67zz70zwxz81zz88zz86z8ex3jlz88ze"
id="magicdomid7"><span
class="author-a-0z67zz70zwxz81zz88zz86z8ex3jlz88ze">Style guides
specify the look and feel of how a company or team communicates
with the outside word. For example, styleguides.io collects
examples of website visual standards that help maintain a
consistent online presence. Style guides can include rules for
how logos, fonts, and colors should be used, and can even extend
to interactive behaviors such as alerts and form templates. </span></div>
<div class="primary-none" id="magicdomid8"><br>
</div>
<div class="primary-author-a-0z67zz70zwxz81zz88zz86z8ex3jlz88ze"
id="magicdomid9"><span
class="author-a-0z67zz70zwxz81zz88zz86z8ex3jlz88ze">Style guides
are not meant to be static documents. They can evolve over time
as the needs of the organization change. However, a style guide
provides a basic set of ground rules for designing user
experiences, and provides a foundation for an ongoing
conversation about UX design.</span></div>
<div class="primary-none" id="magicdomid10"><br>
</div>
<div class="primary-author-a-0z67zz70zwxz81zz88zz86z8ex3jlz88ze"
id="magicdomid11"><span
class="author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm b"><b>Why
d</b></span><span
class="author-a-0z67zz70zwxz81zz88zz86z8ex3jlz88ze b"><b>oes Tor
need one</b></span><span
class="author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm b"><b>?</b></span></div>
<div class="ace-line
primary-author-a-0z67zz70zwxz81zz88zz86z8ex3jlz88ze"
id="magicdomid159"><span
class="author-a-0z67zz70zwxz81zz88zz86z8ex3jlz88ze">People rely
on the visual design of software and websites to help them
determine whether software is trustworthy. A project that has
many different components that all look different from
one-another can come off as disorganized or scary. In our case,
the lack of visual standardization across the Tor ecosystem is
disconcerting to many potential new users. A consistent visual
identity will make it easier for potential users to identify
"real" Tor projects (and for Tor to shut down false claims of
affiliation), in addition to making Tor seem more friendly and
approachable to new members of the community. </span></div>
<div class="primary-none" id="magicdomid13"><br>
</div>
<div class="primary-author-a-0z67zz70zwxz81zz88zz86z8ex3jlz88ze"
id="magicdomid14"><span
class="author-a-0z67zz70zwxz81zz88zz86z8ex3jlz88ze">As the Tor
project prepares to embark on a serious re-vamp of its core
website design (and other initiatives, such as one around
fundraising), the style guide will help various contractors and
volunteers create designs that look good with one another. It
will also help volunteer designers and researchers identify
places where current practice can evolve to be more streamlined
or attractive, rather than having five designers chime in with
five radically different approaches. </span></div>
<div class="primary-none" id="magicdomid15"><br>
</div>
<div class="primary-author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm"
id="magicdomid16"><span
class="author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm b"><b>What
this is not?</b></span></div>
<div class="ace-line
primary-author-a-0z67zz70zwxz81zz88zz86z8ex3jlz88ze"
id="magicdomid1187"><span
class="author-a-0z67zz70zwxz81zz88zz86z8ex3jlz88ze">A r</span><span
class="author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm">ebranding
of Tor. Or a</span><span
class="author-a-0z67zz70zwxz81zz88zz86z8ex3jlz88ze">n attempt to
get every project at Tor to think the same or work in exactly
the same way</span><span
class="author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm">.</span></div>
<div class="primary-none" id="magicdomid21"><br>
</div>
<div class="primary-author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm"
id="magicdomid22"><span
class="author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm b"><b>Who
worked on it?</b></span></div>
<div class="ace-line
primary-author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm"
id="magicdomid282"><span
class="author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm">This was
organized by the UX team with the support of Simply Secure. The
main people involved were:</span></div>
<div class="ace-line
primary-author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm"
id="magicdomid905"><span
class="author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm">Scout,
Amee, Elio, Paul L., Nima and Isabela</span></div>
<div class="ace-line primary-none" id="magicdomid412"><br>
</div>
<div class="ace-line
primary-author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm"
id="magicdomid426"><span
class="author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm b"><b>How
it was done?</b></span></div>
<div class="ace-line
primary-author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm"
id="magicdomid1155"><span
class="author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm">The
discussion to have a style guide started over an year ago with
Simply Secure, as we were talking about building the UX team we
decided that building a style guideline for Tor would be a great
first project for the team since it's such an important
foundation for a product to have. Later on at the Valencia Dev
meeting in Feb 2016 during the UX team meeting we got ourselves
organized to kick off this project. Since them we went through a
lot of meetings and steps to build it up, you can review it all
at our wiki page:</span></div>
<div class="ace-line
primary-author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm"
id="magicdomid1158"><span
class="author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm"> </span><span
class="author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm url"><a
href="https://trac.torproject.org/projects/tor/wiki/org/teams/UxTeam/StyleGuidelines">https://trac.torproject.org/projects/tor/wiki/org/teams/UxTeam/StyleGuidelines</a></span></div>
<div class="ace-line primary-none" id="magicdomid845"><br>
</div>
<div class="primary-author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm"
id="magicdomid25"><span
class="author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm b"><b>How
this affects you and other things moving forward</b></span></div>
<div class="primary-author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm"
id="magicdomid26"><span
class="author-a-0z67zz70zwxz81zz88zz86z8ex3jlz88ze">W</span><span
class="author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm">e will
have a session at the Dev Meeting in Seattle to talk about the
guidelines</span><span
class="author-a-0z67zz70zwxz81zz88zz86z8ex3jlz88ze">, discuss
these proposals,</span><span
class="author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm"> and
plan what's next!</span></div>
<div class="primary-none" id="magicdomid27"><br>
</div>
<div class="ace-line
primary-author-a-0z67zz70zwxz81zz88zz86z8ex3jlz88ze"
id="magicdomid1265"><span
class="author-a-0z67zz70zwxz81zz88zz86z8ex3jlz88ze">As noted
above, the ultimate goal of the style guide is to create a
consistent look and feel across the Tor ecosystem. To that end,
we propose that the majority of projects under the Tor umbrella
work to adopt its conventions around fonts, colors, and logo
design. However, we recognize that this may be a lot of work. We
thus propose that the process happen in several stages. </span></div>
<div class="ace-line primary-none" id="magicdomid1267"><br>
</div>
<div class="ace-line
primary-author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm"
id="magicdomid1334"><span
class="author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm">Step 1:
Present style guidelines to the Tor Community</span></div>
<div class="ace-line
primary-author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm"
id="magicdomid1461"><span
class="author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm">Step 2:
Define Tier 1 and Tier 2 projects - where Tier 1 will adopt the
guidelines and Tier2 will be left open to do it or not</span></div>
<div class="ace-line
primary-author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm"
id="magicdomid1635"><span
class="author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm">Step 3:
Start applying guidelines for Tier 1 projects.</span></div>
<div class="ace-line
primary-author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm"
id="magicdomid1634"><span
class="author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm">Step 4:
Apply guidelines for Tier 2 projects that would like to adopt
them.</span></div>
<div class="ace-line
primary-author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm"
id="magicdomid1740"><span
class="author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm">Step 5:
Make sure that new projects knows of the guidelines.</span></div>
<div class="ace-line primary-none" id="magicdomid1271"><br>
</div>
<div class="ace-line
primary-author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm"
id="magicdomid2055"><span
class="author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm">For now
our suggestion is for Tier 1 projects to be all the official Tor
websites (donation page, main page, metrics sites) and products
(Tor Browser). And for Tier 2 to be anything that is still on
Alpha or Beta such as TorBirdy, TorMessenger and so.</span></div>
<div class="ace-line primary-none" id="magicdomid2057"><br>
</div>
<div class="ace-line
primary-author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm"
id="magicdomid2329"><span
class="author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm">We are
aware that this is something that should be decided with the
broader Tor Community therefore we are suggesting the style
guidelines discussion at the Seattle Meeting. Please join us
there and help us define these Tiers and coordinate/organize an
implementation plan for those.</span></div>
<div class="ace-line primary-none" id="magicdomid2331"><br>
</div>
<div class="ace-line
primary-author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm"
id="magicdomid2361"><span
class="author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm">Let us
know if you have any questions!</span></div>
<div class="ace-line
primary-author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm"
id="magicdomid2398"><span
class="author-a-uz84zz79zz70z7v6z122zz77ziy1z69z2z71zm">Isabela
on behalf of the UX Team.</span></div>
</body>
</html>