Open Stack

Hi Lana and team, 

Thanks for your hard work on this! It’s exciting to see it come together. 

To answer your questions, we should reach out to those governing the various operating systems logos out of an abundance of caution to ensure we have permission to use these logos. The Foundation doesn’t currently have an existing agreement that enables us to use them in this way, so each logo owner must be contacted separately. 

We also have a draft style guide available for the community to review at http://os-styleguide.netlify.com/ <http://os-styleguide.netlify.com/> - it is in draft format at this point (pending additional content and input from the community). There is a comments section on each page if you’d like to ask specific style guide related questions. 

I’m copying my colleagues Wes Wilson, who is leading the style guide build, and Danny Carrino, who works with vendors on licensing the OpenStack logo, in case they have additional input. Please let us know how else we can help!


> On Jan 29, 2017, at 8:15 PM, Lana Brindley <openstack at lanabrindley.com> wrote:
> 
> Hi Heidi,
> 
> Just wanted to check in with you on this. We now have a webdev working on this, Nish Patwa from Intel, and he has a patch up for us already: https://review.openstack.org/#/c/425821
> 
> We still require some things from Foundation, though:
> 
> 1. This design requires access to the logos for the various operating systems. Is this something Foundation already has permission to use, or would we need to approach each group?
> 2. You indicated in a previous email that Foundation would be able to provide access to your design style guide, and possibly to a review. Can we please arrange that?
> 
> Thanks,
> Lana
> 
> On 23/01/17 09:27, Lana Brindley wrote:
>> Hi Heidi,
>> 
>> Happy new year! 
>> 
>> I wanted to circle back on the Install Guide landing page design. Piet created two wireframes for us, and the team have determined that they 'Concept 1' the best: https://openstack.invisionapp.com/share/ZF9OLTYND#/screens/210628213/comments
>> 
>> We have several issues that now need to be adressed:
>> 
>> 1. This design requires access to the logos for the various operating systems. Is this something Foundation already has permission to use, or would we need to approach each group?
>> 2. We don't have any web devs who have put up their hands to actually implement this design. Are we able to tap Foundation staff to create the patch for us?
>> 
>> Thanks,
>> Lana 
>> 
>> On 30/11/16 04:26, Heidi Joy Tretheway wrote:
>>>>> Hi Lana, 
>>> 
>>> Thanks for your patience on this. I wanted to thing through the options before responding, but it’s my fault I didn’t let you know that sooner. 
>>> 
>>> In terms of design requirements, we’ll be switching over from the old OpenStack logo to the new version over the next 4-5 months. The target is to have everything converted by the Boston Summit, which I realize is substantially after Ocata’s release. 
>>> 
>>> We’re also working on the mascots and I hope to have these ready for everyone by the PTG. I said hope because I’m waiting on illustrators to finish a new round, and as you can probably imagine, there were lots of critiques of the draft logos (plus about a dozen waiting for a first draft that we’re happy with). Also I’m seeing some places on the install guide page where you’d use mascots, but in others, you might skip them (e.g. Abstract, Conventions, Overview) and that might create an imbalanced or confusing design.
>>> 
>>> I think it would be great for you to work with Piet and the UX team to ensure you understand how users are engaging with the site. My impression from looking at it is that while plain, it definitely makes things easy to scan and find. So making things “prettier” via design would be far less important, in my opinion, than figuring out where users get stuck (if they do) and how to make it easier for them to use the install guides. 
>>> 
>>> In terms of foundation resources, I can think of a couple of options. I can’t commit our design team to designing a new page at this point because they are doing all of their usual stuff PLUS a full brand conversion, so they’re pretty maxed out through the Boston Summit. However, I can definitely commit us to a design review to ensure it is consistent with the new look and feel of the new brand identity. Also, as they’re working on a style guide, we can also supply that (but I don’t expect it until end of January at earliest) if you decide to do more front-end design work to make the look more functional. 
>>> 
>>> One final idea is to suggest that this might benefit from a strong masthead design to add energy to the page, while keeping the rest of it (text/links) the same and simple. We typically use creative commons-licensed images, and often do some layering of two images to create the right statement. The Path to Cloud booklet (with the hiker overlaid with circuitry illustration) is a good example of this. We’d need a wide horizontal image (or something that can be cropped that way) to start out, or at least some ideas for an image search. 
>>> 
>>> Please let me know if any of these ideas are appealing and I’ll be happy to work with the team to support you. Again, I’m sorry for my delayed reply. I am out of the office Dec. 2-12 but happy to get things going before or after my time away. 
>>> 
>>> Best,
>>> Heidi Joy
>>> 
>>> 
>>>>> 
>>>>> -------- Forwarded Message --------
>>>>> Subject: Re: [OpenStack-docs] Install Tutorial Landing Page Design Elements
>>>>> Date: Mon, 14 Nov 2016 10:29:48 +1000
>>>>> From: Lana Brindley <openstack at lanabrindley.com <mailto:openstack at lanabrindley.com>>
>>>>> To: Heidi Joy Tretheway <heidijoy at openstack.org <mailto:heidijoy at openstack.org>>
>>>>> CC: OpenStack Manuals <openstack-docs at lists.openstack.org <mailto:openstack-docs at lists.openstack.org>>
>>>>> 
>>>>> Hi Heidi,
>>>>> 
>>>>> Just wanted to follow up on this, as I hadn't heard from you yet.
>>>>> 
>>>>> Thanks,
>>>>> Lana
>>>>> 
>>>>> On 04/11/16 12:15, Lana Brindley wrote:
>>>>>> Hi Heidi,
>>>>>> 
>>>>>> As you may already know, docs redesigned how we create and publish the Install Guides in Newton.  Now, each big tent project can use our 'cookie-cutter' to create and maintain their own Install Guide, and we publish them up to our new Install Guide landing page, here: http://docs.openstack.org/project-install-guide/newton/ For the long version of that story, you can see this SuperUser article: http://superuser.openstack.org/articles/turning-openstack-install-guide-head/ or the first lightning talk here: https://www.youtube.com/watch?v=6TYyjrXX-Ec
>>>>>> 
>>>>>> Sadly, the landing page we have now is pretty ugly and hard to use, and we've got a goal to fix this in Ocata. The reason I'm emailing is because I wanted to find out from you  if the design elements we're currently using on the docs page (things like the little cartoon characters, etc) are still the right way to be doing things. Are there new design elements we should be thinking about, maybe in conjunction with the mascots? Also, do you have a designer on Foundation payroll that we can work with to do something truly awesome?
>>>>>> 
>>>>>> I've cc'd Piet, as he's interested in helping us improve the ux and making sure we get that aspect corrrect, but any access to design resources you can offer would be greatly appreciated.
>>>>>> 
>>>>>> Thanks,
>>>>>> Lana
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> _______________________________________________
>>>>>> OpenStack-docs mailing list
>>>>>> OpenStack-docs at lists.openstack.org <mailto:OpenStack-docs at lists.openstack.org>
>>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>>>>>> 
>>>>> 
>>>> 
>>>> -- 
>>>> Lana Brindley
>>>> Technical Writer
>>>> Rackspace Cloud Builders Australia
>>>> http://lanabrindley.com
>>>> 
>>> 
>> 
> 
> -- 
> Lana Brindley
> Technical Writer
> Rackspace Cloud Builders Australia
> http://lanabrindley.com
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20170130/524e331f/attachment-0001.html>