Add SPEC badge recommendation

[jarrodmillman]

Close#240. See https://deploy-preview-305--scientific-python-specs.netlify.app/specs/purpose-and-process/#badges

TODO after getting feedback

• Update quickstart.py
• Update Ecosystem Adoption section of existing SPECs
• Add layouts/shortcodes/spec_badge.html to scientific-python.org repo. It is something like:

{{- $number := .Get "number" }}
{{- $title := .Get "title" }}
{{- $tabs := slice }}
{{- $name := "Rendered badge" }}
{{- $content := printf "[![SPEC %s — %s](https://img.shields.io/badge/SPEC-%s-blue)](https://scientific-python.org/specs/spec-%0*s/)" $number $title $number 4 $number }}
{{- $tabs := $tabs | append (dict "name" $name "content" $content) }}
{{- $name := "Markdown" }}
{{- $content := printf "`[![SPEC %s — %s](https://img.shields.io/badge/SPEC-%s-blue)](https://scientific-python.org/specs/spec-%0*s/)`" $number $title $number 4 $number }}
{{- $tabs := $tabs | append (dict "name" $name "content" $content) }}
{{- $groupId := .Page.Scratch.Get "tabgroup" | default 0 -}}
{{- .Page.Scratch.Set "tabgroup" (add $groupId 1) -}}
{{ partial "_elements/tabs" (dict "ctx" . "tabs" $tabs) }}

[lagru]

Looks good.

By the way I really loved the green color scheme from the meeting notes! Looks like the colors of the SP logo (if not the same even).

[stefanv]

This is fine as-is, but perhaps we also want to add a reminder along the lines of "Not all SPECs are applicable to all projects, so there is no need to try and 'earn' all badges."

[tupui]

This is fine as-is, but perhaps we also want to add a reminder along the lines of "Not all SPECs are applicable to all projects, so there is no need to try and 'earn' all badges."

Though at first maybe it's a good thing as people are more reluctant than anything else at the moment 😅 so if that can somehow motivate more people to look into it, why not I would say!

[jarrodmillman]

[Carreau]

I don't think we really need table for such short snippets.

This is good to see how tabs work, but I think in the long run when snippets are only 1 or 2 lines we can "untabify".

[jarrodmillman]

With tabs

[jarrodmillman]

Without tabs

[jarrodmillman]

It would be great if the @scientific-python/spec-steering-committee could vote for which of the two options above they prefer:

option 1 without tabs 🎉
option 2 with tabs 🚀

[ivanov]

I know I'm a dinosaur - but I appreciate the fact that without tabs works when I have javascript disabled, and has the proper context when rendered in a text-only browser (w3m in my case). (There are ways to make the tabbed version work without javascript too, using a combination of CSS and anchors)

[stefanv]

We could add noscript fallbacks, but then we'd want to do it everywhere JS is used (shortcut sidebar, eg). We don't have the bandwidth for that work built into our roadmap, but if the changes are not too invasive, we'd certainly consider such contributions to the theme.

[stefanv]

(As an aside, we do prioritize accessibility, albeit with JS enabled.)