We made an MCP Server so that Cursor can build anything from API Docs

https://www.npmjs.com/package/apidog-mcp-server

The Python version diagram has been updated to show the bugfix/security split for each release. (Before, the bars were either completely green or yellow.)

https://devguide.python.org/versions/

It's also zoomed in and shows fewer releases than before. There's another chart further down the page showing all of 2.6 to 3.14. And the wording in the status key has been refreshed to make it clearer.

Thanks to @nedbat and @encukou for updating it!

I like the idea of #Docs, an #OpenSource alternative to Google Docs developed by the French and German governments, compliant with #GDPR, and hosted outside the US.
https://docs.numerique.gouv.fr

But I'm having trouble finding reviews, perhaps because it's new or because it has such a generic name. Can anyone point to helpful reviews?

Interesting:
Docs is the result of a joint effort lead by the French (DINUM) and German governments (ZenDiS). We are always looking for new public partners (we are currently onboarding the Netherlands ). Feel free to reach out if you are interested in using or contributing to docs.

https://docs.numerique.gouv.fr/login/

French gov's open source alternative to Notion or Outline

https://github.com/suitenumerique/docs

"[T]he lack of a clear entry path makes the profession less accessible, contributing to a lack of diversity in tech writing teams. If technical writing is to remain relevant in an industry that values innovation and inclusion, it needs to welcome new voices.

Fixing this problem won’t happen overnight, but there are steps companies and the broader industry can take to rebuild the pipeline for entry-level talent:

- Reintroduce mentorship programs.
- Companies can pair senior writers with juniors to share knowledge and help newcomers build confidence.
- Redefine “entry-level” roles.
- Stop asking for years of experience in entry-level job postings. - Focus instead on transferable skills like writing, research, and adaptability.
- Create apprenticeships or internships.
- Paid opportunities to learn on the job can give aspiring writers the experience they need to land full-time roles.
Invest in training.
- Documentation teams should have budgets for upskilling new hires — not just hiring pre-trained professionals."

https://willkelly.medium.com/how-the-technical-writing-profession-betrayed-entry-level-tech-writers-8a0c05617efd

Here is a Rust trick for keeping your documentation up-to-date!

**cargo-sync-rdme**: Synchronize README with crate docs.

Uses markers in README, supports configuration!

GitHub: https://github.com/gifnksm/cargo-sync-rdme

“Fortunately, I think there’s a good alternative to the dismal picture of brain-dead tech writers pressing buttons on AI machines and passing the content to SMEs for review. That alternative is to focus on what AI algorithms can’t do (at least not with a few button clicks). In this revised approach, tech writers offload the simple tasks to AI tools to fix while focusing their real time and energy on more complex, ambitious tasks that are beyond the straightforward capabilities of AI tools.

When I say beyond AI capabilities, I still mean AI tools might assist or augment tech writers in the work; it’s just that the tasks aren’t as simple as the mechanical tasks of fixing doc bugs that I described earlier (e.g., “what’s the issue? what’s the fix?”).

For example, when I set about creating complex tree diagrams showing all elements in an API, this was a new kind of documentation that hadn’t been done before at my company. It became an instant hit and one that proved challenging to maintain and grow and fix, but still worthwhile. (In fact, in a chat with a product manager last week, he wondered if our tree diagram page wasn’t the most popular page in our documentation.)

If we focused more on these sophisticated tasks (beyond click-button AI), I think tech writers could have a brighter future.”

https://idratherbewriting.com/blog/recursive-self-improvement-complex-tasks

I’ve been playing around with Codapi. It lets you make interactive code examples in your docs, blog, etc.

Instead of just reading, readers can play around with them—making learning way more fun and hands-on!

Great work! @antonz

https://github.com/nalgeon/codapi

Using GitHub Copilot code review - Now in VS Code!

https://docs.github.com/en/copilot/using-github-copilot/code-review/using-copilot-code-review?tool=vscode

Our documentation just got a big upgrade! Check out the new site at https://hushline.app/library!

We'll also start publishing all of our blog articles here, too!

New issue of Herding Cats is out, this time exploring routines and how to disrupt them for #OpenSource adoption in the public sector.

I'm also happy to share #Docs, a new tool for collaborative note-taking and a joint production by German and French developers Plus, a short recap of the recent #EUOS Week, including the announcement of a 2025 UN OS Week

https://herdingcats.ghost.io/flexible-technologies-inflexible-routines/

Here is something I would like to give to the community.

I love doing #documentation
It started out of necessity, because as you well know. Most #docs are useless. I was looking for a simple, concise but information dense means to document systems.
Did not find anything that quite fit the bill.

So, I have developed the means to document your entire system on a single page. Feel free to adopt this schema, all I ask is you refer to this method as "Wulf diagram"

I have once developed a means to diagram network latency service levels, and it hurt that a multinational service company kept using it without acknowledging.

This particular diagram is a sanitised version of a Minecraft server I deployed for my younger family.

From the top;
The diagram is divided into three bands;
SERVICES (visible outside)
CORE
INGRESS (accessing backend)

You can put whatever you want there. Usually the bits that make you ask yourself "How did I do that bit again?". Including passwords, scripts, pathing etc.

The big font is so you can see what system it is scrolling through pages.
The software used is Office Libre draw.

Is it perfect? No.
But it sure is better than what I have found out there (prove me wrong)

If you're programming/coding I'd love your help here:

What are some of the best examples you've seen (that are public/I can view - any language is fine) of programming tutorials and/or example code?

I'm looking for the best examples that illustrate how a a program is put together, the patterns it's using, so that you do the same yourself.

Nitrocid service packs will get their own stable documentation.

#Nitrocid #NitrocidKS #KernelSimulator #TechNews #csharp #programming #dotnet #docs #gitbook

https://officialaptivi.wordpress.com/2025/02/06/nitrocid-stable-documentation-will-be-split-soon/

I think that each library that has documentation should also expose its offline version by creating, publishing, and maintaining easy-to-use Docker images for the community.

The Netatalk manual can now be localized to other languages!

In the latest bleeding edge code, the entire documentation suite has been converted from old school DocBook to glorious Markdown.

Here's a preview version published to the website, but not linked to from anywhere yet: https://netatalk.io/manual/en/

As part of the transition, I applied a gettext based localization framework using po4a. With just a few steps, new languages can be added!

If someone feels crazy enough to take on translation of just under 1200 paragraphs of technical documentation, I'd love to hear from you. I have a getting started guide lined up. :)

I teased this over the weekend and the Draft documentation website is now live! It's just the scaffolding for now but we'll be adding actual documentation pages to it soon.

https://draft.steady-bytes.com/