letsencrypt / letsencrypt/website
Feature Request - Machine readable version of /certificates
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 909
- Forks
- 591
- Avg merge
- 10h 40m
- Merged PRs (30d)
- 31
Description
I believe it would be useful to have a machine readable version of the information in /certificates. That would allow for client developers and integrators to quickly check if anything has changed, and aid in automatically tracking certificate lineage.
The data could be maintained in a json file, similar to those in /data and it could serve two purposes:
- it could be published statically
- the data file could be used for templating all the language translations of "/certificates". the letsencrypt staff would only have to update one json file to create updates for all the language translation pages.
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
Inspect the existing /certificates page and the JSON-like files in /data first, then trace how the language translation pages are templated. Define the certificate data shape and check how a static machine-readable version could be published; done means the data is available to clients and can drive the translated pages without duplicating certificate information.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- hugo, json
- Domain
- documentation, localization
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100