@phpc Working on a DocBook renderer: https://gitlab.com/Girgias/docbook-renderer

Possibly to improve the php.net docs, but also to have a way to properly write articles on my website (which won't get written but *shhh*)

@Girgias @phpc Ooo! I worked on such a thing many years ago, in multiple forms.

I take it you don't care for PhD?

@Crell @phpc PhD is an actual nightmare and a massive blob of code that does way too many things.
And none of the people who actually wrote it, don't contribute to it any more since 2012.

Trying to write this in a sane way, but I'm not even sure I can use static analysis on it because of how I overload the DOMNodes :(

@Girgias @phpc I'll take that as a no...

Of course, using it for PHP.Net makes everything harder because of the "no dependencies" rule.

@hunter @phpc The idea is to avoid endorsing any particular framework or library author. Eg, if PHP.net uses Symfony, the Laravel people would get upset and vice versa.

That's valid but the cost is ignoring the incredibly robust ecosystem of PHP. I'm not convinced that is a good tradeoff any more.

Although, they do use Dokuwiki for the wiki, even though it's 3rd party and a mess. So...

@ramsey @hunter @phpc oh, I thought there was still an unwritten ban on anything 3rd party at all.

I can understand wanting to avoid the "big brands", but especially for something like PhD or the main site, avoiding any library is just self defeating.

@Crell @ramsey @hunter @phpc The main reason my improvements to use composer were rejected for PhD was not the external lib, but needing to maintain something in the build process that is just going to rust away.

The biggest issue with php.net infra is that barely no one has a clue who has access to what antiquated machine that runs what piece of code.

My current plan is, if actually cover what is needed, to just publish a "mirror" myself to convince the swap.