@@ -148,6 +148,68 @@ Projects that adopt a SPEC early should engage in the collaborative process
148
148
leading to the SPEC being endorsed by the Core Projects.
149
149
Each SPEC describes what adopting it means in its _ Ecosystem Adoption_ section.
150
150
151
+ #### Badges
152
+
153
+ Projects can highlight their adoption of specific SPECs with a SPEC badge.
154
+ For example, for SPEC 0, we recommend using
155
+
156
+ {{< tabs >}}
157
+
158
+ {{< tab "Rendered badge" >}}
159
+ [ ![ SPEC 0 — Minimum Supported Dependencies] ( https://img.shields.io/badge/SPEC-0-blue )] ( https://scientific-python.org/specs/spec-0000/ )
160
+ {{< /tab >}}
161
+
162
+ {{< tab "Markdown" >}}
163
+
164
+ ```
165
+ [](https://scientific-python.org/specs/spec-0000/)
166
+ ```
167
+
168
+ {{< /tab >}}
169
+
170
+ {{< tab "reStructuredText" >}}
171
+
172
+ ```
173
+ |SPEC 0 — Minimum Supported Dependencies|
174
+
175
+ .. |SPEC 0 — Minimum Supported Dependencies| image:: https://img.shields.io/badge/SPEC-0-blue
176
+ :target: https://scientific-python.org/specs/spec-0000/
177
+ ```
178
+
179
+ {{< /tab >}}
180
+
181
+ {{< /tabs >}}
182
+
183
+ Alternatively, you can use one badge to indicate adoption of multiple SPECS.
184
+ For example, to indicate adoption of SPECs 0, 1, and 4, we recommend the following
185
+
186
+ {{< tabs >}}
187
+
188
+ {{< tab "Rendered badge" >}}
189
+ [ ![ Scientific Python Ecosystem Coordination] ( https://img.shields.io/badge/SPEC-0,1,4-blue )] ( https://scientific-python.org/specs/ )
190
+ {{< /tab >}}
191
+
192
+ {{< tab "Markdown" >}}
193
+
194
+ ```
195
+ [](https://scientific-python.org/specs/)
196
+ ```
197
+
198
+ {{< /tab >}}
199
+
200
+ {{< tab "reStructuredText" >}}
201
+
202
+ ```
203
+ |Scientific Python Ecosystem Coordination|
204
+
205
+ .. |Scientific Python Ecosystem Coordination| image:: https://img.shields.io/badge/SPEC-0,1,4-blue
206
+ :target: https://scientific-python.org/specs/
207
+ ```
208
+
209
+ {{< /tab >}}
210
+
211
+ {{< /tabs >}}
212
+
151
213
### New SPEC Proposals
152
214
153
215
A good SPEC proposal focuses on a single key recommendation or idea for
0 commit comments