The introduction to markdown should be interesting to read :) or just jump to Scenario 1
Priority | User Story |
---|---|
P1 | As a page author, I can easily author beautiful content leveraging simple styles are already know from my work with other github projects. |
This should be really good
- Fast
- Good
- Cheap
Pick two
Priority | Requirement | Description |
---|---|---|
P1 | Markdown must be consistent with known styles | Because that would be stupid to invent something new, just to be different |
Go back up to Customer Scenarios
Priority | Requirement | Description |
---|---|---|
P1 | Markdown must be consistent with known styles | Because that would be stupid to invent something new, just to be different |
Go back up to Customer Scenarios