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: docs/contributing/index.md
+49-7Lines changed: 49 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -125,18 +125,60 @@ The benefits of this approach are that the link won't break if
125
125
126
126
### Images
127
127
128
+
> A picture is worth a thousand words
129
+
130
+
We encourage the usege of images to improve clarity and understanding. You can use **screenshoots** or **diagrams**.
131
+
128
132
Images are stored in the `docs/images` directory.
129
133
130
-
*there are sub-directories in the `docs/images` path - create a new sub-directory for your images if appropriate
131
-
* choose image and path names that make sense - `screenshot.png` is not a great file name. Neither is `PX-202502025-imgx.png`.
134
+
* create a new sub-directory for your images if appropriate
135
+
* choose a path and file name that hint what the image is about - neither `screenshot.png` nor `PX-202502025-imgx.png` are great names.
132
136
133
-
!!! tip
134
-
When providing a screenshot, do you need to show the whole screen, or just part of one window?
137
+
!!! warning
138
+
Keep the size of your images to a minimum because we want to keep an overall lightweight repository.
135
139
136
-
Cropping the image will decrease file size, and might also draw the readers attention to the most relevant information.
137
140
138
-
!!! tip
139
-
Do you need a screenshot, or can a text description also work?
141
+
#### Screenshots
142
+
143
+
Screenshots can help readers follow steps on guides. Think if you need to show the whole screen or just part of one window. Cropping the image will decrease file size, and might also draw the readers attention to the most relevant information.
144
+
145
+
Often, screenshots can quickly become obsolete, so you may want to complement (or maybe even replace) some with text descriptions.
146
+
147
+
#### Diagrams
148
+
149
+
Diagrams can help readers understand more abstract concepts like processes or architectures. We suggest you use [mermaid](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/creating-diagrams#creating-mermaid-diagrams). Such format makes diagrams easy to maintain and removes the need to commit image files in the repository.
150
+
151
+
??? "Diagram Example"
152
+
153
+
=== "Source"
154
+
155
+
````text
156
+
```mermaid
157
+
graph TD;
158
+
Image(Will image add value?);
159
+
Image--NO-->T(keep text only);
160
+
Image--YES-->SD(What image is needed?)
161
+
SD--Screenshoot-->S(keep it lean)
162
+
SD--Diagram-->D(keep it maintainable)
163
+
D--Default-->M(Mermaid)
164
+
D--Custom-->DR(Draw.io)
165
+
```
166
+
````
167
+
168
+
=== "Rendered"
169
+
170
+
```mermaid
171
+
graph TD;
172
+
Image(Will image add value?);
173
+
Image--NO-->T(keep text only);
174
+
Image--YES-->SD(What image is needed?)
175
+
SD--Screenshoot-->S(keep it lean)
176
+
SD--Diagram-->D(keep it maintainable)
177
+
D--Default-->M(Mermaid)
178
+
D--Custom-->DR(Draw.io)
179
+
```
180
+
181
+
If you need more hand-crafted diagrams, we suggest you use [draw.io](https://www.drawio.com/). Make sure you export the png with the [source inside](https://www.drawio.com/doc/faq/export-to-png), typically a `file.drawio.png`, so it can be extended in the future as needed.
0 commit comments