You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: developer_manual/design/foundations.rst
+13-2Lines changed: 13 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,8 +15,9 @@ Primary color
15
15
^^^^^^^^^^^^^
16
16
17
17
.. figure:: ../images/colour-primary.svg
18
-
19
-
#0082C9
18
+
:alt:Nextcloud primary color swatch showing blue #0082C9
19
+
20
+
#0082C9
20
21
21
22
While this is the primary color associated with Nextcloud and can be used to draw attention to an element, it is best to limit the usage of this to primary actions and other important elements.
Copy file name to clipboardExpand all lines: developer_manual/prologue/bugtracker/triaging.rst
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -68,6 +68,7 @@ Much content from https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging
68
68
The goal of triaging is to have only useful bug reports for the developers. And you don't have to know much to be able to judge at least some bug reports to be less than useful. There are duplications, incomplete reports and so on. Here is the work flow for each bug:
69
69
70
70
.. figure:: ../../images/triageworkflow.png
71
+
:alt:Bug triage workflow diagram showing steps to evaluate and categorize issue reports
0 commit comments