soehlert/concert-elephant

Never forget the concerts you've seen

Concert Elephant

Never forget your concerts

License: MIT

Settings

Moved to settings.

Basic Commands

Setting Up Your Users

• To create a normal user account, just go to Sign Up and fill out the form. Once you submit it, you'll see a "Verify Your E-mail Address" page. Go to your console to see a simulated email verification message. Copy the link into your browser. Now the user's email should be verified and ready to go.

• To create a superuser account, use this command:

  $ python manage.py createsuperuser
  

For convenience, you can keep your normal user logged in on Chrome and your superuser logged in on Firefox (or similar), so that you can see how the site behaves for both kinds of users.

Type checks

Running type checks with mypy:

$ mypy concert_elephant

Test coverage

To run the tests, check your test coverage, and generate an HTML coverage report:

$ coverage run -m pytest
$ coverage html
$ open htmlcov/index.html

Running tests with pytest

$ pytest

Live reloading and Sass CSS compilation

Moved to Live reloading and SASS compilation.

Deployment

The following details how to deploy this application.

Heroku

See detailed cookiecutter-django Heroku documentation.

Docker

See detailed cookiecutter-django Docker documentation.

concert-elephant's Issues

Artists not counted when openers

If a band is an opener at 5 concerts they will show up as having 0 concerts

Profile?

Should I set up a profile model or something so people can update their username? What does this get me, currently it's never displayed and only shows up in the admin site.

Add a search bar just for my profile

If i want to search through the concerts listed on my profile i shouldnt use the main search i should have a different set up to search only that page

Created_at

Add a created_at model field for the different models. Probably just use and auto_add_now or whatever. Would be useful to get the "most recent" artists and venues at the very least.

Test Javascript

Look into unit testing the javascript code

concert detail view

if im logged in and ive left a review go ahead and show me that

Review

Maybe add a review model for people to save a review for concerts? I guess this is maybe similar to notes

Concert review shows up for editing even for other concerts

"When I add a review, having already added a review before, it seems to pre-populate with the text from the previous review. Not a huge deal."

"yeah, I was adding a review for a different concert."

Sort by state broken

it just doesnt seem to sort at all

sort by fields

allow users to sort the list views

clickable fields

make home page rows clickable and change from using "more info" to having a clickable row on the concerts

Caching for github actions

I probably am doing some stupid stuff and rebuilding everything everytime making it run very slowly or something.

Handle characters from other encodings?

I feel like maybe we won't do a good job with characters from other encodings and alphabets very well

Concert Form UX

Improve concert form UX:

autocomplete all fields that makes sense, allow to create artist|venue|opener directly from there without having to remember to do it in advance.

Add global search

Desired:

1. work with venues, artists and concerts
2. case insensitive
3. partial string matching (eg can find Rose Bowl Tavern based on the search of "bowl")

Auto populate some concerts

Grab data from somewhere like

1. Zyla
2. Ticketmaster
3. Setlist

or something similar depending on API restrictions

We could pull based on venues or artists we already know of.

My profile remove button

The UX just seems kinda bad with the button colors and all that. Maybe use some sorta red color instead? Should I add a confirmation too? Does it delete my concert review? Should it?

Remove myself as an attendee

Might as well give option to remove yourself as an attendee. You might accidentally click the wrong show after all.

Card header width vs tables

On narrow screens my card headers are not nearly as wide as the table which looks...awkward

Authn Styling

The style on the allauth pages is...not awesome. How can I override that. The link is ugly and the second page with the "you're signing in with google click to continue" or whatever page is even more ugly

Documentation?

The readme is kinda generic from the cookiecutter...but it's not like I expect people to use this project. Might be nice for my own sake at some point to fix that up a bit but not urgent.

US states

Currently just taking name, city and country. Kind of weird UX should find a way to handle states

Homepage

We could have some cards like:

1. "most popular concerts" based on how many people have said "i was there"
2. most recent concerts added
3. most recent venues added
4. most recent artists added

Search AJAX

It might be a better experience to not need a full page reload on searches? Adding AJAX for autocomplete and avoiding reloads would be good.

Make venue create look more like concert create

Its an AJAX form already i think so lets clean it up and make it behave like concert create especially on errors and whatnot

Extraneous message

When you use the artist create modal, close it, then reopen it, it still shows Artist Added Succesfully

Fix API

API is lagging, add any other models or fields needed. Do a general once over.

authz

definitely need to clean up authz before we go live

AJAX Tests

They are not really DRY so i could probably do more with scenario outlines for them.

Combine pages

Instead of a separate artist list and artist create page can we combine them? (this goes for venues and concerts as well)

Create Venue from Concert Form

It would be really great to be able to add a Venue from the concert form instead of having to remember to create that in advance.

Add cards to the front page for popular artists and venue

Currently have popular concerts (which will be more rare) and then recent stuff. I think popular artists especially would be fun

Deal with the "The" Problem

Don't want to duplicate if we see things like "beatles" and "the beatles"

Users "I was there"

Add an option to let people say "i was there" to a concert that already exists, created by someone else.

Fix CI pytest

Pytest is failing

Reusable pagination

Currently repeating the pagination code in all of our templates which seems like we don't need to?

Label my inputs

I think some of the input elements are missing labels which are vital for screen readers

Dummy data

Set up some dummy test data so I don't have to manually create some every time

Split JS into different files

Currently HTML templates are very busy with all the js

Unified autocomplete

Rewriting the autocomplete code all over is silly. Just find a way to keep using JQuery UI Autocomplete but make it available for any field.

Add new opener only works for the first opener

I think this will cover most cases, but still I want to be able to add more openers if someone went to a show with three openers and none of them are listed in the db yet

Tests

API is well tested but t he web views could use some work

Clean up search results page

Currently if you actually go to the search results page it looks terrible. Either clean that up or have search results show up on the home page and keep people from actually browsing the search page or something

Capitalization

Weird capitalizations like Zz Top and Buddy Guy'S Legends

Notes

Let users add a note to the instance of the concert connected to their profile somehow?

Sorting for other lists

Add sorting functionality for lists, so far we only have concert list.

• artist list
• concert list
• venue list
• my concerts list on profile?

also need to do this in a way that doesn't break pagination

Remove containers

I don't use the sphinx docs in local and I use hosted postgres so no need for that in prod

Allow users to edit their objects

This may be trickier once we allow other users to click "i was there" on soemone else's object. can we alert the other users that there was a change and let them decide to accept or not? seems unlikely to allow since the database would get messed up? can we copy over the old data into a new model object and apply that to other users and then warn them upon their next login something had changed?

Authn

Set up all auth to actually allow accounts

Styling

The website is not..pretty