We want to communicate our values and our strengths with the design of Pootle. Here we collect some of our main design goals, principles, and ideas. This should help new contributors to understand what to aim for, and for all developers to judge new ideas against.
Pootle is aimed at several users, but these are the most prominent ones:
Furthermore we'll want to target people from any and all languages, big and small, developed or underdeveloped. We will assume that most of our users aren't English, and therefore strive for perfect i18n of Pootle itself.
We want to work well on small screens (a reasonable experience on 10”-13” screens is ideal). End-user hardware released in the last few years should be able to handle using Pootle well.
We want to run reasonably well on older servers, although big installations can rely on more powerful servers. We currently run reasonably big sites on less than 1 GB of RAM. TODO: expand this a bit.
Pootle should work on many browsers, while being realistic about which features can be implemented easily and the representation of different browsers in the current and future user base. So we obviously should try to work on most browsers, with a reasonable fallback for legacy browsers like IE6 and IE7 where possible.
We can assume that CSS is enabled.