I "love" this...
In work I sometimes look for some #docs online about some #software, possible service to hosting on-premise or something similar. I naively believe its authors website would be the best source.
What I expect: technical info how it's created and how it works.
What I see: "We improved ways to do [insert something I want to achieve] in most efficient ways! Many companies trusted us! Check our X, Y, Z product for A, B, C problem! [sponsors' logos in bottom part of site]"
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.
Good docs always make me smile. Translating terms across knowledge domains is essential so people can map what they already know onto your API. #python#fastapi#docs#technicalwriting
🆕 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'.
Man I didn't even notice #Flathub now has a dedicated page for its #docs. So much better than the old READMEs on GitHub style! https://docs.flathub.org/
Let's get this out of the way: they give a number of #reasons why #webservers "might wish" to establish that a web #client is running on a "#trusted" software stack, including things like "make sure other game players aren't cheating" and "ensure I'm talking to another human".
If not using a Google-endorsed #browser means #losing#access to all of that, most people are not going to be able to make that choice. They're going to have to use #Chrome, and they'll have to put up with it shoving "#interstitial ads" (aka all-encompassing #TV#commercials in the middle of your attempt to use the service) and a million other ads.
Org provides methods to create a link in the correct syntax, to insert it into an Org file, and to follow the link.
The main function is 'org-store-link', called with 'M-x org-store-link'. ... It stores a link to the current location.
I didn't realize such stored links then suggested for completion on 'M-x org-insert-link ('C-c C-l).
I thought I knew #Python until I read this. The plugins' functionality was quite interesting, and I have a few ideas about what I can use it for. One thing I miss in Python that I often use is in #CPP are true abstract classes, overloading, and extension of classes. With tools like this, you can achieve similar functionality.
Normally, after reading an article like this, I like to go back to the official #Python documentation. Articles like this teach by example and plant seeds, terms, words, and concepts in your brain. Going back to the documentation, you then get a better understanding of what you read. It also gives more meankng and some sense to the chaos that documentation can often introduce.