Add comprehensive cheat sheet creation guide (GUIDELINE.md) #1768

packtman · 2025-08-26T11:37:09Z

Issue Reference #1745

Summary

Added a comprehensive "How To Make A Cheatsheet" guide to help contributors create effective security cheat sheets.

Changes Made

Created GUIDELINE.md with detailed guidance for cheat sheet creation
Updated README.md to reference the new guide
Updated CONTRIBUTING.md to reference the new guide

Benefits

Helps new contributors understand how to create quality cheat sheets
Provides comprehensive best practices and templates
Improves the contribution experience for the community

…e documentation references

jmanico

Excellent!

jmanico · 2025-08-26T13:34:40Z

There are several lint errors, for example:

GUIDELINE.md:1 MD022/blanks-around-headings Headings should be surrounded by blank lines [Expected: 1; Actual: 0; Below] [Context: "# Cheat Sheet Creation Guide"]
GUIDELINE.md:2 MD022/blanks-around-headings Headings should be surrounded by blank lines [Expected: 1; Actual: 0; Above] [Context: "## How to Create Comprehensive Security Cheat Sheets"]
GUIDELINE.md:9:1 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1]
GUIDELINE.md:47 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- Developers: Code examples, i..."]
GUIDELINE.md:53 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- Beginner: Basic concepts, st..."]
GUIDELINE.md:61 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- [ ] Existing Coverage: Check..."]
GUIDELINE.md:85 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- Comprehensive Coverage: 3,00..."]
GUIDELINE.md:91 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- Background & Theory: 20%"]
GUIDELINE.md:118 MD036/no-emphasis-as-heading Emphasis used instead of a heading [Context: "1. Background & Context"]
GUIDELINE.md:119 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- Problem statement"]
GUIDELINE.md:123 MD036/no-emphasis-as-heading Emphasis used instead of a heading [Context: "2. Threat Analysis"]
GUIDELINE.md:124 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- Attack vectors"]
GUIDELINE.md:128 MD036/no-emphasis-as-heading Emphasis used instead of a heading [Context: "3. Prevention Strategies"]
GUIDELINE.md:129 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- Defense in depth approach"]
GUIDELINE.md:133 MD036/no-emphasis-as-heading Emphasis used instead of a heading [Context: "4. Implementation Guide"]
GUIDELINE.md:134 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- Step-by-step instructions"]
GUIDELINE.md:138 MD036/no-emphasis-as-heading Emphasis used instead of a heading [Context: "5. Testing & Validation"]
GUIDELINE.md:139 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- Verification methods"]
GUIDELINE.md:143 MD036/no-emphasis-as-heading Emphasis used instead of a heading [Context: "6. Monitoring & Maintenance"]
GUIDELINE.md:144 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- Ongoing security measures"]
GUIDELINE.md:148 MD036/no-emphasis-as-heading Emphasis used instead of a heading [Context: "7. References & Resources"]
GUIDELINE.md:149 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- Further reading"]
GUIDELINE.md:158 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- Hierarchical Structure: Use ..."]
GUIDELINE.md:164 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- Clear & Descriptive: Section..."]
GUIDELINE.md:172 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- Related Cheat Sheets: Links ..."]
GUIDELINE.md:178 MD031/blanks-around-fences Fenced code blocks should be surrounded by blank lines [Context: "markdown"] GUIDELINE.md:193 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- Clear Language: Avoid unnece..."] GUIDELINE.md:209 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- Code examples in multiple la..."] GUIDELINE.md:215 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- Threat analysis and risk ass..."] GUIDELINE.md:221 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- System-level security consid..."] GUIDELINE.md:227 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- Deployment and configuration..."] GUIDELINE.md:246 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- Problem-Solution: Identify p..."] GUIDELINE.md:272 MD031/blanks-around-fences Fenced code blocks should be surrounded by blank lines [Context: "java"]
GUIDELINE.md:279 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- Language-Specific: Provide e..."]
GUIDELINE.md:302 MD031/blanks-around-fences Fenced code blocks should be surrounded by blank lines [Context: "nginx"] GUIDELINE.md:313 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- Flow Diagrams: Attack vector..."] GUIDELINE.md:319 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- Clear & Simple: Avoid overly..."] GUIDELINE.md:329 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "1. Problem Statement: What sec..."] GUIDELINE.md:337 MD031/blanks-around-fences Fenced code blocks should be surrounded by blank lines [Context: "markdown"]
GUIDELINE.md:364 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "1. Network Layer: Network-leve..."]
GUIDELINE.md:370 MD031/blanks-around-fences Fenced code blocks should be surrounded by blank lines [Context: "markdown"] GUIDELINE.md:397 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "1. Design Phase: Security cons..."] GUIDELINE.md:542 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- Security Experts: Validate s..."] GUIDELINE.md:548 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "1. Initial Review: Technical a..."] GUIDELINE.md:556 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- Technical Writers: Review cl..."] GUIDELINE.md:562 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- Technical Accuracy: All info..."] GUIDELINE.md:572 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- Functionality: Code examples..."] GUIDELINE.md:578 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "1. Unit Testing: Test individu..."] GUIDELINE.md:586 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- Comprehension: Target audien..."] GUIDELINE.md:592 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- User Testing: Have target us..."] GUIDELINE.md:615 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- New Vulnerabilities: Update ..."] GUIDELINE.md:621 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- Critical: Security vulnerabi..."] GUIDELINE.md:645 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- What Changed: Document speci..."] GUIDELINE.md:651 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- Content Updates: New informa..."] GUIDELINE.md:661 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- User Surveys: Regular feedba..."] GUIDELINE.md:667 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- Content Quality: Accuracy, c..."] GUIDELINE.md:675 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- Content Gaps: Identify missi..."] GUIDELINE.md:681 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "1. Identify Opportunities: Gat..."] GUIDELINE.md:863 MD022/blanks-around-headings Headings should be surrounded by blank lines [Expected: 1; Actual: 0; Below] [Context: "### 7.2 Advanced Template Features"] GUIDELINE.md:864 MD031/blanks-around-fences Fenced code blocks should be surrounded by blank lines [Context: "markdown"]
GUIDELINE.md:945 MD022/blanks-around-headings Headings should be surrounded by blank lines [Expected: 1; Actual: 0; Below] [Context: "### Further Reading"]
GUIDELINE.md:946 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- [OWASP Cheat Sheets Series](..."]
GUIDELINE.md:950 MD022/blanks-around-headings Headings should be surrounded by blank lines [Expected: 1; Actual: 0; Below] [Context: "### Tools & Templates"]
GUIDELINE.md:951 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- [Markdown Guide](https://www.../"]
GUIDELINE.md:955 MD022/blanks-around-headings Headings should be surrounded by blank lines [Expected: 1; Actual: 0; Below] [Context: "### Community"]
GUIDELINE.md:956 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- [OWASP Community](https://ow.../"]
GUIDELINE.md:961:142 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1]

packtman · 2025-08-29T17:39:06Z

Will fix the errors this weekend 👍

jmanico · 2025-09-01T15:29:02Z

A few more still exist : GUIDELINE.md:124 MD036/no-emphasis-as-heading Emphasis used instead of a heading [Context: "1. Background & Context"]
GUIDELINE.md:130 MD036/no-emphasis-as-heading Emphasis used instead of a heading [Context: "2. Threat Analysis"]
GUIDELINE.md:136 MD036/no-emphasis-as-heading Emphasis used instead of a heading [Context: "3. Prevention Strategies"]
GUIDELINE.md:142 MD036/no-emphasis-as-heading Emphasis used instead of a heading [Context: "4. Implementation Guide"]
GUIDELINE.md:148 MD036/no-emphasis-as-heading Emphasis used instead of a heading [Context: "5. Testing & Validation"]
GUIDELINE.md:154 MD036/no-emphasis-as-heading Emphasis used instead of a heading [Context: "6. Monitoring & Maintenance"]
GUIDELINE.md:160 MD036/no-emphasis-as-heading Emphasis used instead of a heading [Context: "7. References & Resources"]
GUIDELINE.md:295 MD031/blanks-around-fences Fenced code blocks should be surrounded by blank lines [Context: "java"] GUIDELINE.md:326 MD031/blanks-around-fences Fenced code blocks should be surrounded by blank lines [Context: "nginx"]
GUIDELINE.md:912 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "- [Related Cheat Sheet 3](link..."]
GUIDELINE.md:913 MD031/blanks-around-fences Fenced code blocks should be surrounded by blank lines [Context: "```"]
GUIDELINE.md:1017:142 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1]
Error: Process completed with exit code 1.

jmanico · 2025-09-05T14:53:04Z

One markdown bug left!

GUIDELINE.md:295 MD031/blanks-around-fences Fenced code blocks should be surrounded by blank lines [Context: "```java"]

GUIDELINE.md

mackowski · 2025-09-08T09:29:59Z

GUIDELINE.md

+- Functionality: Code examples work as intended
+- Security: Examples implement security best practices
+- Compatibility: Examples work across different environments
+- Performance: Examples don't introduce performance issues


IMO remove this

Just the performance part of Testing criteria section?

IMO only Performance

mackowski · 2025-09-08T09:30:05Z

GUIDELINE.md

+1. Unit Testing: Test individual code examples
+2. Integration Testing: Test examples in context
+3. Security Testing: Verify security properties
+4. Performance Testing: Check for performance impact


IMO remove this

Just the performance part of Testing process section?

Yes the performance section does not apply to this project

mackowski · 2025-09-08T09:30:47Z

GUIDELINE.md

+
+---
+
+## Maintenance & Updates


This does not match what we or contributors do

Just wanted to confirm, you want me to remove entire section and directly go to section 7.

@mackowski bump on the comments and new commit review

Yes, the whole section should be removed

GUIDELINE.md

jmanico · 2025-09-11T12:11:28Z

I agree with all of Mac’s change suggestions.

packtman · 2025-09-13T05:02:05Z

Just noticed the linters fix led to a bit messed up previous section 7, now section 6. I need to fix section 6 and check if I get new linter related issues.

jmanico · 2025-09-18T23:34:49Z

@mackowski has the lead here, let's patiently wait for his review :)

mackowski · 2025-09-22T07:33:00Z

GUIDELINE.md

+- Functionality: Code examples work as intended
+- Security: Examples implement security best practices
+- Compatibility: Examples work across different environments
+- Performance: Examples don't introduce performance issues


IMO only Performance

mackowski · 2025-09-22T07:34:53Z

GUIDELINE.md

+
+```
+
+### 6.2 Advanced Template Features


was this all tested? Is it working in markdown and on the website?

mackowski · 2025-09-22T07:35:47Z

GUIDELINE.md

+
+## Additional Resources
+
+### Further Reading


This further reading is not helpful in this context right?

mackowski · 2025-09-22T07:36:16Z

GUIDELINE.md

+- [GitHub Markdown](https://docs.github.com/en/github/writing-on-github)
+- [MkDocs Documentation](https://www.mkdocs.org/)
+
+### Community


What is the benefit of having this here?

let me remove the whole additional resources section.

Unless, we want to embed a section dedicated for adding owasp channels or route users to contributors and chat with them.

mackowski · 2025-09-22T07:41:13Z

I left some comments + Markdown linter is failing + I would like to see an example of at least one cheatsheet created (by human or LLM + human) based on this guide to see what is essential in this guide and what is not needed.
I feel that this guide is lengthly

packtman · 2025-10-02T00:50:23Z

I left some comments + Markdown linter is failing + I would like to see an example of at least one cheatsheet created (by human or LLM + human) based on this guide to see what is essential in this guide and what is not needed. I feel that this guide is lengthly

You may look at what MCP Cheatsheet team is doing here https://docs.google.com/document/d/16LvkpUOC5arYl1uIjBglIg9UhoOKm1Lsb6OJYUJhfPU/edit?tab=t.1hsjuwcid34z#heading=h.i6wuwte0l3gd

Do you want to recommend any other new cheatsheet who can leverage what we have suggested in this PR?

mackowski · 2025-10-03T12:07:16Z

GUIDELINE.md

+
+Recommended Content Length:
+
+- Comprehensive Coverage: 3,000-5,000 lines of content


We do not want so long cheatsheets

agreed, let me remove it.

mackowski · 2025-10-03T12:07:39Z

GUIDELINE.md

+Recommended Content Length:
+
+- Comprehensive Coverage: 3,000-5,000 lines of content
+- Practical Examples: 20-30 code samples per cheat sheet


From where you get this number?

mackowski · 2025-10-03T12:08:03Z

GUIDELINE.md

+
+- Comprehensive Coverage: 3,000-5,000 lines of content
+- Practical Examples: 20-30 code samples per cheat sheet
+- Multiple Perspectives: 3-5 different approaches/methodologies


Can you give an example of 3-5 cheatsheets that are doing that

mackowski · 2025-10-03T12:08:24Z

GUIDELINE.md

+- Comprehensive Coverage: 3,000-5,000 lines of content
+- Practical Examples: 20-30 code samples per cheat sheet
+- Multiple Perspectives: 3-5 different approaches/methodologies
+- Cross-References: 10-15 links to related topics


I think this is too much

szh · 2025-10-03T13:33:17Z

I think the general gist of this cheat sheet is just too much. Cheat sheets aren't comprehensive guides, and we certainly don't want an extremely long document explaining how to write them.

packtman · 2025-10-03T14:42:18Z

I think the general gist of this cheat sheet is just too much. Cheat sheets aren't comprehensive guides, and we certainly don't want an extremely long document explaining how to write them.

I agree, how about we just keep Section 6 template? Let's keep it simple to start with.

Just keep this section

6.1 Basic Cheat Sheet Template

I think this is the core and the most useful part. I can delete rest. Thoughts @mackowski @szh @jmanico?

szh · 2025-10-03T14:52:18Z

I love that idea

…- Remove excessive content and keep it simple

szh · 2025-10-03T16:44:28Z

CONTRIBUTING.md


 ### Structure

+> **Need help with content structure?** Check out our comprehensive [How To Make A Cheatsheet guide](GUIDELINE.md) for detailed structure guidelines, content organization, and best practices.


Maybe this should say something like "Check out our template" or just "Check out our guidelines" now that it's not comprehensive.

Still needs to be addressed

szh · 2025-10-03T16:44:48Z

GUIDELINE.md

@@ -0,0 +1,260 @@
+# Cheat Sheet Creation Guide
+
+## How to Create Comprehensive Security Cheat Sheets


I'd remove "Comprehensive". That's not what we want in a cheat sheet.

szh · 2025-10-03T16:45:04Z

GUIDELINE.md

+## Executive Summary
+
+This guide provides a comprehensive framework for creating high-quality security cheat sheets based on analysis of 100+ OWASP cheat sheets. It covers structure, content, formatting, and best practices for creating authoritative security guidance documents.
+
+**Target Audience**: Security professionals, developers, technical writers, and anyone creating security documentation.
+
+**Based On**: Analysis of 100+ OWASP cheat sheets ranging from 44KB to 212KB in size.


For brevity I'd honestly remove this whole section

szh · 2025-10-03T16:45:58Z

GUIDELINE.md

+
+## Conclusion
+
+Creating comprehensive security cheat sheets requires careful planning, thorough research, and ongoing maintenance. By following this guide, you can create authoritative, practical, and valuable security guidance that helps practitioners implement effective security controls.


This sounds too mellow and AI generated. I don't think it's necessarily bad, just very non-human.

Ack, let me make changes to this language.

Still needs to be addressed

szh · 2025-10-03T16:46:37Z

GUIDELINE.md

+---
+
+
+*This guide is based on analysis of 100+ OWASP cheat sheets and represents best practices for creating comprehensive security documentation.*


Can you share more details on how this analysis was performed and how it was used to generate these recommendations?

Sure, I downloaded all the cheatsheets and ran an analysis on it using Cursor. Looked for common patterns and gaps and provided template based on this analysis. Comment for reference #1745 (comment)

I would love more details on what the analysis was. Like what prompts were used, etc. if you still have.

Hi @szh, I had created this document when I worked on analysis of Threat Modeling Analysis for 100+ threat models https://docs.google.com/document/d/1RkpBgLICnTbpPQLeIxc7njzQC3ULhAHH/edit

Unfortunately, I didn't document something similar for this guideline analysis. Let me know if this gives you a good idea of how the analysis was performed.

szh · 2025-10-03T16:46:50Z

GUIDELINE.md

+
+### Remember
+
+The goal is to create **practical, actionable security guidance** that helps practitioners build more secure applications and systems. Focus on providing value to your target audience and maintaining high quality standards.


I think we should mention "concise" somewhere

szh · 2025-10-03T16:47:25Z

README.md

 ## Contributions, Feature Requests, and Feedback

-We are actively inviting new contributors! To start, please read the [contribution guide](CONTRIBUTING.md).
+We are actively inviting new contributors! To start, please read the [contribution guide](CONTRIBUTING.md) and our comprehensive [How To Make A Cheatsheet guide](GUIDELINE.md).


Suggested change

We are actively inviting new contributors! To start, please read the [contribution guide](CONTRIBUTING.md) and our comprehensive [How To Make A Cheatsheet guide](GUIDELINE.md).

We are actively inviting new contributors! To start, please read the [contribution guide](CONTRIBUTING.md) and our [How To Make A Cheatsheet guide](GUIDELINE.md).

packtman · 2025-10-03T16:47:42Z

Alright, this is much cleaner and simpler to consume. Please let me know if I need to make any other changes.

szh · 2025-10-03T16:48:30Z

@packtman Getting closer! I left a few more comments

packtman · 2025-10-03T17:01:54Z

@packtman Getting closer! I left a few more comments

Done, let me know if this looks good now.

jmanico · 2025-10-08T01:53:47Z

Thank you @szh and @mackowski for taking "lead review" roles on this. I support whatever decisions you both agree to.

Any thank you to everyone else for working on this!

packtman · 2025-10-17T02:56:20Z

Hey everyone, please let me know if the changes look good.

szh

LGTM

szh · 2025-10-17T13:29:24Z

Oops, I missed that the linter is failing:

GUIDELINE.md:3 MD001/heading-increment Heading levels should only increment by one level at a time [Expected: h2; Actual: h3]
GUIDELINE.md:245 MD012/no-multiple-blanks Multiple consecutive blank lines [Expected: 1; Actual: 2]

szh

LGTM. @mackowski will need your approval as well

andrzejsydor

not needed such a change

Add comprehensive cheat sheet creation guide (GUIDELINE.md) and updat…

58a0b40

…e documentation references

jmanico previously approved these changes Aug 26, 2025

View reviewed changes

Fix linting issues

0f61d4b

packtman dismissed jmanico’s stale review via 0f61d4b September 1, 2025 15:17

jmanico previously approved these changes Sep 1, 2025

View reviewed changes

Fix linting issues

23d9b59

packtman dismissed jmanico’s stale review via 23d9b59 September 1, 2025 15:50

andrzejsydor approved these changes Sep 1, 2025

View reviewed changes

mackowski requested changes Sep 8, 2025

View reviewed changes

packtman force-pushed the master branch from 64172bd to 23d9b59 Compare September 13, 2025 04:28

Remove maintenance and peer review sections, streamline guide structure

641c4b1

Dipen Shah and others added 2 commits September 13, 2025 01:07

Fix code block formatting in template examples

cf6e0a7

Remove title and other parts from section 4.1

9dc6e42

mackowski requested changes Sep 22, 2025

View reviewed changes

mackowski reviewed Oct 3, 2025

View reviewed changes

Dipen Shah added 2 commits October 3, 2025 12:40

Simplify GUIDELINE.md based on PR feedback - Focus on basic template …

ff4b022

…- Remove excessive content and keep it simple

Remove section numbering from Advanced Template Features

eb4ca28

szh requested changes Oct 3, 2025

View reviewed changes

CHanges per new feedback

b82318a

Dipen Shah added 2 commits October 10, 2025 09:22

Simplify conclusion section in GUIDELINE.md

49da8f7

simplify text in GUIDELINE.md and CONTRIBUTING.md

e8c44bf

szh previously approved these changes Oct 17, 2025

View reviewed changes

andrzejsydor approved these changes Oct 21, 2025

View reviewed changes

Fix markdown linting issues in GUIDELINE.md

ca4c5f8

packtman dismissed szh’s stale review via ca4c5f8 October 24, 2025 00:46

szh approved these changes Oct 24, 2025

View reviewed changes

andrzejsydor reviewed Oct 25, 2025

View reviewed changes


		Recommended Content Length:

		- Comprehensive Coverage: 3,000-5,000 lines of content


		### Structure

		> Need help with content structure? Check out our comprehensive [How To Make A Cheatsheet guide](GUIDELINE.md) for detailed structure guidelines, content organization, and best practices.

		@@ -0,0 +1,260 @@
		# Cheat Sheet Creation Guide

		## How to Create Comprehensive Security Cheat Sheets


		## Conclusion

		Creating comprehensive security cheat sheets requires careful planning, thorough research, and ongoing maintenance. By following this guide, you can create authoritative, practical, and valuable security guidance that helps practitioners implement effective security controls.

		---


		This guide is based on analysis of 100+ OWASP cheat sheets and represents best practices for creating comprehensive security documentation.


		### Remember

		The goal is to create practical, actionable security guidance that helps practitioners build more secure applications and systems. Focus on providing value to your target audience and maintaining high quality standards.

	We are actively inviting new contributors! To start, please read the [contribution guide](CONTRIBUTING.md) and our comprehensive [How To Make A Cheatsheet guide](GUIDELINE.md).
	We are actively inviting new contributors! To start, please read the [contribution guide](CONTRIBUTING.md) and our [How To Make A Cheatsheet guide](GUIDELINE.md).

Add comprehensive cheat sheet creation guide (GUIDELINE.md) #1768

Are you sure you want to change the base?

Add comprehensive cheat sheet creation guide (GUIDELINE.md) #1768

Conversation

packtman commented Aug 26, 2025

Summary

Changes Made

Benefits

Uh oh!

jmanico left a comment

Choose a reason for hiding this comment

Uh oh!

jmanico commented Aug 26, 2025

Uh oh!

packtman commented Aug 29, 2025

Uh oh!

jmanico commented Sep 1, 2025

Uh oh!

jmanico commented Sep 5, 2025

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

packtman Sep 13, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

jmanico commented Sep 11, 2025 via email

Uh oh!

packtman commented Sep 13, 2025

Uh oh!

jmanico commented Sep 18, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

mackowski commented Sep 22, 2025

Uh oh!

packtman commented Oct 2, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

szh commented Oct 3, 2025

Uh oh!

packtman commented Oct 3, 2025

6.1 Basic Cheat Sheet Template

packtman Sep 13, 2025 •

edited

Loading