A docs‑as‑code repository for offensive cybersecurity engagements—organized by the Diátaxis framework—to teach and reference penetration testing tactics, techniques, and procedures.
/
├── docs/ ← All MDX source content
│ ├── concept/ ← Concept guides (e.g. “What is Reconnaissance?”)
│ ├── how-to/ ← Step‑by‑step recipes (e.g. Reconnaissance how‑to)
│ ├── tutorial/ ← End‑to‑end walkthroughs (e.g. Full pentest lab build)
│ └── reference/ ← Cheat‑sheets and API/attack technique reference (e.g. Injection payloads)
├── assets/ ← Images, SVGs, example payload files
│ ├── img/
│ └── samples/
├── .github/
│ └── workflows/docs-ci.yml ← CI: lint, link‑check, build, deploy previews
├── tests/ ← Link‑checker & snippet validation configs
├── docusaurus.config.js ← Docusaurus configuration
├── sidebar.js ← Docusaurus sidebar structure
├── openapi.yaml ← (Optional) API specs for reference generation
├── package.json ← Build scripts & dependencies
└── README.md ← This overview & developer guide
-
Clone the repo
git clone git@github.com:ObsidianStrike/cybersec-writeups.git cd cybersec-writeups -
Install dependencies
npm ci
-
Run locally
npm run start # Opens http://localhost:3000 with hot‑reload
- Fork the repo and create a feature branch:
git checkout -b feature/<quadrant>/<short-desc>
- Write your content under the appropriate
docs/<quadrant>/folder. - Preview locally with
npm run start. - Submit a PR targeting
main, linking to an issue if applicable. - At least one peer review is required before merge.
See CONTRIBUTING.md for style guidelines and branch naming conventions.
- Lint:
npm run lint:md(Markdown linting) - Link‑check: via
tests/link-check.config.json - Build:
npm run build - Preview Deploy: on PRs via GitHub Pages previews
- Concept: “What” & “Why” (e.g., web app pentest overview)
- How‑To: Task‑oriented recipes (e.g., reconnaissance steps)
- Tutorial: Guided, end‑to‑end labs (e.g., build a vulnerable app)
- Reference: Concise cheat‑sheets (e.g., injection payload library)
This project is licensed under the GNU General Public License v3.0.
- Add “Was this page helpful?” at the bottom of each doc.
- Track page views via Plausible (or your analytics tool).
- File issues for typos, content gaps, or outdated references: New Issue.
Thank you for making our docs better!