Thanks a lot!

I've been so buried in my own drafts I didn't realize how bad the actual guideline page was.

It's not hard to preview things directly in the browser from the PR; I did that and it certainly looks better.

@tibbs similarly to you, fixing this was an (undesired) side-effect of doing something else, so I did not really bother with previews ;)

@ignatenkobrain I see the updated version is already on docs. Is there a chance to add some reference from which commit it was actually generated, so I could be able to see what is the actual version comparing to the sources? Or is it somehow automatically published after commit/merge?

@ignatenkobrain there is still broken "Package Versioning Examples" link. It does not look we have that page in new documentation ....

That page was never really completed. My original intent was that the examples page would stay in the wiki and not be under Packaging at all, so that the community could provide examples. But given how easy it is for someone to send a PR now, I guess it's not really a problem to have it under the examples section in these new guidelines pages.

Still, it would need to actually be written. I have done some private work on that in concert with the other work I've been doing for the versioning overhaul, and will provide some content for that page once we actually decide what we're going to do.

As for indicating the docs pages, that is all still under development. I think the rebuilds still happen manually though I believe the plan is to have them driven by commits. (I can't comprehend why they aren't at least done by a cron job that runs a few times an hour, but it's not my system.) I would assume there must be some way to indicate the point HEAD was at when they were generated, but I have no idea how to do it.