Wen Kokke
Wen Kokke
The current build script no longer builds the PDF. However, it should be easy to adapt the task that builds the EPUB into a task that generates one massive LaTeX...
A partial solution would be, for each library, to: - generate an `Everything.agda` in `_cache/` which imports all modules in a set of libraries; - run Agda once to highlight...
Suggested workflow: 1. Open an issue describing the proposed contribution; 2. Discuss proposal with existing contributors; 3. Create pull request for contribution; 4. Publish contribution with `draft` tag, which labels...
Add [branch protection](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule) on dev to enforce a workflow using PRs.
The build and tests generate reports: - **Shake**: already generated, see: [Makefile#L35](https://github.com/plfa/plfa.github.io/blob/c0464e4e31679c59291ec6198008d8f9b28617e3/Makefile#L35) - **HTMLProofer**: see [HTMLProofer: Reporting](https://github.com/gjtorikian/html-proofer#reporting) - **html-validate** - **EPUBCheck**: see [EPUBCheck: Getting a report in a structured format](https://www.w3.org/publishing/epubcheck/docs/cli/#getting-a-report-in-a-structured-format)...
- [ ] Write rule which compiles TeX documents - [ ] Remove course PDFs from repository
- [ ] Add descriptions to all footnote links, as done in [5827bc3](https://github.com/plfa/plfa.github.io/commit/5827bc3f0f8172b80c0fb9ec012ffcf83ce3a658#diff-f7ccb94ec731d3f9c0776f6dd4489addf172c7d3f590a39acc2a5cfe575688fdR7) - [ ] Automatically add descriptions to links generated by Agda
- [ ] Move `web/CONTRIBUTING.md` to `CONTRIBUTING.md` - [ ] Describe directory structure: + chapters in `src/` + courses under `courses/` + resources for building website under `web/` + resources...
Currently, the numbers of the book parts are hardcoded as part of their titles. This won’t play well with formats which automatically number sections, such as LaTeX and EPUBs, and...
In order to draft a new release, I believe we should fix all the issues tracked by the [22.07](https://github.com/plfa/plfa.github.io/milestone/1) milestone, then release the new version following [the instructions](https://plfa.github.io/Contributing/)—which will become...