theupdateframework / theupdateframework/theupdateframework.io
Make implementations more visible
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 25
- Forks
- 46
- PR merge metrics
- No merged PRs in 30d
Description
Followup to #85. From a Slack #tuf comment:
Radoslav Dimitrov: Great work! 🙌 Does it make sense to have a page listing the existing implementations and tools build on top under the official org, i.e. python-tuf, go-tuf, tuf-on-ci, the conformance test suite, etc.? That can help steer people to the right tools.
@chalin: ... something like this : https://docsy--theupdateframework.netlify.app/docs/getting-started/#implementations?
RD: Maybe the suggestion can be updated to have these somewhere more visible
I agree that it can be made more visible. I'd suggest using the third entry (the right-most one) of the "features ribbon" of the site landing page to highlight implementation.
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 at the site landing page and inspect the features ribbon, focusing on its right-most entry. Make the existing implementations and related tools more visible there, and confirm that the landing page clearly directs visitors to them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 63/100