Analyze PS documentation infrastructure, build tools, and other learning resources

[JordanMartinez]

Here's the kind of questions I'd like to answer:

• Who are the core contributors to the PS language and infrastructure as a whole? (helps us know who has write access to the repos)
• What does PS' main documentation website, Pursuit,
  1. currently do well?
  2. currently do poorly but could be improved in?
  3. currently does not do at all but should be done (i.e. new features that could greatly extend current capabilities)?
• When reviewing build tools integration with Pursuit...
  • what integrates with it
  • how well/poorly does it integrate with it?
  • what are these integrations' main benefits/limitations and why?
• The purs docs command:
  • How does it work?
  • What are its advantages and disadvantages?
  • How could improvements here greatly benefit the entire ecosystem?
• What other learning materials already exist in the PS ecosystem?
  • who wrote them and how active are those people (would they want to be part of a potential documentation team? what are their incentives?)
  • who is their intended audience, what type of documentation are they (i.e. tutorial, how-to, reference, explanation)

[JordanMartinez]

I'll likely do the majority of this work on Saturday, with a little bit of work here and there for the next few days

[JordanMartinez]

Finished by cfb40eb142a47c1b7e93e102ce76846c8ddb6622

There is more work that could be done on various build tools (i.e. purp or `spago). However, since these do not currently integrate with Pursuit, I'm not including them here.