Rebrand stories (#154)

* docs: update on stories

* docs: correct stories intro

docs/security-champion/3-faq.md

@@ -20,9 +20,9 @@ No, but we highly recommend everyone on sharing. It might also be that you hear
 
 Are you sure? Everyone knows something, and how you apply certain tools or how you've implemented security testing could be very interesting! The [Impostor syndrome](https://en.wikipedia.org/wiki/Impostor_syndrome) is real, and we need to combat it.
 
-## I have a success story I want to share
+## I have a story I want to share
 
-Awesome! We want to hear about what you did. Reach out to the AppSec team on Slack. Maybe we will award this with unique merch as well?
+Awesome! We want to hear about what you did. Reach out to the AppSec team on Slack after reading the [stories](./stories/index.md) page. Maybe we will award this with unique merch as well?
 
 Even if it was something "bad" you discovered in your project, why not share? It's important to highlight the issues we have as well as the good, as everything can be used to learn from.
 

docs/security-champion/4-learning-platform.md

@@ -57,7 +57,7 @@ Please help contribute with useful activities that make sense in Equinor context
 - Gain three ```white``` belts
 - Gain two ```yellow``` belts
 - Gain two ```green``` belts
-- Create a success story about something your team did. Check out [success stories](./success-stories/index.md) for template
+- Create a story about something your team did. Check out [stories](./stories/index.md) for template
 
 !!! note
     The list of activities might change based on your feedback.

docs/security-champion/stories/index.md

@@ -0,0 +1,33 @@
+# Stories 🏆
+
+We want to highlight stories from our teams, to promote both learning and sharing culture, in the context of security. What _is_ a story? Below are a few examples:
+- Something that went wrong in a project, how it was fixed and lessons learned
+- New feature added to improve security
+- New routines or ceremonies that has helped the team
+
+ If you have something in mind, consider writing a story. It's even an activity to reach the [brown/black belt](../4-learning-platform.md#activities)!
+
+!!! info
+    Please use the below template and send it to the AppSec team on Slack or e-mail at ``appsec[at]equinor.com``
+
+## How to get started
+
+This is just a guidance, you do you when telling this story. Feel free to include pictures to illustrate, and provide sources where applicable.
+
+- **The team:**<br>
+This is normally you and your team.
+
+- **Initial situation:**<br>
+This is the initial situation of why you are telling the story. Did some security control go wrong? Did a new feature get in the backlog?
+
+- **The mission:**<br>
+What activities was made to improve or remediate the initial situation? What challenges occurred along the way? Usually the part where readers can learn something to take home, or get new ideas.
+
+- **Outcome:**<br>
+What was the outcome? Did it improve the initial situation and give some new learning to the team?
+
+!!! tip "Tips"
+    Try to add technical and quantifiable information to the story to better showcase the value.
+
+!!! Warning "Note"
+    Please keep in mind that the site is accessible publicly to everyone across the internet, therefore avoid sharing information that is sensitive or should not be available to the public.