Update design guidelines and add new screenshots#15002
Conversation
AI-assisted by Claude Opus 4.7 for first-draft and converting to .rst Signed-off-by: Nimisha Vijay <nimisha.k.vijay@gmail.com>
This comment was marked as resolved.
This comment was marked as resolved.
Signed-off-by: Nimisha Vijay <nimisha.k.vijay@gmail.com>
📖 Documentation Preview📄 8 changed documentation pages
Last updated: Fri, 22 May 2026 09:16:19 GMT |
oops, copy-paste oversight
Could we consider removing the html css design section? I has been outdated for almost 10 releases now. or we set up a redirect to the new guidelines 🤔 |
Sure, why not ? |
|
Please also use conventional commits :) |
… description. Signed-off-by: Nimisha Vijay <nimisha.k.vijay@gmail.com>
|
|
||
| Nextcloud design and brand standards are used to maintain the identity of Nextcloud apps. | ||
| If you're a developer who wants to create or contribute to a Nextcloud app, following this guide will make sure your app looks like it belongs to the Nextcloud family. | ||
| Nextcloud design and brand standards are used to maintain the identity of Nextcloud apps. If you’re a developer who wants to create or contribute to a Nextcloud app, following this guide will make |
There was a problem hiding this comment.
Will this line break be fine?
There was a problem hiding this comment.
Theoritecally, our design rst guidelines ask devs to split all lines after 120 characters.
| limits <https://www.nngroup.com/articles/response-times-3-important-limits/>`__. | ||
| - The state of the application should be clear. If something loads, provide feedback. | ||
| - Regularly reset your installation to see what the first-run experience is like, and improve it. | ||
| - Ideally do `usability testing <http://jancborchardt.net/usability-in-free-software>`__ to know how people use the software. Testing with 5 users is enough to identify most of your problems. |
There was a problem hiding this comment.
Minor, but this can be https now: https://jancborchardt.net/usability-in-free-software :)
There was a problem hiding this comment.
| - Ideally do `usability testing <http://jancborchardt.net/usability-in-free-software>`__ to know how people use the software. Testing with 5 users is enough to identify most of your problems. | |
| - Ideally do `usability testing <https://jancborchardt.net/usability-in-free-software>`__ to know how people use the software. Testing with 5 users is enough to identify most of your problems. |
| the `W3 website <https://www.w3.org/WAI/standards-guidelines/wcag/glance/>`__ | ||
| - Software should work. Only put features into main branch when they are complete. It is better to not have a feature instead of having one that works poorly. | ||
| - Software should get out of the way. Do things automatically instead of offering configuration options. When people ask for a setting, find out what the root of the problem is and fix that instead. | ||
| Also read `Choosing our Preferences <http://ometer.com/preferences.html>`__. |
There was a problem hiding this comment.
Same here, can be https: https://ometer.com/preferences.html
| Also read `Choosing our Preferences <http://ometer.com/preferences.html>`__. | |
| Also read `Choosing our Preferences <https://ometer.com/preferences.html>`__. |
| - Software should get out of the way. Do things automatically instead of offering configuration options. When people ask for a setting, find out what the root of the problem is and fix that instead. | ||
| Also read `Choosing our Preferences <http://ometer.com/preferences.html>`__. | ||
| - People’s data is sacred. Provide undo for most operations and optionally a confirmation for bigger more complex operations, but be careful about confirmations `as they might be | ||
| dismissed <http://www.alistapart.com/articles/neveruseawarning/>`__. |
There was a problem hiding this comment.
https and link slightly changed
| dismissed <http://www.alistapart.com/articles/neveruseawarning/>`__. | |
| dismissed <https://alistapart.com/article/neveruseawarning/>`__. |
| * The state of the application should be clear. If something loads, provide feedback. | ||
| * Regularly reset your installation to see what the first-run experience is like, and improve it. | ||
| * Ideally do `usability testing <http://jancborchardt.net/usability-in-free-software>`_ to know how people use the software. Testing with 5 users is enough to identify most of your problems. | ||
| For further UX principles, read `Alex Faaborg from Mozilla <http://uxmag.com/articles/quantifying-usability>`__, and the `GNOME Human Interface Guidelines <https://developer.gnome.org/hig/principles.html>`__ |
There was a problem hiding this comment.
https
| For further UX principles, read `Alex Faaborg from Mozilla <http://uxmag.com/articles/quantifying-usability>`__, and the `GNOME Human Interface Guidelines <https://developer.gnome.org/hig/principles.html>`__ | |
| For further UX principles, read `Alex Faaborg from Mozilla <https://uxmag.com/articles/quantifying-usability>`__, and the `GNOME Human Interface Guidelines <https://developer.gnome.org/hig/principles.html>`__ |
jancborchardt
left a comment
There was a problem hiding this comment.
Looks very nice! Just some details on the links (being not https) and on screenshots (like left nav not appearing blurry).
There was a problem hiding this comment.
Would be good to have 1 or 2 of them checked, no?
There was a problem hiding this comment.
This looks a bit wrong or too little contrast. Is it correct @marcoambrosini @nimishavijay?
There was a problem hiding this comment.
This doesn’t have the new left nav changes yet, and the left nav is also not blurred.
There was a problem hiding this comment.
Might be nice to have one of the entries hovered/focused to show it?
There was a problem hiding this comment.
Also here, background of nav is not blurred
(AI-assisted by Claude for first-draft and converting to .rst)
☑️ Resolves
🖼️ Screenshots
✅ Checklist
codespellor similar and addressed any spelling issues