Hey hey.. I've been doing evil again. 😈 I made a docs site today via a crazy prompt. You have got to check this out: https://github.com/cvquesty/voxdocs Here was my prompt:

We're going to write some documentation.  Consider the URL <https://github.com/puppetlabs/docs-archive>. This is the legacy archive of documentation from puppet/perforce.  The documentation is from version 5.x, and is unencumbered by copyright and is free to use by anyone.

Also consider the new OpenVox project here: <https://github.com/openvoxproject>.  OpenVox is an Open Sourced version of Puppet, and has its own community, and the product (found here: <http://yum.voxpupuli.org|yum.voxpupuli.org> and <http://apt.voxpupli.org|apt.voxpupli.org>)

The official site for the current shipping versions of Puppet Core and Puppet Enterprise is at <https://puppet.com> with a git repo of <https://github.com/puppetlabs>.

Finally, consider the documentation here on my desktop "puppet-7.34.0.pdf" and "puppet-8.10.0.pdf"

The task is to develop a complete set of documentation for the OpenVox project. Create the documentation in a conversational/helpful style, cover the current shipping versions of OpenVox, and be certain to avoid copyright issues with official Perforce/Puppet documentation. Also be sure to include atomic references of every binary's command line output. There is a sample server at <http://openvox.questy.org|openvox.questy.org> for which there are SSH keys to connect to that system in /Users/jsheets/.ssh/.

Write at the level of a college senior, do not be afraid to have mild humor in places, and feel free to use all available mechanisms in the Markdown language to produce a complete documentation store in Markdown.  Place the documentation in /Users/jsheets/Projects/voxdocs. To connect to the <http://openvox.questy.org|openvox.questy.org> system, use the user jsheets (ssh <mailto:jsheets@openvox.questy.org|jsheets@openvox.questy.org>) and then use "sudo" to perform the processes you need to

It created what you see there minus me breaking apart a couple markdowns that were literally over 1000 lines long.