Skip to content

Navigation Menu

Sign in

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Appearance settings

Commit acf92fe

Browse filesBrowse files
story645story645
committed
reorganize contribute page into blocks and cards
changed buttons into clickable cards + code spaces placeholder
1 parent 0b8bd96 commit acf92fe
Copy full SHA for acf92fe

File tree

5 files changed

+138
-60
lines changed
Filter options

5 files changed

+138
-60
lines changed

‎doc/devel/contribute.rst

Copy file name to clipboardExpand all lines: doc/devel/contribute.rst
+6-1Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,8 @@ contribute. Everyone within the community
1818
is expected to abide by our
1919
`code of conduct <https://github.com/matplotlib/matplotlib/blob/main/CODE_OF_CONDUCT.md>`_.
2020

21+
22+
2123
Below, you can find a number of ways to contribute, and how to connect with the
2224
Matplotlib community.
2325

@@ -77,7 +79,9 @@ There are a few typical new contributor profiles:
7779
and gaining context on this area by reading the issues and pull requests
7880
touching these subjects is a reasonable approach.
7981

80-
Get Connected
82+
.. _get_connected:
83+
84+
Get connected
8185
=============
8286

8387
Do I really have something to contribute to Matplotlib?
@@ -145,6 +149,7 @@ though not necessarily all at the same time:
145149
- It involves Python features such as decorators and context managers, which
146150
have subtleties due to our implementation decisions.
147151

152+
.. _managing_issues_prs:
148153

149154
Work on an issue
150155
----------------

‎doc/devel/development_setup.rst

Copy file name to clipboardExpand all lines: doc/devel/development_setup.rst
+2-2Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -148,8 +148,8 @@ The simplest way to do this is to use either Python's virtual environment
148148
Remember to activate the environment whenever you start working on Matplotlib.
149149

150150

151-
Installing Matplotlib in editable mode
152-
======================================
151+
Install Matplotlib in editable mode
152+
===================================
153153
Install Matplotlib in editable mode from the :file:`matplotlib` directory
154154
using the command ::
155155

‎doc/devel/development_workflow.rst

Copy file name to clipboardExpand all lines: doc/devel/development_workflow.rst
+9-9Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -145,8 +145,8 @@ If you don't think your request is ready to be merged, just say so in your pull
145145
request message and use the "Draft PR" feature of GitHub. This is a good way of
146146
getting some preliminary code review.
147147

148-
Some other things you might want to do
149-
======================================
148+
Manage commit history
149+
=======================
150150

151151
Explore your repository
152152
-----------------------
@@ -163,8 +163,8 @@ To see a linear list of commits for this branch::
163163

164164
.. _recovering-from-mess-up:
165165

166-
Recovering from mess-ups
167-
------------------------
166+
Recover from mistakes
167+
---------------------
168168

169169
Sometimes, you mess up merges or rebases. Luckily, in git it is
170170
relatively straightforward to recover from such mistakes.
@@ -193,8 +193,8 @@ If you forgot to make a backup branch::
193193

194194
.. _rewriting-commit-history:
195195

196-
Rewriting commit history
197-
------------------------
196+
Rewrite commit history
197+
----------------------
198198

199199
.. note::
200200

@@ -285,7 +285,7 @@ to replace your already published commits with the new ones.
285285

286286
.. _rebase-on-main:
287287

288-
Rebasing on ``upstream/main``
288+
Rebase onto ``upstream/main``
289289
-----------------------------
290290

291291
Let's say you thought of some work you'd like to do. You
@@ -363,8 +363,8 @@ to replace your already published commits with the new ones.
363363
.. _force-push:
364364

365365

366-
Pushing, with force
367-
-------------------
366+
Push with force
367+
---------------
368368

369369

370370
If you have in some way re-written already pushed history (e.g. via

‎doc/devel/index.rst

Copy file name to clipboardExpand all lines: doc/devel/index.rst
+117-48Lines changed: 117 additions & 48 deletions
Original file line numberDiff line numberDiff line change
@@ -5,72 +5,141 @@ Contribute
55
##########
66

77
Thank you for your interest in helping to improve Matplotlib! There are various
8-
ways to contribute to Matplotlib. All of them are super valuable! For example:
8+
ways to contribute: optimizing and refactoring code, detailing unclear
9+
documentation and writing new examples, reporting and fixing bugs and requesting
10+
and implementing new features, helping the community...
911

10-
- cleaning up and optimizing the code base
11-
- creating and sharing examples of using the library
12-
- detailing unclear and missing documentation
13-
- reporting and fixing bugs
14-
- requesting and implementing new features
15-
- helping the community with all of the above
12+
.. card::
1613

14+
.. grid:: 1 1 2 2
1715

18-
If you have any questions on the
19-
process or how to fix something feel free to ask on `gitter
20-
<https://gitter.im/matplotlib/matplotlib>`_ for short questions and on
21-
`discourse <https://discourse.matplotlib.org>`_ for longer questions.
16+
.. grid-item::
17+
:class: sd-fs-5
18+
:child-align: spaced
2219

23-
.. rst-class:: sd-d-inline-block
20+
:octicon:`info;1em;sd-text-info` :ref:`Where should I start? <start-contributing>`
2421

25-
.. button-ref:: submitting-a-bug-report
26-
:class: sd-fs-6
27-
:color: primary
22+
:octicon:`question;1em;sd-text-info` :ref:`Where should I ask questions? <get_connected>`
2823

29-
Report a bug
24+
:octicon:`issue-opened;1em;sd-text-info` :ref:`What are "good-first-issues"? <new_contributors>`
3025

31-
.. rst-class:: sd-d-inline-block
26+
:octicon:`git-pull-request;1em;sd-text-info` :ref:`How do I claim an issue? <managing_issues_prs>`
3227

33-
.. button-ref:: request-a-new-feature
34-
:class: sd-fs-6
35-
:color: primary
28+
.. :octicon:`codespaces;1em;sd-text-info` placeholder for codespaces link
3629
37-
Request a feature
30+
.. grid-item::
3831

39-
.. rst-class:: sd-d-inline-block
32+
.. grid:: 1
33+
:gutter: 1
34+
:class-row: sd-fs-5
4035

41-
.. button-ref:: contributing-code
42-
:class: sd-fs-6
43-
:color: primary
36+
.. grid-item-card::
37+
:link: request-a-new-feature
38+
:link-type: ref
4439

45-
Contribute code
40+
:octicon:`light-bulb;1em;sd-text-info` Request new feature
4641

47-
.. rst-class:: sd-d-inline-block
42+
.. grid-item-card::
43+
:link: submitting-a-bug-report
44+
:link-type: ref
4845

49-
.. button-ref:: documenting-matplotlib
50-
:class: sd-fs-6
51-
:color: primary
46+
:octicon:`bug;1em;sd-text-info` Submit bug report
5247

53-
Write documentation
48+
.. grid-item-card::
49+
:link: contributing-code
50+
:link-type: ref
5451

55-
.. toctree::
56-
:maxdepth: 2
57-
58-
contribute.rst
59-
triage.rst
60-
development_setup.rst
61-
development_workflow.rst
62-
testing.rst
63-
document.rst
64-
style_guide.rst
65-
coding_guide.rst
66-
release_guide.rst
67-
dependencies.rst
68-
min_dep_policy.rst
69-
maintainer_workflow.rst
70-
MEP/index
52+
:octicon:`code;1em;sd-text-info` Contribute code
53+
54+
.. grid-item-card::
55+
:link: documenting-matplotlib
56+
:link-type: ref
57+
58+
:octicon:`note;1em;sd-text-info` Write documentation
59+
60+
If you are new to contributing, we recommend that you first read our
61+
:ref:`contributing guide<contributing>`. If you are contributing code or
62+
documentation, please follow our guides for setting up and managing a
63+
:ref:`development environment and workflow<development_environment>`.
64+
For code, documentation, or triage, please follow the corresponding
65+
:ref:`contribution guidelines <contribution_guideline>`.
66+
67+
68+
.. _development_environment:
69+
70+
Development workflow
71+
==============================
72+
73+
.. grid:: 1 1 2 2
74+
75+
.. grid-item-card:: Install
76+
77+
.. toctree::
78+
:maxdepth: 2
79+
80+
development_setup
81+
82+
.. toctree::
83+
:maxdepth: 1
84+
85+
dependencies
86+
Minimum versions <min_dep_policy>
87+
88+
89+
.. grid-item-card:: Workflow
90+
91+
.. toctree::
92+
:maxdepth: 2
93+
94+
development_workflow
95+
96+
97+
98+
.. _contribution_guideline:
99+
100+
Contribution guides
101+
===================
102+
103+
.. grid:: 1 1 2 2
104+
:class-row: sf-fs-1
105+
106+
.. grid-item-card:: Code
107+
108+
| :ref:`coding_guidelines`
109+
110+
.. toctree::
111+
:maxdepth: 1
112+
113+
coding_guide
114+
testing
115+
116+
.. grid-item-card:: Documentation
117+
118+
.. toctree::
119+
:maxdepth: 1
120+
121+
document
122+
style_guide
123+
124+
.. grid-item-card:: Triage
125+
126+
| :ref:`bug_triaging`
127+
| :ref:`triage_team`
128+
| :ref:`triage_workflow`
129+
130+
.. grid-item-card:: Maintenance
131+
132+
.. toctree::
133+
:maxdepth: 1
134+
135+
maintainer_workflow
136+
release_guide
137+
MEP/index
71138

72139
.. toctree::
73140
:hidden:
74141

75-
license.rst
142+
contribute
143+
triage
144+
license
76145
color_changes

‎doc/devel/triage.rst

Copy file name to clipboardExpand all lines: doc/devel/triage.rst
+4Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -62,6 +62,8 @@ The following actions are typically useful:
6262
explores how to lead online discussions in the context of open source.
6363

6464

65+
.. _triage_team:
66+
6567
Triage team
6668
-----------
6769

@@ -121,6 +123,8 @@ can do the following important tasks:
121123
should be closed.
122124

123125

126+
.. _triage_workflow:
127+
124128
A typical workflow for triaging issues
125129
--------------------------------------
126130

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.