lateworm / manganese Goto Github PK

• Replace boilerplate left over from stock GitHub Readme with meaningful content.
• Extract Rails-related notes in the Readme to some other form of Ruby study document.

• Many of our 'destory' links return DB errors because of orphaned records. Most of these should probably just cascade the delete.
• If we're making destroy buttons more powerful, we should probably add some form of safety mechanic around them.
• We currently have 'Destroy' links on Index pages only. It'd be convenient to have them on 'edit' and 'show' pages as well.

Currently there is just one general-use admin/danger colour. This results in benign 'add' admin links being shown in a 'danger' colour. These should be differentiated.

Add fields for Spotify (etc..) links to the The 'New Album' and 'New Recommendation' forms.

List of DB records (albums, events, etc...) have a few problems:

1. The alternating background colours only work well when there is an odd number or items
2. On wide desktop sizes, information loses legibility due to being too spread out

The obvious solution is to move back to a card-based record list.

Add Albums fields to the 'New Event' form. Currently, Admin has no way of assigning an Album to an Event.

Currently the navigation bar is not visible when the user scrolls down the page, forcing them to scroll back up to access it.

A possible solutions is to pin the navbar to top of page, perhaps with hiding when scrolling down.