hialeahliam/progressions-old-

progressions-old-'s Issues

Chords assigned inversion during progression edit or creation

Style login and sign up forms

Rename a collection or progression by double clicking on title

User can publish downloaded progression only if they have edited it

• Edit must not be identical to original.
• New progression should have user and previous authors as authors.

User can search published progressions and add them to their own collections

• User does not need to be signed in to view published progressions.

User can publish progressions or collections to public repository

• User can published a collection made entirely of downloaded progressions.

Audio playback takes into account chord inversion

Style modifier buttons

add9, add11, add13 modifiers

Progressions are played back in their key or in random key if they don't have a key assigned.

Email and password signup and login

7th and major 7th modifiers

9th and major 9th modifiers

Allow user to recover password

Logged in user can publish their own progression or collection

• If a collection is published, its progressions can also appear as database search results.

Redesign after MVP

Make an openapi 3.0 yaml based on the current api. Analyze which routes are used and which aren't.

Add additional endpoints and expand on current ones.

Document design decisions as comments in this issue.

Chord is played back when input or modifier is sent while editing a progression,

Public progression database search results can be either collections or progressions

Stop using firebase for authentication

Use Google, Apple and Twitter as OAuth2 identity providers instead.

User can add descriptions to progressions

User can see the download counts of their published progressions

• If a collection is downloaded, its progressions are downloaded. Therefore, the download count of the collection and every single one of its progressions increment by one.

User can create or edit a progression Collections page

• When a progression is created, it is saved to whichever collection was selected when progression creation was initiated

• Clicking on another collection or progression from the menus should automatically
  save the progression before another is viewed

Chords can be assigned playback lengths in beats

Combine frontend and backend into single NextJS app

Login and sign up info verification

Provide user an alert when signing up if:

- Passwords don't match

- Passwords are incorrect format

- Email is incorrect format

- Account already exists

When logging in if:

- Password is incorrect

- User not found 

Current progression Title, Collection, Key, and Mode should be displayed in Training page

Reassigning mode while editing progression will transpose semitones of III/iii, VI/vi, VI/vii chords by one.

Deploy backend on something other than EC2 instance.

EC2 instance was way too expensive. investigate if a Margate container or deploying the whole thing on a Lambda would be cheaper.

Clicking a chord slot when viewing progressions in the Collections page should play back chord

User selects which collections they want to train with on the Training Page

• User not logged in can only train with a Default collection

Progressions can be assigned tempos in BMP

Progressions can optionally have keys assigned

Dominant chord modifier for scale degrees other than 7

• Modifier button to replace chord with its dominant chord. E.g. replace V with II, v with II, #vi+7 with #III, or viiø7 with #iv
  • chords starting with scale degree 7 are the only chords with diatonic roots having dominants with non-diatonic roots