Prepare User Stories First Draft

[emecas]

Overview

User stories (from the point of view of the website user):

• Accessible in English and Spanish
• Easy to find videos
• Easy to find survey and to fill them out
• Feel and personality of the website should be “fun” and “empowering” (example: United Sodas of America brand)
• Easy to leave feedback and comments

Action Items

• [ ] Write the user stories using as <user> I want ... format .
• I want a website that clearly communicates United by Chocolate, a non-profit that is here to empower farmer communities through translated information for the cacao and chocolate industry.
• I want a website that can easily be translated between languages. The most important in order of priority are Spanish, English, French, and Indonesian
• I want a website where UBC's videos can be easily accessed and watched.
• I want a website where users can easily leave their contact information (email and/ or WhatsApp)
• I want a website where users can easily leave leave their feedback and suggestions
• I want a website that will allow us to better understand our users. I want to better understand what languages are most needed, which topics are the most searched for, what videos are the most useful to out users, and which ones are the most shared with others.
• I want a website where users can easily search or filter videos by topics and language availability
• I want a website where industry partners (NGO's, industry association groups, cacao co-ops, government, etc. ), that create content, can learn about how UBC can help provide language interpretation for their conferences and online events.
• I want a website that will support fundraising efforts (Patreon, selling logo merchandise, donations, event ticket sales, etc.)
• I want a website that allows interested parties to connect with UBC via email

Resources/Instructions

See #37 (How To Write Good Uses Stories Resources)

[nhrafiq]

• Incorporating two other platforms (translator and analytics)
• Hosting videos (what service to use?)
• Payment / monetization feature
• Maintainability (no-code platform or hybrid solution)
• Flexibility (from scratch - Ruby on Rails)
• API - Django

[emecas]

Closing this issue since I have created 10 discussions in order to refine the results for this User Stories First Draft

See Discussions :

1 -> #20 2 -> #21
3 -> #23 4 -> #25 5 -> #27 6 -> #28 7 -> #30 8 -> #32 9 -> #34 10 -> #36