-
Notifications
You must be signed in to change notification settings - Fork 293
ARCHIVE: Redesign 2019
Will Coleda edited this page Mar 10, 2023
·
1 revision
Notes from 2019
The original design of the documentation system comes from the pre-Christmas release dark times. It's been (mostly) working ever since, but it's showing its age. Here are a few proposals for its change.
- It would be interesting to first have a look at the objectives we want to achieve with this redesign.
- A Redesign of the Raku Documentation System by Richard Hainsworth is probably the most complete.
- Previously, Tom Browder proposed a reorganization.
- Even before that, ab5tract proposed a p6doc server
- Any redesign will need a test suite. Richard Hainsworth proposed one.
- Redesign should start with a reformulation of data and metadata for files in the repository. Here's a proposal for the document file specs.
From time to time, a squashathon is proposed. Here's a guide on how to work with that.