Sops needs a Website / Docs site / Logo
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.1k
- Forks
- 1.1k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 9
Description
Big fan of sops -- I use it on all new projects. I'm giving a talk at a lookup DevOps meetup about sops in the coming few days and I realized that this awesome project doesn't have a great online presence outside of this repo and its corresponding README. I definitely believe it deserves one and I'd love to see that happen! Just figured I'd drop this thought here for ya'll to mull on.
Thanks!
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 reviewing the repository README and the existing project context to determine what an online presence would need. The issue mentions a website, a documentation site, and a logo, but does not identify files, tools, or acceptance criteria; completion would require defining and delivering that broader scope.
Written by the indexing model from the issue text.
Assessment
- Domain
- design, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100