Skip to content

Commit cc4e418

Browse files
authored
Merge pull request #14369 from nextcloud/backport/14314/stable33
2 parents 38f2094 + 7b2a4c7 commit cc4e418

File tree

5 files changed

+21
-2
lines changed

5 files changed

+21
-2
lines changed

developer_manual/design/foundations.rst

Lines changed: 13 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,8 +15,9 @@ Primary color
1515
^^^^^^^^^^^^^
1616

1717
.. figure:: ../images/colour-primary.svg
18-
19-
#0082C9
18+
:alt: Nextcloud primary color swatch showing blue #0082C9
19+
20+
#0082C9
2021

2122
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.
2223

@@ -34,10 +35,12 @@ Background color
3435
.. list-table::
3536

3637
* - .. figure:: ../images/colour-main-background.svg
38+
:alt: Light theme background color swatch showing white #FFFFFF
3739

3840
Background for light theme: #FFFFFF
3941

4042
- .. figure:: ../images/colour-dark-theme-main-backgroud.svg
43+
:alt: Dark theme background color swatch showing dark grey #181818
4144

4245
Background for dark theme: #181818
4346

@@ -55,10 +58,12 @@ Text color
5558
.. list-table::
5659

5760
* - .. figure:: ../images/colour-main-text.svg
61+
:alt: Light theme text color swatch showing near-black #222222
5862

5963
Text in light theme: #222222
6064

6165
- .. figure:: ../images/colour-dark-theme-main-text.svg
66+
:alt: Dark theme text color swatch showing light grey #D8D8D8
6267

6368
Text in dark theme: #D8D8D8
6469

@@ -73,10 +78,12 @@ This is the main color for the text in light theme, and in dark theme.
7378
.. list-table::
7479

7580
* - .. figure:: ../images/colour-text-maxcontrast.svg
81+
:alt: Light theme secondary text color swatch showing grey #767676
7682

7783
Secondary text in light theme: #767676
7884

7985
- .. figure:: ../images/colour-dark-theme-text-maxcontrast.svg
86+
:alt: Dark theme secondary text color swatch showing medium grey #8C8C8C
8087

8188
Secondary text in dark theme: #8C8C8C
8289

@@ -95,18 +102,22 @@ Status and indicators
95102
.. list-table::
96103

97104
* - .. figure:: ../images/color-info.svg
105+
:alt: Info status color swatch showing blue #006AA3
98106

99107
Info: #006AA3
100108

101109
- .. figure:: ../images/color-success.svg
110+
:alt: Success status color swatch showing green #46BA61
102111

103112
Success: #46BA61
104113

105114
- .. figure:: ../images/color-error.svg
115+
:alt: Error status color swatch showing red #E9322D
106116

107117
Error: #E9322D
108118

109119
- .. figure:: ../images/color-warning.svg
120+
:alt: Warning status color swatch showing amber #ECA700
110121

111122
Warning: #ECA700
112123

developer_manual/digging_deeper/dashboard.rst

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -338,6 +338,7 @@ render the widget. Its constructor is:
338338
following example from the Talk app:
339339

340340
.. figure:: ../images/talk-widget-half-empty-content.png
341+
:alt: Talk dashboard widget showing half empty content state with a message displayed above a short item list
341342
:width: 40%
342343

343344
Here is a full example of a widget that implements the `OCP\\Dashboard\\IAPIWidgetV2` interface:

developer_manual/digging_deeper/profiler.rst

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -54,6 +54,7 @@ run, how many database and LDAP requests it did, how often did the cache hit and
5454
the toolbar track the XHR requests created by the JavaScript frontend.
5555

5656
.. image:: ../images/profiler-toolbar.png
57+
:alt: Nextcloud profiler toolbar showing request timing, database queries, LDAP requests, and cache statistics
5758

5859
You can hover on top of the toolbar information to show more detailed information and also
5960
click on the toolbar to show all the information collected.
@@ -71,6 +72,7 @@ The General Request and Response View
7172
.....................................
7273

7374
.. image:: ../images/profiler-request.png
75+
:alt: Profiler general request and response view showing controller, response headers, and request parameters
7476

7577
This view gives you general information about the request. For example,
7678
which Controller and method was used, what where the response headers, the
@@ -85,6 +87,7 @@ the query to see if an index was used and also see the backtrace to better under
8587
why the query was executed.
8688

8789
.. image:: ../images/profiler-database.png
90+
:alt: Profiler database queries view listing executed queries with execution time and explain options
8891

8992
It's important to keep the number of queries executed to a minimum since the database
9093
is often a limiting factor in a Nextcloud installation. In particular try to avoid the
@@ -105,6 +108,7 @@ This view display all the logged events and allow you to determine in which part
105108
programe the more time is spent.
106109

107110
.. image:: ../images/profiler-event.png
111+
:alt: Profiler event view displaying logged events and time spent in each part of the program
108112

109113
The Cache View
110114
..............
@@ -113,6 +117,7 @@ This view display all the access to the cache. It allows to detect cache hits an
113117
as well as getting an idea of the time spent on Redis.
114118

115119
.. image:: ../images/profiler-cache.png
120+
:alt: Profiler cache view showing cache hits, misses, and time spent on Redis operations
116121

117122
Contributing
118123
------------

developer_manual/html_css_design/popovermenu.rst

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -96,6 +96,7 @@ Technical details
9696
* Supported inputs are all text based ones and buttons type ones
9797

9898
.. image:: ../images/popover-position.png
99+
:alt: Diagram showing required 14px right distance for popover menu positioning relative to the three-dot icon
99100

100101
Alignment
101102
---------

developer_manual/prologue/bugtracker/triaging.rst

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -68,6 +68,7 @@ Much content from https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging
6868
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:
6969

7070
.. figure:: ../../images/triageworkflow.png
71+
:alt: Bug triage workflow diagram showing steps to evaluate and categorize issue reports
7172
:scale: 50
7273

7374
Let's go over each step.

0 commit comments

Comments
 (0)