ENH: Adding docstub

[bsipocz]

It's ready for the public usage, so time to list on the website

cc @stefanv @lagru

[netlify]

✅ Deploy Preview for tools-scientific-python-org ready!

Name	Link
🔨 Latest commit	e105bde
🔍 Latest deploy log	https://app.netlify.com/projects/tools-scientific-python-org/deploys/682e744a2b834a0008edc1ff
😎 Deploy Preview	https://deploy-preview-71--tools-scientific-python-org.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 99 Accessibility: 96 Best Practices: 100 SEO: 100 PWA: - View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[stefanv]

@lagru Happy to put this up, if you think you're ready for some more eyes on the project!

[lagru]

Happy too! But could we wait until I've completed the minimal documentation (scientific-python/docstub#24)? I'd like to give first users at least a chance to grok the concepts involved. 😅

After that I'll release v0.3 and approve this. 😊

[bsipocz]

Sounds like a plan, thanks!

[lagru]

Fyi, preparing docstub 0.3.0 in scientific-python/docstub#51.

[lagru]

Okay, I released version 0.3.0.post0. After some annoying shenanigans, I had to make a post release. It seems that my deployment workflow didn't really agree with me tagging the same commit with 0.3.0rc0 and 0.3.0. I think while pushing the final release, setuptools still tried to use the 0.3.0rc0 instead of 0.3.0. Couldn't reproduce that locally.

So note to myself, always make sure that release tags point to different commits. Even if that means unnecessarily pushing something. 😅