KhronosGroup / KhronosGroup/OpenCL-Docs
Enhancement: generate enums.html from cl.xml
- Dominant language
- Python
- Stars
- 420
- Forks
- 131
- Avg merge
- 5d 13h
- Merged PRs (30d)
- 11
Description
Nothing important, but I just thought I'd mention it:
Given, that there are already [generated refpage contents](https://github.com/KhronosGroup/OpenCL-Docs/pull/67), couldn't [enums.html](https://www.khronos.org/registry/OpenCL/sdk/2.2/docs/man/html/enums.html) also almost completely be generated from [cl.xml](https://github.com/KhronosGroup/OpenCL-Docs/blob/master/xml/cl.xml)?
Contributor guide
Research direction
Compare the generated refpage contents from pull request 67 with enums.html and the source structure in xml/cl.xml. Determine which enum-page content can be generated from cl.xml and what generation entry point is used. Done means enums.html is generated consistently from the XML source rather than maintained separately.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, documentation
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100