PMC proposals/Use Material Design

Summary

I propose to standardize that new or substantially redesigned Web interfaces and sites for Apertium be standardized to use Material Design.

In detail

Currently, Apertium has no standard for user interfaces, creating a discontinuity. I propose to adopt Material Design as the standard for Apertium Web interfaces.

To be clear, I am not proposing that existing interfaces should be immediately rewritten. I believe we should encourage this, but this proposal, if accepted, would not require this. It would only be required for new or substantially rewritten interfaces.

Over time, however, the interfaces would be rewritten or migrated. The Wiki would at least switch to the Timeless skin (which, although not Material, clashes much less than Monobook), and preferably the Material skin if it is deemed usable. There are already current discussions on rewriting html-tools, and the new version would use Material Design if this is accepted.

Additionally, desktop program and mobile app interfaces should continue to be designed to match the OSes they run on. (Of course, this would mean Material Design for Android and Chrome OS.)

Pros

• It's quite popular (not a reason in and of itself, but with UIs, some users may be more comfortable with Material Design)
• One of the most common ways to discover Apertium is GCI/GSoC. It may help a bit if Apertium "matches" the GCI and GSOC interfaces.
• There are many libraries for Material Design. Being one of the most popular UI specifications, any Web framework we could use (including no framework) will have at least one Material library.

Cons

• Not everyone likes it
• Looking "Google-y" may not be good

Proposed by: ScoopGracie {Talk~|~Contributions}