dev-sec / dev-sec/dev-sec.github.io
How to use documentation
Open
Nobody has claimed this yet.
- Dominant language
- SCSS
- Stars
- 22
- Forks
- 15
- Avg merge
- 4h 41m
- Merged PRs (30d)
- 1
Description
Very simple step-for-step documentation how to use dev-sec assets would be nice (I get a such questions quite often), something like "Getting started guide":
- step for step docs how to install inspec and run it with particular baseline
- step for step docs how to apply hardening with ansible/puppet/chef
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
Review the existing documentation structure in the dev-sec.github.io project before choosing where the guide belongs; no specific file or test is named. The work is complete when a step-by-step guide covers installing InSpec and running a baseline, plus applying hardening with Ansible, Puppet, and Chef.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible
- Domain
- devops, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100