✅ Deploy Preview for docssigstore ready!

Name	Link
🔨 Latest commit	cf9df62
🔍 Latest deploy log	https://app.netlify.com/sites/docssigstore/deploys/673bec296221ad00083bcd17
😎 Deploy Preview	https://deploy-preview-346--docssigstore.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@loosebazooka tagging you in case you want to review. CC: @haydentherapper @cmurphy

I'm not sure how I feel about the duplication of information... These tend to go out of date as the source of truth would be sigstore-java? Should this just be an automated pull in of the readme on sigstore-java (or some translation of it)? Alternatively we could include this is a point to update in our release plan, but that does put more work on the devs.

@loosebazooka that makes a lot of sense. @haydentherapper @cmurphy and I are trying to thread a needle a little bit--a little bit of repetition, but increased exposure, and the devs get to primarily work within their own repositories and aren't forced to standardize between the different language clients. We have open PRs for the other language clients too.

@loosebazooka We've tried to find a balance. We want to highlight all clients in the documentation, while leaving deeper technical documentation in the client repo and a responsibility of the package maintainer to keep it up to date. We tried to create a "quickstart" for each client and with documentation that is unlikely to frequently go out of date.

Do you have any suggestions on what we should omit?

Thanks for the comments @haydentherapper I have addressed them and merged main.