navigating to the browse events page while you are on the browse events page clears all of the events.

remove address column from events table.

create a general browse events page to filter through events by type not by location., yet

Make sure you can't like events if you are logged out.
Make sure the likes instantly are removed from the likes page.

The venue text box become enabled when loading an event with ONLINE location.

investigate the font barlow for headers

• Should have 7 MVPs.
  • 3 of those are User Auth, Heroku, and Production README.
  • The other 4 are from the MVP List or they have clarified them with you
• Contains a description sentence of the app
• Includes two to three detailed bullets on functionality and presentation of feature
• At least one CRUD feature, which states what CRUD operations are planned (creation, reading, updating, deletion)
• Estimates how long it will take the code each MVP
• Correctly formatted
  • MVPs are listed in an ordered list
  • Each MVP is broken down into bullet points

fix the sign out

The header nav bar container is accessing props and causing an error.

the picture preview on the details page is too large.

User Auth

Functionality

• The main button with logo should link to /
• Has working demo login
• Smooth, bug free navigation

Before Login

• The /login page should not display a link to Log In. Same for /signup
• Going to a random route /#/oweiniouewbrviuwebv should redirect or display a 404 page
• Errors should display for both /signup and /login.
• Errors should clear when moving between /signup and /login.
• Can sign up a user
• Can sign in as a user
• Can log out a user
• Can't sign up with the same username/email
• Pressing enter after filling out the session form should use the form data, not the demo user

After Login

• Should not be able to visit /login or /signup
• Should be able to refresh the page and still be logged in

Style

• The site should look exactly like the actual site
• All relevant elements should have cursor: pointer on hover
• When errors are displayed, most elements should not move around the page (particularly input boxes)
• Remove Redux logger and all console.log()'s from production

Seeds

• Adequate and appropriate seeds

on update prepopulate details from with correct details.

you've confused the about and description columns. they are actually the same. combine them.

when there are no likes change the message "please select another filter"

add box shadow to events and change cursor to pointer upon hover.

adjust the css of the likes button to fit inside of the event card.

remove follows link from drop down.

On the ticket modal.

MAke sure that the users can't register more tickets than the remaining amount of tickets.

events need an update option

event deletion

event show page.

• State shape is flat!
• State's keys are camelCased
• All keys within the values in the state are accessible in the schema
• Correctly formatted
  • Sample state is rendered with triple backticks, and the language ```javascript...```). This will display the state as a code block instead of a giant line of text
  • Top level slices
    • entities
    • session
    • errors (here or in ui)
    • ui (if needed)
  • Should NOT have nested slices, aka comments inside of posts
    • Some info from other tables is ok, for instance:
      • the author username and imageurl for a post. basically any info that the user can't change
      • like count and a boolean on whether the user likes the post instead of a likes slice

refreshing this page causes an error

add new featured collections

The create event page is not clearing the data from the previous update.

also the submit is not working.

adjust the start time minimum time on edit

add organizer to each events.

delete events with a confirmation.

Add a price filter for free and paid events. based on tickets.

maybe add another column to the jbuilder the association to tickets.

add a pick a date option or delete it from the browse page.

• Is the first page you see upon entering the wiki
• Contains a welcome message
• Contains a link/placeholder for a link to the live page
• All links in the right sidebar should contain each wiki page and link to the correct page
• Correctly formatted
  • each wiki page is listed in bullet points
  • all links route the correct page

remove the users event from the users event slice of state upon deletion.

create an about me page.

adjust the css for the error messages on the sign up page.

Create an error message for the email login page to validate for emails. with error message.

do validation for email addresses. make sure users can't enter non valid email addresses.

none of the discard buttons work. they should delete the event if it has been created on the create event page / details event page.

• Contains correct datatypes
• Contains appropriate constraints/details
  • primary key
  • not null
  • unique
  • indexed
  • foreign key
• Contains bullet points after the table that state which foreign keys will reference to which table, or references to the associations which will be made
  • foreign key and table name are lowercased, snake_cased and back_ticked
• Correctly formatted
  • schema is written in a table format
  • the table's name are lowercased, snake_cased and back_ticked
  • the table header column names are bolded
  • columns names are lowercased and snaked_cased and back_ticked

Make sure that the start date can't be after the end date on the sign up form.

The events are not being correctly labeled as in the past.

add a shopping mart menu to ticket modal based on registrations.

Add incomplete event profiles to the demo user account.

create a cron job that reseeds the database every week and a half or so.

update the kebab menu to not go off of the side of the page

• Frontend routes contains wildcard variables written in camelCase
• Correctly formatted
  • Routes are displayed with inline coding text (backticks)

• Contains the following sections: HTML, API Endpoints(Backend)
• Each route has a description
• API Endpoint routes contains wildcard variables written in snake_case
• Routes does not contain superfluous routes
• Have API routes that will allow the front end to get all info it needs and does not have unneeded routes:
  • probably doesn't need a GET likes api endpoint because that info comes through the post show

upon logging in the header nav bar is to change to include icons.