Page History

...

•  Write Doc: Why would a project want to come to the ASF (ie, our value proposition to an existing project - what benefits will they get that justify the costs?). See also: the Incubator: why would someone want to bring their community here?
•  Define simple style/layout guides for new content on the website.  Very simple best practices for any style, document structure, or the like guides are helpful for people creating new content (or taking the time to migrate/update existing content).  In particular: past complaints are often "it's a wall of text", so when should writers include images/etc. in content, and what's the simplest way to do so consistently?  See also: https://photos.apachecon.com/ for imagery.
•  Draft ideas for navigation/pathing: the current website serves multiple audiences and topics.  Starting to define how an overall navigation structure will help lead people to where they want to go is useful.
•  

  Onboarding documents for major audiences (Contributor, Committer, PMC member, ASF Member, Director). Some of these exist, but can be improved. Some do not exist in an organized fashion. All need to be made more consistent in scope and format, and more discoverable in the usual places.  START HERE: Proposal: Improving Onboarding Experiences

•  

  Explain the why of quarterly project reporting. Who should you report to? (Board vs Stakeholders are separate reports, with different tones and purposes, for example.). See also the official policy/guidance: https://apache.org/foundation/board/reporting See also the PMC guide: https://community.apache.org/pmc/reporting and See also the report wizard https://reporter.apache.org/

...