-
Notifications
You must be signed in to change notification settings - Fork 0
User Stories
Replace default README File User Story As a Project Manager, I want to see a completed Readme file so that I can understand more about your project. Acceptance Criteria
- Readme located at the root of your project has been updated with info from the wiki.
See https://github.com/adamLovettApps/JamOut/blob/main/README.md for an example.
Replace default favicon File User Story As a Project Manager, I want to see an updated favicon so that I can easily identify your application in a list of tabs. Acceptance Criteria
- Favicon has been updated from the default icon provided by the project starter. See https://www.favicon-generator.org/ for a simple favicon generator
Deploy for the first time User Story As a Developer, I want to deploy my starter app to Heroku so that I can make sure I can deploy changes consistently. Acceptance Criteria
- The cloned starter app has been deployed to Heroku.
Create About Links on the Home Page User Story As a Developer, I want to display links to my GitHub and LinkedIn profiles so that prospective hiring managers can learn more about me after looking at my project. Acceptance Criteria
- Links to your LinkedIn and GitHub profiles should appear on the homepage of your application
Sign Up Functionality User Story As a User, I want to create an account so I can use the website. Acceptance Criteria
- A link/button appears in the navigation for Sign Up (only when not already logged in)
- When clicking the link/button the user is redirected to a sign up form.
- After filling out the form and clicking a Submit button an account is created.
- A message is displayed to the user indicating that the account has been created. (optional)
- The user is redirected to an appropriate page (determined by the developer)
- The user has some indication that the user is now logged in.
Login Functionality User Story As a User, I want to login with my previously created account so I can use the website. Acceptance Criteria
- A link/button appears in the navigation for Log In (only when not already logged in)
- When clicking the link/button the user is redirected to a login form.
- After filling out the form with username and password and clicking a Login button the user is logged in.
- A message is displayed to the user indicating that the user has successfully logged in (optional)
- The user is redirected to an appropriate page (determined by the developer)
- The user can visually identify they’ve been logged in by having their username displayed in the navigation bar.
Error handling Complete User Story As a Developer, I want to validate the LogIn/Signup forms being submitted so my users have a good experience when using my application. Acceptance Criteria
- (Log In) If the username/password combination is wrong, or the user does not exist the login fails.
- (Log In) A message is displayed to the end user indicating which fields are invalid.
- (Sign Up) If the username/email already exists, the signup form fails
- (Sign Up) A message is displayed to the end user indicating which fields are invalid.
Logout Functionality Complete User Story As a Logged In User, I can log out of my account so I can ensure it isn’t used without my permission. Acceptance Criteria
- A link/button appears in the navigation for Log Out (only when logged in)
- When clicking this button/link the session ends and the user is logged out.
- When refreshing the page or traveling to other pages the user does not appear to be logged in
- The logged out user can log in with a separate account without issue.
Demo Login Functionality Complete
User Story
As a Project Manager, I can use a Demo Account so that I can use the application without having to use the signup form.
Acceptance Criteria
- A link/button appears in the navigation form and/or Login Form titled “Demo Login” (only when logged out)
- When clicking this button/link the user is automatically logged in as a Demo User (a previously created account for testing) without the need to fill out the signup/login form.
- The user is redirected as if they successfully completed the Log In form.
Auth Styling Complete User Story As a User, I would like to see at least basic styling on the signup and login forms so that the application doesn’t appear too similarly to the default application provided. NOTE: Specific style choices are up to you. But use common sense given your time, ability and wireframes. Acceptance Criteria
- Sign up and Login forms have been styled appropriately.
Splash Page Complete
User Story
As a logged out user, I can view the splash page of the application so that I can log in or sign up.
Acceptance Criteria
- A page appears when you navigate to the link.
- Buttons exist in the navbar and on the page to allow log in or sign up.
- Page is styled appropriately.
Home Page Complete
User Story
As a logged in user, I can view the home page of the application so that I can create new offers and requests, view nearby offers and requests, and see navigation to the rest of the application.
Acceptance Criteria
- A page appears when you log in.
- Buttons exist in the navbar to take me to other pages in the site.
- I can see offers and requests close to my location.
- Page is styled appropriately.
NavBar Complete User Story As a logged in user, I can view the navbar of the application so that I can navigate to all pages in the site. Acceptance Criteria
- Navbar appears at the top of the page when logged in.
- A logo exists on the navbar that I can click to navigate to home at any time.
- A search bar exists on the navbar so that I can search anywhere on the site.
- A button exists that creates a dropdown when clicked with links to profile, logout, request, and offer pages.
- Navbar is styled appropriately.
NavBar Complete User Story As a logged in user, I can view the navbar of the application so that I can navigate to all pages in the site. Acceptance Criteria
- Navbar appears at the top of the page when logged in.
- A logo exists on the navbar that I can click to navigate to home at any time.
- A search bar exists on the navbar so that I can search anywhere on the site.
- A button exists that creates a dropdown when clicked with links to profile, logout, request, and offer pages.
- A button exists that opens a form to create an offer or request when clicked.
- Navbar is styled appropriately.
User Offers Complete User Story As a logged in user, I can visit the user offers page so that I can view all of my offers. Acceptance Criteria
- Offers are listed newest first.
- I can edit and delete offers.
- I can click a button to view all offers.
- I can click a button to order offers by location. (BONUS)
- Page is styled appropriately.
User Requests Complete User Story As a logged in user, I can visit the user requests page so that I can view all of my requests. Acceptance Criteria
- Requests are listed newest first.
- I can edit and delete requests.
- I can click a button to view all requests.
- I can click a button to order requests by location. (BONUS)
- Page is styled appropriately.
User Profile Complete User Story As a logged in user, I can visit my profile page so that I can edit my information and view my ratings.. Acceptance Criteria
- I can edit my information.
- I can view my information.
- I can view my ratings.
- I can delete my account
- Other users cannot see my personal information.
- Other users can post ratings on my profile.