Canonical Voices

Posts tagged with 'notes'

Robin Winslow

pre {font-size: 1em; margin-bottom: 0.75em; padding: 0.75em} code {padding-left: 0.5em; padding-right: 0.5em} pre code {padding: 0; display: block;}

I recently tried to setup OpenID for one of our sites to support authentication with login.ubuntu.com, and it took me much longer than I’d anticipated because our site is behind a reverse-proxy.

My problem

I was trying to setup OpenID with the django-openid-auth plugin. Normally our sites don’t include absolute links (https://example.com/hello-world) back to themselves, because relative URLs (/hello-world) work perfectly well, so normally Django doesn’t need to know the domain name that it’s hosted it.

However, when authenticating with OpenID, our website needs to send the user off to login.ubuntu.com with a callback url so that once they’re successfully authenticed they can be directed back to our site. This means that the django-openid-auth needs to ask Django for an absolute URL to send off to the authenticator (e.g. https://example.com/openid/complete).

The problem with proxies

In our setup, the Django app is served with a light Gunicorn server behind an Apache front-end which handles HTTPS negotiation:

User <-> Apache <-> Gunicorn (Django)

(There’s actually an additional HAProxy load-balancer in between, which I thought was complicating matters, but it turns out HAProxy was just passing through requests absolutely untouched and so was irrelevant to the problem.)

Apache was setup as a reverse-proxy to Django, meaning that the user only ever talks to Apache, and Apache goes off to get the response from Django itself, with Django’s local network IP address – e.g. 10.0.0.3.

It turns out this is the problem. Because Apache, and not the user directly, is making the request to Django, Django sees the request come in at http://10.0.0.3/openid/login rather than https://example.com/openid/login. This meant that django-openid-auth was generating and sending the wrong callback URL of http://10.0.0.3/openid/complete to login.ubuntu.com.

How Django generates absolute URLs

django-openid-auth uses HttpRequest.build_absolute_uri which in turn uses HttpRequest.get_host to retrieve the domain. get_host then normally uses the HTTP_HOST header to generate the URL, or if it doesn’t exist, it uses the request URL (e.g.: http://10.0.0.3/openid/login).

However, after inspecting the code for get_host I discovered that if and only if settings.USE_X_FORWARDED_HOST is True then Django will look for the X-Forwarded-Host header first to generate this URL. This is the key to the solution.

Solving the problem – Apache

In our Apache config, we were initially using mod_rewrite to forward requests to Django.

RewriteEngine On
RewriteRule ^/?(.*)$ http://10.0.0.3/$1 [P,L]

However, when proxying with this method Apache2 doesn’t send the X_Forwarded_Host header that we need. So we changed it to use mod_proxy:

ProxyPass / http://10.0.0.3/
ProxyPassReverse / http://10.0.0.3/

This then means that Apache will send three headers to Django: X-Forwarded-For, X-Forwarded-Host and X-Forwarded-Server, which will contain the information for the original request.

In our case the Apache frontend used HTTPS protocol, whereas Django was only using so we had to pass that through as well by manually setting Apache to pass an X-Forwarded-Proto to Django. Our eventual config changes looked like this:

<VirtualHost *:443>
    ...
    RequestHeader set X-Forwarded-Proto 'https' env=HTTPS

    ProxyPass / http://10.0.0.3/
    ProxyPassReverse / http://10.0.0.3/
    ...
</VirtualHost>

This meant that Apache now passes through all the information Django needs to properly build absolute URLs, we just need to make Django parse them properly.

Solving the problem – Django

By default, Django ignores all X-Forwarded headers. As mentioned earlier, you can set get_host to read the X-Forwarded-Host header by setting USE_X_FORWARDED_HOST = True, but we also needed one more setting to get HTTPS to work. These are the settings we added to our Django settings.py:

# Setup support for proxy headers
USE_X_FORWARDED_HOST = True
SECURE_PROXY_SSL_HEADER = ('HTTP_X_FORWARDED_PROTO', 'https')

After changing all these settings, we now have Apache passing all the relevant information (X-Forwarded-Host, X-Forwarded-Proto) so that Django is now able to successfully generate absolute URLs, and django-openid-auth now works a charm.

Read more
Robin Winslow

We recently introduced Vanilla framework, a light-weight styling framework which is intended to replace the old Guidelines framework as the basis for our Ubuntu and Canonical branded sites and others.

One of the reasons we created Vanilla was because we ran into significant problems trying to use Guidelines across multiple different sites because of the way it was made. In this article I’m going to explain how we structured Vanilla to hopefully overcome these problems.

You may wish to skip the rationale and go straight to “Overall structure” or “How to use the framework”.

Who’s it for?

We in Canonical’s design team will definitely be using Vanilla, and we also hope that other teams within Canonical can start to use it (as they did with Guidelines before it).

But most importantly, it would be fantastic if Vanilla offers a solid enough styling basis that members of the wider community feel comfortable using it as well. Guidelines was never really safe for the community at large to use with confidence.

This is why we’ve made an effort to structure Vanilla in such a way that any or all of it can be used with confidence by anyone.

Limitations of Guidelines

Guidelines was initially intended to solve exactly one problem – to be a single resource containing all the styling for ubuntu.com. This would mean that we could update Guidelines whenever we needed to update ubuntu.com’s styling, and those changes would propagate across all our other Ubuntu-branded sites (e.g.: cn.ubuntu.com or developer.ubuntu.com).

So we simply structured the markup of these sites in the same way, and then created a single hosted CSS file, and linked to it from all the sites that needed Ubuntu styling.

As time went on, two large problems with this solution emerged:

  • As over 10 sites were linking to the same CSS file, updating that file became very cumbersome, as we’d have to test the changes on every site first.
  • As the different sites became more individual over time, we found we were having to override the base stylesheet more and more, leading to overly complex and confusing local styling.

This second problem was only exacerbated when we started using Guidelines as the basis for Canonical-branded sites (e.g.: canonical.com) as well, which had a significantly different look.

Architecture goals for Vanilla

Learning from our experiences with Guidelines, we planned to solve a few specific problems with Vanilla:

  • Website projects could include only the CSS code they actually needed, so they don’t have to override lots of unnecessary CSS.
  • We could release new changes to the framework without worrying about breaking existing sites, allowing us to iterate quickly.
  • Other projects could still easily copy the styles we use on our sites with minimal work

To solve these problems, we decided on the following goals:

  • Create a basic framework (Vanilla) which only contains the common elements shared across all our sites.

    • This framework should be written in a modular way, so it’s easy to include only the parts you need
  • Extend the basic framework in “theme” projects (e.g. ubuntu-vanilla-theme) which will apply specific styling (colours etc.) for that specific brand.

    • These themes should also only contain code which needs to be shared. Site-specific styling should be kept local to the project
  • Still provide hosted compiled CSS for sites to hotlink to if they like, but force them to link to a specific version (e.g. vanilla-framework-version-0.0.15.css) rather than “latest” so that we can release a new version without worry.

Sass modularisation

This modular structure would be impossible in pure CSS. CSS itself offers no mechanism for encapsulation. Fortunately, our team has been using Sass to write our CSS for a while now, and Sass offers some important mechanisms that help us modularise our code. So what we decided to create is actually a Sass mixin library (like Bourbon for example) using the following mechanisms:

Default variables

Setting global variables is essential for the framework, so we can keep consistent settings (e.g. font colours, padding etc.). Variables can also be declared with the !default flag. This allows the framework’s settings to be overridden when extending the framework:

We’ve used this pattern in each of the Vanilla themes we’ve created.

Separating concerns into separate files

Sass’s @import feature allows us to encapsulate our code into files. This not only keeps our code tidier, but it means that anyone hoping to include some parts of our framework can choose which files they want:

Keeping everything in a mixin

When a Sass file is imported any loose CSS is compiled directly to the output. But anything declared inside a @mixin will not be output unless you call the mixin.

Therefore, we set a goal of ensuring that all parts of our library can be imported without any CSS being output, so that you can import the whole module but just choose what you want output into your compiled CSS:

Namespacing

To avoid conflicts with any local sass setup, we decided to namespace all our mixins with the vf- prefix – e.g. vf-grid or vf-header.

Overall structure

Using the aforementioned techniques, we created one base framework, Vanilla Framework, which contains (at the time of writing) 19 separate “modules” (vf-buttons, vf-grid etc.). You can see the latest release of the framework on the project’s homepage, and see the framework in action on the demo page.

The framework can be customised by overriding any of the global settings inside your local Sass, as described above.

We then extended this basic framework with three branded themes which we will use across our sites:

You can of course create your own themes by extending the framework in the same way.

NPM modules

To make it easy to include Vanilla Framework in our projects, we needed to pick a package manager to use for installing it and tracking versions. We experimented with Bower, but in the end we decided to use the Node package manager. So now anyone can install and use any of the following packages:

Hotlinks for compiled CSS

Although for in-depth usage of our framework we recommend that you install and extend it locally, we also provide hosted compiled CSS files, both minified and unminified, for the Vanilla framework itself and all Vanilla themes, which you can hotlink to if you like.

To find the links to the latest compiled CSS files, please visit the project homepage.

How to use the framework

The simplest way to use the framework is to hotlink to it. To do this, simply link to the latest version (minified or unminified) directly in your HTML:

However, if you want to take full advantage of the framework’s modular nature, you’ll probably want to install it directly in your project.

To do this, add the latest version of vanilla-framework to your project’s package.json as follows:

Then, after you’ve npm installed, include the framework from the node_modules folder:

The future

We will continue to develop Vanilla Framework, with version 0.1.0 just around the corner. You can track our progress over on the project homepage and on Github.

In the near future we’ll switch over ubuntu.com and canonical.com to using it, and when we do we’ll definitely blog about it.

Read more
Giorgio Venturi

Canonical and Ubuntu at dConstruct

Brighton is not just a lovely seaside town, mostly known for being overcrowded in Summer by Londoners in search for a bit of escapism, but also the home of a thriving community of designers, makers and entrepreneurs. Some of these people run dConstruct, a gathering where creative minds of all sorts converge every year to discuss important themes around digital innovation and culture.

When I found out that we were sponsoring the conference this year, I promptly jumped in to help my colleagues in the Phone, Web and Juju design teams. Our stand was situated in the foyer of the Brighton Dome, flashing the orange banner of Ubuntu and a number of origami unicorns.

The Ubuntu Stand

Origami Unicorns

We had an incredibly positive response from the attendees, as our stand was literally teeming with Ubuntu enthusiasts who were really keen to check our progress with the phone. We had a few BQ phones on display where we showed the new features and designs.

Testing the phone

For us, it was a great occasion to gather fresh impressions of the user experience on the phone and across a variety of apps. After a few moments, people started to understand the edge interactions and began to swipe left and right, giving positive feedback on the responsiveness of the UI. Our pre-release models of BQ phones don’t have the final shell and they still display softkeys, as a result some people found this confusing. We took the opportunity to quickly design our own custom BQ phone by using a bunch of Ubuntu stickers…and viola, problem solved! ;)

Ubuntu phone - customised

Our ‘Make your Unicorn’ competition had a fantastic response. To celebrate the coming release of Utopic Unicorn and of the BQ phone, the maker of the best origami unicorn being awarded a new phone. The crowd did not hesitate to tackle the complex paper-bending challenge and came up with a bunch of creative outcomes. We were very impressed to see how many people managed to complete the instructions, as I didn’t manage to go beyond step 15..

Ubuntu fans

Twitter   Search - #dconstruct #ubuntu

Read more
Benjamin Keyser

Bringing Fluid Motion to Browsing

In the previous Blog Post, we looked at how we use the Recency principle to redesign the experience around bookmarks, tabs and history.
In this blog post, we look at how the new Ubuntu Browser makes the UI fade to the background in favour of the content. The design focuses on physical impulse familiarity – “muscle memory” – by marrying simple gestures to the two key browser tasks, making the experience feel as fluid and simple as flipping through a magazine.

 

Creating a new tab

For all new browsers, the approach to the URI Top Bar that enables searching as well as manual address entry has made the “new tab” function more central to the experience than ever. In addition, evidence suggests that opening a new tab is the third of the most frequently used action in browser. To facilitate this, we made opening a new tab effortless and even (we think) a bit fun.
By pulling down anywhere on the current page, you activate a sprint loaded “new tab” feature that appears under the address bar of the page. Keep dragging far enough, and you’ll see a new blank page coming into view. If you release at this stage, a new tab will load ready with the address bar and keyboard open as well as an easy way to get to your bookmarks. But, if you change your mind, just drag the current page back up or release early and your current page comes back.

http://youtu.be/zaJkNRvZWgw

 

Get to your open tabs and recently visited sites

Pulling the current page downward can create a new blank tab, and conversely dragging the bottom edge upward shows you already open tabs ordered by recency that echoes the right edge “open apps” view.

If you keep on dragging upward without releasing, you can dig even further into the past with your most recently visited pages grouped by site in a “history” list. By grouping under the site domain name, it’s easier to find what you’re looking for without thumbing through hundreds of individual page URLs. However, if you want all the detail, tap an item in the list to see your complete history.

Blog Post - Browser #2 (1)
It’s not easy to improve upon such a well-worn application as the browser, it’s true. We’re hopeful that by adding new fluidity to creating, opening and switching between tabs, our users will find that this browsing experience is simpler to use, especially with one hand, and feels more seamless and fluid than ever.

 

 

Read more
Inayaili de León Persson

Latest from the web team — June 2014

We’re now almost half way through the year and only a few days until summer officially starts here in the UK!

In the last few weeks we’ve worked on:

  • Responsive ubuntu.com: we’ve finished publishing the series on making ubuntu.com responsive on the design blog
  • Ubuntu.com: we’ve released a hub for our legal documents and information, and we’ve created homepage takeovers for Mobile Asia Expo
  • Juju GUI: we’ve planned work for the next cycle, sketched scenarios based on the new personas, and launched the new inspector on the left
  • Fenchurch: we’ve finished version 1 of our new asset server, and we’ve started work on the new Ubuntu partners site
  • Ubuntu Insights: we’ve published the latest iteration of Ubuntu Insights, now with a dedicated press area
  • Chinese website: we’ve released the Chinese version of ubuntu.com

And we’re currently working on:

  • Responsive Day Out: I’m speaking at the Responsive Day Out conference in Brighton on the 27th on how we made ubuntu.com responsive
  • Responsive ubuntu.com: we’re working on the final tweaks and improvements to our code and documentation so that we can release to the public in the next few weeks
  • Juju GUI: we’re now starting to design based on the scenarios we’ve created
  • Fenchurch: we’re now working on Juju charms for the Chinese site asset server and Ubuntu partners website
  • Partners: we’re finishing the build of the new Ubuntu partners site
  • Chinese website: we’ll be adding a cloud and server sections to the site
  • Cloud Installer: we’re working on the content for the upcoming Cloud Installer beta pages

If you’d like to join the web team, we are currently looking for a web designer and a front end developer to join the team!

Juju scenariosWorking on Juju personas and scenarios.

Have you got any questions or suggestions for us? Would you like to hear about any of these projects and tasks in more detail? Let us know your thoughts in the comments.

Read more
Inayaili de León Persson

Latest from the web team — May 2014

We’re fast approaching the summer, and the first few sunny days have already arrived in London. The web team cannot slow its pace though…

In the last few weeks we’ve worked on:

  • Responsive ubuntu.com: we’ve had a sprint to clean up our processes and CSS files after the big responsive release last month
  • Ubuntu.com: we’ve updated our Jumpstart service to include the exciting new Orange Box Micro-cluster and Your cloud product pages in preparation for the OpenStack Developer Summit
  • Juju GUI: we’ve finished creating new personas
  • Ubuntu OpenStack Interoperability Lab: we’ve completed the report design
  • Ubuntu OpenStack Installer: the installer was presented at the OpenStack Developer Summit last week, and we’ve done iterations on the designs based on recent user research
  • Fenchurch: we’ve moved Fenchurch into a proper Django project, nearly completed the first phase of a new asset server with a new Juju charm, and set up a new Fenchurch instance for the new legal website
  • Ubuntu Insights: we’ve made the move from Ubuntu Resources to Ubuntu Insights, and launched the desktop version of the site
  • Las Vegas sprint: we worked on updated, mobile-first bundle and charm details pages and started planning for the next cycle
  • Partners: we’ve completed the final UX and copy for this new Ubuntu website

And we’re currently working on:

  • Responsive ubuntu.com: we’re now in the process of updating our web style guide documents before the public release of the new styles
  • Ubuntu Insights: we’re adding the final touches before launching the press centre in the next few weeks
  • Juju GUI: we’re planning the work for the next cycle
  • Fenchurch: we’re working on getting the Juju charms in production for the new legal site, finishing up the asset server and planning the development of our new partners website
  • Partners: we’re currently building the new partners website
  • Legal pages: we’re now in the process of building the new hub that will hold all our legal information
  • Chinese website: we’ve finalised UX and copy for this upcoming Ubuntu site

If you’d like to join the web team, we are currently looking for experienced user experience and web designers to join the team!

Design team moving desksThe design team getting ready to move desks, at the end of April.

Have you got any questions or suggestions for us? Would you like to hear about any of these projects and tasks in more detail? Let us know your thoughts in the comments.

Read more
Inayaili de León Persson

Latest from the web team — April 2014

Ubuntu 14.04 LTS is out and it’s great! The period after release tends to be slightly less hectic than the lead up to it, but that doesn’t mean that the web team is not as busy as ever.

In the last few weeks we’ve worked on:

  • Ubuntu 14.04 LTS release: we’ve published the latest updates to www.ubuntu.com that go alongside the latest release of Ubuntu
  • Ubuntu.com: ubuntu.com is now responsive! Stay tuned for a more in-depth post on this, and keep following our series on how we made ubuntu.com responsive; we’ve also launched a new and improved cloud section
  • Juju GUI: we’ve moved the inspector to the left of the screen, which should be live in the coming weeks, and we’re finalising user research
  • Fenchurch: we moved downloads, contributions and search to Fenchurch, so we’re now effectively off our old Drupal site, with a better geolocation solution for download mirrors
  • Ubuntu Resources: we’ve released the beta version for large screen sizes of Ubuntu Resources
  • Future of Web Design: I attended and spoke at the Future of Web Design conference, in London, where I talked about letting mechanisation into our work as web designers, and how we can move further in our profession

And we’re currently working on:

  • Responsive ubuntu.com: we’re currently working on tweaks and improvements following the release on 17 April
  • Web style guide: we’re updating the Ubuntu web style guide (still in alpha) to reflect the changes from making www.ubuntu.com responsive
  • Ubuntu Resources: we’re currently working on making the transition from Ubuntu Resources to Ubuntu Insights, after that we’ll be working on creating a press centre on the new Ubuntu Insights
  • Fenchurch: we’re working on a new front-end for our asset server and upgrading the ubuntu.com CMS to the version running www.canonical.com
  • Las Vegas sprint: a few of us are travelling to the USA next week for some intense Juju planning and work
  • Legal pages: we’re in the process of defining the information architecture and wireframing for a new hub that will hold all our legal information
  • Partners: we’re finalising wireframes and content for a new Ubuntu partners site

And, if you’d like to join the web team, we are currently looking for an experienced user experience designer to join us! Send us an email if you’d like to apply.

Delicious treats for the Ubuntu releaseDelicious treats on release day

Do you have any questions or suggestions for us? Would you like to hear about any of these projects and tasks in more detail? Let us know your thoughts in the comments.

Read more
Inayaili de León Persson

Latest from the web team — March 2014

Spring has officially (but not technically…) arrived, and we’re getting busier and busier in preparation for Ubuntu 14.04 LTS release next month.

In the last few weeks we’ve worked on:

  • Ubuntu Resources: we’ve just launched a new version of the site
  • Ubuntu.com: we’ve launched a localised Chinese homepage that highlights Ubuntu Kylin
  • Juju GUI: Matthieu has worked on a new icon set for charms which will be released in the next few weeks
  • Fenchurch: we completely rewrote the Juju charm that updates canonical.com
  • Landscape sprint: Carla has been to Rome for the Landscape team’s sprint, where she helped to wireframe changes for 14.04 and beyond

And we’re currently working on:

  • Ubuntu Resources: we’re now working on expanding the styles of the site to accommodate desktop screen sizes and adding even more features
  • Ubuntu 14.04 release: we’re reskinning the OpenStack Horizon dashboard for the OpenStack 14.04 release, and we’ve started working on updated images for the release
  • Responsive ubuntu.com: we’ve been testing on various devices and fixing lots of little rendering issues; we’ve also been tackling larger challenges like the navigation and footer; you can follow our progress in the series of posts we’re publishing on this blog!
  • Fenchurch: we’re currently updating the contributions and download pages so that it works on Fenchurch
  • Juju: we’re doing some user research to understand engineer workflows
  • Cloud section: we’ve finished wireframing and the first round of designs for the 14.04 refresh of www.ubuntu.com’s cloud section
  • Partners section of ubuntu.com: we’re at the wireframing stage of this project

This month we’ve also welcomed a new member of the team: Robin is our new back-end developer.

Testing Ubuntu Resources on a Kindle Fire HDTesting Ubuntu Resources on a Kindle Fire HD

Have you got any questions or suggestions for us? Would you like to hear about any of these projects and tasks in more detail? Let us know your thoughts in the comments.

Read more
Inayaili de León Persson

Latest from the web team — February 2014

Time flies! February is mostly behind us now and hopefully spring won’t take too long to show up in London.

In the last few weeks we’ve worked on:

  • Ubuntu Resources: we’ve released a new iteration of the site this week — have a look and let us know your thoughts!
  • MWC 2014: we’ve created a few homepage takeovers and updated the /phone and /tablet sections of www.ubuntu.com in preparation for this event
  • Cape Town sprint: a few of us have been to the cloud sprint in South Africa earlier this month, where work focused on planning the next iterations of Juju
  • Fenchurch: we’ve been improving the Fenchurch Juju charm

And we’re currently working on:

  • Ubuntu Resources: we’ve already started working on the next iteration of the site, which should be released in just a few weeks — this time we’re focusing on medium screen sizes
  • Ubuntu 14.04 release: we’ve started to go through the long list of updates to make the site ready for the upcoming release, mainly creating and updating image assets and copywriting
  • Responsive ubuntu.com: we’re now moving full speed ahead, updating our front end framework, which powers www.ubuntu.com and other sites, to be mobile-first and responsive; a lot of the work in the next few weeks will be focused on creating new image assets and lots and lots of testing
  • Fenchurch: we’ll be finalising Fenchurch’s Juju charm auto-updating
  • Videos: we’re putting the final touches and testing the updated version of our web video player
  • Juju: in the last few weeks we’ve released a new design for relationship lines and we’ve added local charm support — you can now import local charms into an environment using the import function or by dragging a YAML file from your computer onto the Juju canvas

Here are a few photos that Luca took of the week in Cape Town, where the sun was shining.

Luca's Cape Town photosSome moments from Cape Town, earlier this month.

Have you got any questions or suggestions for us? Would you like to hear about any of these projects and tasks in more detail? Let us know your thoughts in the comments.

Read more
Vesa Rautiainen

In January when the winter weather was at its worst in London we packed our laptops, designs and prototypes and headed to Cape Town, South Africa for Client Platform Sprint. This design sprint was a mid cycle checkpoint and the target was to get some important 14.04 designs, including Dash and Right edge swipe, reviewed and finalized.

It was an intense week with lots of review sessions and a tight schedule. But after the day’s work was done we tried to make most of our time in this astonishing place. The trip wouldn’t have been complete without visiting those vineyards, white-sand beaches and of course THE Table Mountain.

All in all it was a great work week in the sun with some bits of free time activities. Easily beats a regular week at the office. Some pictures from the trip:

Right Edge designRight Edge design

Trying to nail the DashTrying to nail the Dash

Camps Bay

Camps Bay

Table Mountain

Table MountainCape Town

Read more
Inayaili de León Persson

Latest from the web team — January 2014

We’re now well into 2014 and working on several exciting projects that will be released throughout the year.

In the last few weeks we’ve worked on:

  • Ubuntu Resources: we’ve been working on designs for a new homepage and topic landing pages for the upcoming beta release
  • Canonical website: the new canonical.com is now live!
  • Videos: we’ve finalised the designs for a web video player, which should soon be added to www.ubuntu.com
  • Front end mini sprint: we discussed what we’ve learned from making canonical.com and how it might impact the update of ubuntu.com and of the Web Style Guide

And we’re currently working on:

  • Ubuntu Resources: we are making improvements based on feedback we’ve received and adding some new features, like filtered search
  • Ubuntu 14.04 release: we’ve finalised all the planning for the 20th Ubuntu release and have started to work through the long to-do list in the run up to April
  • Ubuntu.com: we are in the process of updating our Web Style Guide to become responsive, which will mean a responsive www.ubuntu.com
  • Juju GUI: we’re working on improved relationship lines
  • Fenchurch: an initial Juju charm has been released and we’re now enhancing it with additional hooks
  • Cloud sprint: many of us are getting ready for a cloud sprint taking place next week in Cape Town, South Africa

Office before holidays The design team’s corner right before the holidays

Have you got any questions or suggestions for us? Would you like to hear about any of these projects and tasks in more detail? Let us know your thoughts in the comments.

Read more
Matt Turnbull

New year links

Happy new year!

Here are a couple of links that have been flying around the London office since we returned. The Verge did a recap of their most influential people of 2013.

pussy-riot

 

And there’s a report from JWT pointing at some nice trends, manifestations and insights for 2014 (thank you, Daniel, for the link).

sunday-assembly
reaper-drone
apex-brasil

Read more
Inayaili de León Persson

Latest from the web team — December 2013

This month we’ve been working hard trying to wrap up as much as we can before the holidays and planning for 2014.

In the last few weeks we’ve worked on:

  • Ubuntu Resources: updating the site based on feedback we received from users — keep those comments coming!
  • Canonical website: getting the site ready for launch, which will happen early next month
  • Juju GUI: adding animations to the GUI
  • Landscape: providing designs for an upcoming visual update
  • Juju Labs: designing and updating the labs section of juju.ubuntu.com

And we’re currently working on:

  • Ubuntu Resources: adding topic-based subscriptions and filters in search results
  • Ubuntu 14.04 release: believe it or not, we’re already starting to look into how we’ll be updating www.ubuntu.com for this LTS
  • Ubuntu.com: updating our partner pages in the new year and adding new Ubuntu installation videos to the site
  • Canonical website: now testing the new website on various mobile devices
  • Juju GUI: refining the bundle and browse experience and interactions
  • Fenchurch: moving towards continuous integration of Juju service with Canonical’s IS team

We have also had a very fun Canonical End of Year party!

Canonical status board
A photo of our status board of the upcoming and updated canonical.com

Have you got any questions or suggestions for us? Would you like to hear about any of these projects and tasks in more detail? Let us know your thoughts in the comments.

Read more
Christina Li

App Design Clinic #6

We have been running the app design clinic every two weeks to answer any questions from community designers and developers on the apps they are working on!

For this session we talked about the community submitted convergence designs for file manager and clock app (thanks everyone!) as well as answering some questions from our Canonical engineers submitted apps, such as:
- If your app has two equal actions- how do you provide entry points?
- What if I want to show more content, but page stack is not appropriate?
- Where should ‘About’ & ‘Settings’ go? (Not in the tabs, please)

If you missed it, or want to watch it again, here it is:

Please send your questions and screenshots to
design@canonical.com by 1pm UTC on a Tuesdays to be included in the following Wednesday clinic.

Watch this space for our next App Design Clinic time.

Read more
Katie Taylor

App Design Clinic #5

Over the last few months we have been running the App Design Clinic and we want to thank you for all your submissions, contribution and feedback!
The Design Clinic happens every two weeks and the last one co-incided with vUDS, so we included more information on general app design as well as answering quesitons.

Here’s what happened:

- A summary of topics from previous App Design Clinics
- A run-down of where to find the necessary things and resources to design an app
- And finally, how you can contribute and participate in the clinic

The next one happens tomorrow, 4th of December. Please send your questions and screenshots to
design@canonical.com by 1pm UTC on a Tuesdays to be included in the following Wednesday clinic.

Read more
Christina Li

On 19-21 November we had our vUDS where we got to discuss and share with the community some of the design work we’ve been doing recently.

Our topics ranged from our design blog to convergence designs to Juju GUI cloud to icon designs!

If you missed any of our sessions, don’t worry. They are all below for you to check them out!

Design Blog

Love our blog? How can we make it better? What topics would you like to see?

Responsive Design

Hear about our thoughts on converging our patterns, components and designs from phone to tablet to desktop.

App Design Clinic

Every two weeks, we gather to talk about app designs and patterns. If you are developing an app or have any questions on apps, let us know!

Designing a responsive website and web guide

We talked about the process of designing a responsive website and shared the current web style guide we have been using for the main Ubuntu.com site.

Research on Windows and Android usability

Juju GUI design evolution

User research has informed the way Juju GUI has changed over the last year. Here is the evolution of Juju GUI.

Designing icons for Ubutnu

We have been designing icons for Ubuntu Phone and Tablet and Desktop. Check them out!

Let us know what you think, or suggestions on what you want to see next from the Design team at the next vUDS!

Read more
Inayaili de León Persson

Latest from the web team — November 2013

Even though Ubuntu 13.10’s release is behind us, we always find ways to keep busy. Here are the highlights of the past four weeks.

In the last few weeks we’ve worked on:

And we’re currently working on:

  • Ubuntu Resources: we’re iterating on the current alpha release, improving the design and adding new features
  • Canonical website: we’re currently exploring design directions and finalising the content for the site
  • Juju GUI: we’re refining the bundle experience and interactions for the 14.04 release
  • Fenchurch: we’ve been improving deployment scripts and asset deployment
  • Live chat trial: we’ve been helping the sales team to test a live chat feature on www.ubuntu.com

We also welcomed a new member of the team: Felipe is the new Lead User Experience. And we’ve learned about Karl’s cage fighting past.

Welcome lunchTeam lunch to welcome Felipe and Karl

Have you got any questions or suggestions for us? Would you like to hear about any of these projects and tasks in more detail? Let us know your thoughts in the comments.

Read more
Christina Li

November Brown Bag lunch

Some of us in the Design team have been gathering on a monthly basis to have lunch together and share things we find interesting to us.

Today, I’d like to share with you the Brown Bag lunch we had this week.

Vesa shared with us his interest in photography and showed us some of the shots he took over time.

9690256316_8c4040a4bb_bWestminster at night by Vesa (flickr)

I came across an inspiring research done by Helen Hamlyn Centre for Design at the Royal College of Art in London. The research focused on facilitating older people using mobile phones, rather than designing a simpler phone for them to use.

And, our challenge of the month was to build the tallest paper tower! Each team had 20 pieces of paper and 6 minutes, with 2 rules:

1. You can only use paper to build your tower
2.You can tear or fold the pieces of paper.

Well, I’m happy to report that Rachel, Vesa and Olga proudly won this challenge with their paper tower!

photo (2)

How would you build your tower in 6 minutes?

Read more
Jouni Helminen

App Design Clinic #4

App design Clinic #4 focuses on icons, with questions from Stuart Langridge including:

  • guidance on creating app icons (stylistically and in terms of file format and resolution)
  • tips on how to use action icons

The presentation deck link will be shared on the blog once it’s been checked by our icon designer, and we hope to have an icons guideline with downloadable templates and full API docs online within a month.

The next clinic is held in conjunction with vUDS. Let’s make it a great one,  please send any designs and/or questions to design@ubuntu.com

Read more
Spencer Bygraves

A week in San Francisco

I recently attended my first cloud sprint meeting held in San Francisco, and it turned out to be a great experience. It’s been 10 years since I last visited, so as well as working hard, it was nice to have the opportunity to see the city again.

Whilst there we worked on the UX and visual design for two of our cloud products, which we’ll be able to share with you soon. It was also a great opportunity to spend time with colleagues from around the world, working together during the day and having a few beers in the evening.

In terms of design, we are working to extend the cloud visual language that is being established through the Juju GUI, with a view to having a consistent suite of cloud products.

A post with some cloud designs will follow soon. For now, here’s some pictures from our week in San Francisco.

Watch this space!

 

SF-01Discussing Juju and collaborative coding

 

SF-02San Francisco

 

 

Read more