status/2026Q3/doceng: Add doc project report

[ziaee]

Summary

I have never done a doceng report before. To be honest, I do not feel
that the template we used historically is meaningful today*. The needle
on translations** does not move. Actually people send in translations on
github and nobody reviews them, and then the submitter garbage collects
their branch. What is meaningful I think are the many projects in the
tree that we should showcase. So, here is a first draft at that, it
probably needs some help.

Please tell me about your projects or offer corrections!

*: Actually I think we should nuke freebsd.org/docpro*. Nobody is
maintianing it, all of the information is available elsewhere, and
docs.freebsd.org is understood to be the projects homepage now. The only
attention it gets is pruning stale links for several years now.

**: Except the Russian translations get a lot of love.

[maxim]

This is probably not the right forum to discuss this but I cannot help but comment:

The needle on translations** does not move.

I have been contemplating this issue for good decade, outside of FreeBSD as wll, and see several possible reasons for that. Some of them are that with the modern tools (a) having a translation is not that necessary anymore and is not a significant issue as it used to be (b) it could be done consumer side automatically with adequate quality and negligible cost. One can argue that the end user <> documentation way of interaction has already changed to the point where the end user rarely actually reads anything on docs.freebsd.org themself. In short, maybe the needle doesn't move simply because there is no need for it to.

I deliberately leave out the elephant in the room question of whether we as the project want to adopt modern practices of working with documentation or keep the traditional way (i.e., pretend nothing happening).

[maxim]

The report looks good.