Editorial style guide

Read this alongside the Contributor guide, which covers what we publish, how to submit, and the terms that apply.

Last updated: April 2026

Overview

This guide exists to keep v0id_deck consistent in voice, formatting, and presentation across all contributors. All articles are written and submitted in Markdown, as v0id_deck is built on Strapi and renders content natively from .md files.

Read this before submitting. It will save everyone time.

Voice & tone

v0id_deck is a practitioner-run platform. Write accordingly.

Do:

• Write directly. Say what you mean.
• Use first person where appropriate — own your perspective
• Write for a technically literate audience — you don't need to explain what a CVE is
• Be specific. Vague generalisations are filler.
• Show your thinking, including uncertainty and caveats where honest
• Use humour if it's natural to you — we are not a sterile publication

Don't:

• Write like a vendor whitepaper
• Hedge every statement into meaninglessness
• Use buzzwords as a substitute for substance ("leverage synergies", "holistic approach")
• Write a five-paragraph essay introduction — get to the point
• Moralise or lecture — make your argument and let readers decide

Markdown formatting

v0id_deck uses Strapi as its CMS. All articles must be submitted as .md files using standard Markdown syntax. The following conventions apply.

Headings

Use ATX-style headings with # symbols. Do not use underline-style headings (== or --).

# H1 — Article Title (used once, at the top)
## H2 — Major Section
### H3 — Subsection
#### H4 — Use sparingly

• H1 is reserved for the article title only
• Do not skip heading levels (e.g. H2 directly to H4)
• Keep headings concise — they are signposts, not sentences

Paragraphs & line breaks

• Separate paragraphs with a single blank line
• Do not use <br> tags for line breaks — use blank lines
• Keep paragraphs focused. One idea per paragraph.

Emphasis

**bold** — for key terms, warnings, or critical emphasis
*italic* — for titles, technical terms on first use, or light emphasis
~~strikethrough~~ — use sparingly, only where editorially relevant

Do not bold entire sentences or paragraphs. Bold is for emphasis, not decoration.

Lists

Use unordered lists for non-sequential items, ordered lists for steps or ranked content.

- Unordered item
- Another item
  - Nested item (use 2-space indent)

1. First step
2. Second step
3. Third step

Do not mix list styles within the same list. Keep list items parallel in structure.

Code

Use fenced code blocks with a language identifier. Always specify the language.

```python
def example():
    return "always specify the language"
```

```bash
nmap -sV -p 443 target.com
```

```json
{
  "key": "value"
}
```

For inline code (short commands, file paths, variable names), use single backticks:

Run `nmap` against the target, then check `/etc/passwd` for the result.

Links

[Link text](https://example.com)

• Use descriptive link text — not "click here" or bare URLs
• External links open in the same tab by default in Strapi — note this if linking to references
• Do not link every technical term — link where genuinely useful

Images

Do not embed images as base64 in Markdown. Submit image files separately and reference them using standard Markdown syntax:

![Alt text describing the image](image-filename.png)

• Always include meaningful alt text for accessibility
• Use lowercase filenames with hyphens, no spaces: attack-chain-diagram.png
• Supported formats: PNG, JPG, SVG
• Minimum resolution: 1200px on the longest edge

AI-generated images

AI-generated images are permitted as editorial support — cover images and in-article supporting visuals only. They are not accepted as standalone art contributions.

All AI-generated images must be labelled in the caption:

*Conceptual diagram of a phishing attack chain. AI-generated image.*

Brand note: A lazy or generic AI image undermines the v0id_deck aesthetic. If you're using an AI image, make it purposeful and relevant.

Tables

Use standard Markdown tables. Keep them simple — complex tables are hard to read on mobile.

| Column A | Column B | Column C |
|----------|----------|----------|
| Value    | Value    | Value    |
| Value    | Value    | Value    |

Left-align columns by default. Use alignment sparingly and only where it aids readability.

Blockquotes

Use for direct quotations or to call out important statements.

> "The best way to predict the future is to invent it." — Alan Kay

Do not use blockquotes as a styling device for general callout boxes.

Horizontal rules

Use --- sparingly for major section breaks within long articles. Not required for standard sections separated by headings.

Article structure

There is no rigid template, but strong articles generally follow this shape:

1. Hook — why does this matter? Why now? What is the reader going to get?
2. Context — minimum necessary background. Assume technical literacy.
3. Body — your argument, analysis, walkthrough, or story
4. Conclusion — what should the reader take away? What are the implications?

You do not need to label these sections explicitly. Let the content flow naturally.

Attribution & references

• Attribute all quotes, data, and sourced claims inline or via footnote
• Link to original sources where possible
• Do not cite paywalled sources without summarising the relevant content
• For CVEs, link to the NVD entry: https://nvd.nist.gov/vuln/detail/CVE-XXXX-XXXXX
• For MITRE ATT&CK techniques, link to the technique page

Technical terminology

• Spell out acronyms on first use: "Tactics, Techniques and Procedures (TTPs)"
• Use consistent capitalisation: "threat actor" not "Threat Actor", "zero-day" not "0day" in formal text
• Tool names follow their official capitalisation: Nmap, Metasploit, Cobalt Strike, BloodHound
• MITRE ATT&CK technique IDs in parentheses where relevant: lateral movement (T1021)

What we will edit

We will lightly edit for:

• Grammar and spelling
• Markdown formatting compliance
• Broken links
• Heading structure

We will not edit:

• Your argument or conclusions
• Your voice or style
• Technical content we cannot independently verify — we will flag and return these to you

Questions about style or formatting? Reach us at hello@v0iddeck.com