You can add a bit of JavaScript to automatically activate the relevant tab based on the reader's operating system, so they see the relevant info sooner.
📗 The dated Lucida Grande was the Mac system font a decade ago and used for the docs on Mac (and only Mac). We now use the system font stack, to get a similar result to Linux, Windows, Android and iOS. https://systemfontstack.com
Boost to save a writer's life: you can block that fucking @ popup on GoogleDoc newlines (they added it super recently) by hacking your adblocker. Basically add "docs.google.com###docs-instant-bubble" as a new line in your My Filters list on uBlock or similar.
Whether it's your very first contribution to an open-source project, or you're translating our docs, or you're contributing a how-to recipe, or you're preparing the accompanying documentation for your new Astro feature... we have a guide for that!
Want to level up your open-source documentation skills? We even have guides for reviewing docs PRs: what we look for when we work with, and bring out the best in, your contributions to us.
If you want to contribute to @astro Docs, or you're looking for some guidance you can follow to create your own project's docs, we hope you'll find our resources helpful.
et donc ouais, quand on veut stocker ses infos de profil facebook dans un truc comme google doc, le transfert refuse de fonctionner si on n'autorise "que les fichiers qui viennent de facebook". Il faut EN PLUS cocher la case obligatoire "TOUS les fichiers google docs" que Meta a ainsi le droit de modifier, éditer, supprimer etc.
What if your class api docs, generated by @phpdoc would be available via an api?
I'm trying to find a way to create inter project references, that allow your api to consume the docs of your dependencies.
For example, if you base a project on classes from your framework, extend the base classes, implement interfaces. I think it would be nice to have that in your docs. With links to the original source.
🆕 When you visit https://docs.python.org you can now hit the forward slash key ➡️ / ⬅️ to highlight the search box, and immediately start typing your query. Try it!
The Fedora Docs team have done the first onboarding session. If you missed it, you still have a chance to drop into a Jitsi meeting on 18:00 UTC later. Peter and I will greet you. See you then.
Come along to the writing workshop hosted by the Fedora Docs team on Thursday 28 September 12:00 → 12:30 and 18:00 → 18:30 (UTC). Choose one that suits your timezone.
No registration is necessary. Just write your name or nick on Jitsi Meet UI before you click 'join meeting'.