Investigate automation of screenshot capture as part of documentation build process?
Open
Nobody has claimed this yet.
- Dominant language
- Racket
- Stars
- 516
- Forks
- 103
- PR merge metrics
- No merged PRs in 30d
Description
ref #172 @rfindler
update Drracket documentation: Investigate automation of screenshot capture as part of documentation build process?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the referenced issue #172 and the DrRacket documentation build process. Investigate how screenshots are currently captured and where the build is defined. Done means documenting or implementing a decided automation approach for screenshot capture, with the result incorporated into the documentation build.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100