User Stories - RAISE Manifesto Website

Last updated:

These user stories define the key features and functionality requirements for the RAISE Manifesto website, capturing stakeholder needs and guiding development decisions.

User Stories

The following user stories guide the development of the RAISE Manifesto website:

Story 001: Publish and Discuss the RAISE Manifesto

As a person interested in story-first engineering and new approaches to building software, I want to easily read the RAISE Manifesto on a simple, accessible, and versioned website, So that I can understand its core principles and reflect on its ideas.

Acceptance Criteria

  • The RAISE Manifesto is published in a clear, readable format on a standalone website.
  • The site is simple, fast, and works on any device.
  • No login or account is required to read the manifesto.
  • The site displays a date-based version for the manifesto (using the last updated date), reflecting its status as a living artifact.
  • The site reflects the RAISE values of simplicity, transparency, humility, and bravery.
  • The website meets high accessibility standards (WCAG 2.1 Level AA or higher), ensuring a world-class experience for screen reader users.

Story 002: Display Author Information

As a reader of the RAISE Manifesto, I want to understand who is behind the manifesto, So that I can know the context of its creation and the perspective of the author(s).

Acceptance Criteria

  • The site includes a clearly identifiable section for "Who We Are" (author bio).
  • This section provides a short bio as specified in the design document (e.g., brief, text-only, 2-4 sentences).
  • The presentation of this section is de-emphasized compared to the main manifesto content, adhering to the site's design principles for modesty and simplicity.
  • The section is located on the main page, after the manifesto text and before the Example Projects section, accessible via scrolling.

Implementation Notes

  • This feature enhances transparency and builds trust with readers.
  • Adheres to our "Human-first, always" principle by showing the human creators behind the methodology
  • Maintains the site's minimalist aesthetic while providing important context

Story 003: Add a Blog Section to the Site

As a visitor to the site, I want to be able to access a "Blog" section so that I can read news, updates, and articles related to the project, all in one place without needing to search through external sites or social media.

Acceptance Criteria

  • There is a clear and accessible "Blog" link in the main navigation on the homepage.
  • The Blog section displays a list of posts, each with a title, date, and short summary.
  • Clicking on a blog post shows the full content of that post on its own page.
  • Blog posts are easy to read and formatted consistently.
  • The blog is publicly accessible and does not require any login.
  • The blog and its posts are created and updated by simply adding or editing HTML files in the GitHub repository (no CMS or static site generator used).
  • The blog section works seamlessly within the existing design and layout of the website.

Value Statement

Adding a blog section enhances the site's ability to share updates, insights, and knowledge with its audience, fostering greater engagement and keeping visitors informed about project developments.

These user stories define the core requirements and functionality for the RAISE Manifesto website, guiding development decisions and priorities.