diff --git a/docs/style-guide-for-curriculum-challenges.md b/docs/style-guide-for-curriculum-challenges.md
index 1496703335..e611499128 100644
--- a/docs/style-guide-for-curriculum-challenges.md
+++ b/docs/style-guide-for-curriculum-challenges.md
@@ -18,6 +18,7 @@ With that practical focus in mind, let’s talk about the requirements for our c
- [Writing instructions](#writing-instructions)
- [Formatting challenge text](#formatting-challenge-text)
- [Formatting seed code](#formatting-seed-code)
+- [Formatting solution](#formatting-solution)
- [Why do we have all these rules?](#why-do-we-have-all-these-rules)
## Proper nouns
@@ -139,6 +140,40 @@ Here are specific formatting guidelines for the challenge seed code:
`// Fix this line`
+## Formatting Solution
+
+The challenge solution must be in proper markdown tags. The code must be wrapped in `section` tags with an id of `solution`.
+
+```
+
+
+three backticks + html or js
+ [ SOLUTION CODE]
+three backticks
+
+
+```
+
+Example:
+
+````
+
+
+```html
+
+
+
+```
+
+
+````
+
## Why do we have all these rules?
Our goal is to develop a fun and clear interactive learning experience.