Completed Edit me
A Product Manager should be able to document requirements as Epics, Stories, Use Cases or any other format he/she wishes, using plain HTML or Markdown

User Story

As a PRACTICAL ™ Product Manager, I don’t want to be limited to any specific format of requirements definition. I want to be able to document my requirements as Epics, User Stories, Use Cases, simple bullet point lists, or anything else I can think of. I want to be able to document using plain HTML formatting. However, if I have to write that HTML by hand (no graphical editor available) then I want the option of using Markdown to make the text more human readable, and to enable direct editing in the online GitLab editor.

Implementation

At ZCS, we’re using our own forked and heavily modified version of Tom Johnson’s Jekyll Documentation Theme. Our version has been modified pretty heavily to support our own requirements. However, both the basics of how to use this theme, and how to get the most of our modifications to it are documented right here on this site! Of course, you’re currently looking at the documentation of how we use the theme and how we’ve modified it. If you not familiar with the basics, our own modified version of the how-to guide is hosted here as well.