Commit 537d823e authored by Robert Martinez's avatar Robert Martinez

make header and content more distinct

parent 0dbcf8d7
Pipeline #62871815 canceled with stages
in 47 seconds
# Specs - User Stories
# Specs - User Stories
> *for https://snowdrift.coop*
## Understanding this document
> ***Understanding this document***
Collaboratively creating software presents many challenges, not the least of
> Collaboratively creating software presents many challenges, not the least of
which is agreeing on what software is actually being created. This page is a
record of what agreements have been made. It is a **living document**. The rest
of this section will describe its format and contents: namely, user stories.
We try to focus our discussion on individual features by motivating them with
user stories. By using the format, *As a ____, I want ___ so that ____*, we can
> We try to focus our discussion on individual features by motivating them with
user stories. By using the format **" As a ____ , I want ____ so that ____ "**, we can
have a concrete discussion about *who* is using the feature, *what* it provides,
and *why* it is useful. Deciding on a user story is only the first step, of
course, and can certainly be contentious in its own right. We can always return
to it, however, to reign in lengthy and far-ranging tangents while collaborating
on future plans.
The user stories for the website are grouped under the page on which the relevant
> The user stories for the website are grouped under the page on which the relevant
feature exists. This is just for ease of lookup. User stories define which pages
exist—not the other way around.
## User Stories for https://snowdrift.coop
### / (Welcome page)
- **As a** visitor, **I want** to read an introduction to the website **so that** I can
familiarize myself with the platform and its goals.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment