operaton / operaton/operaton.org
Fetch types & licenses for Hub page dynamically from issue template
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1
- Forks
- 11
- Avg merge
- 14d 1h
- Merged PRs (30d)
- 2
Description
Currently the issue template for Hub entries and hub.html must be in sync for the given options. In the HTML page the lists should be filled automatically from the issue template. Therefore the template has to be fetched and parsed to render the options.
See this gist for an example to use the GitHub API.
Contributor guide
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 inspecting hub.html and the Hub-entry issue template, then review the linked gist for the GitHub API example. Trace how the page currently defines its type and license options; done means those lists are fetched and parsed from the template so the rendered choices stay synchronized.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, html
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100