nataliethistime / songdown-app Goto Github PK

The design on the site is a little ugly and needs to be cleaned up.

When a user tries to transpose a song which has a line of chords with brackets in it (example below) things get ugly.

(Am C) => ?? ??

We could use Firebase to store all the songs. This would allow in-browser editing and saving of songs. However, we'd need to sort out a password arrangement or something.

Similar to Youtube links it should be possible for a song author to specify the key.

Perhaps there could be a way of figuring out the key. Though my music theory ain't great... :P

The situation with printing is pretty terrible right now. My solution is thus:

Implement a new page on the express app that is for returning the raw output of the compiler. Use url params to control things like transpose and font size. This way, printing might work on a browser other than Chrome (which, btw, Chrome itself doesn't do it very well anyway).

The toolbox needs to implement a print button. Note: there may be some issues here to do with limitations of Radium.

Print the Songdown version at the bottom of each page the app.

We need to append a '?cacheBust=' + (Date.now()) to the URL when we get the songs.json file. It sometimes gets cached by the browser and it never should.

Add a "thing" on the Edit Song page which explains the Songdown syntax.

All the CSS for pages is tangled in one file, we need to split things up in a way that makes more sense.

A song could possibly have a picture (maybe the cover of the album it came from?) that's shown in the search results alongside the song's name.

This is a bit far fetched, but it could be a subtle addiction that would add to the look and feel, considering that it all looks a bit boring right now.

Title says it all...

With the recent move back to using just <a>'s for links, the page reloads everytime one is clicked. This be bad. 👎

We need to find a way to make the index page look prettier and be more usable.

Should implement a "link to PDF" so that proper sheet music can be attached to each song.

We may need to organize the frontend code better. A JS framework like Angular, Ember or Backbone might be needed.

The built templates.js needs to be placed in the folder for all the built js files. (of course). The reason this doesn't happen was because handlebar-rider wasn't able to create a new file.

The solution is simple: make sure the destination file exists before running handlebar-rider. :)

Youtube links should be able to be added to songs.

The toolbox needs font size controls.

Use passport.js to implement logging in with Github. We could then possibly use that to edit songs. Maybe.

The index page is only going to get bigger and bigger. We need a way to search through it.

Implement the theme selector in the new UI, again.

Implement a page for when a song that doesn't exist is attempted to be viewed or edited.

Use Jekyll style front matter to add additional information to a song such as:

• youtube link
• key of the song
• etc etc

Could possibly use the front-matter npm module for this.

Need to figure out how to make the application seem cool. Eg, add in animations and more it more colorful.

Split the code up and move the theme selector stuff into a separate file so that it can be used in two places effectively.

There needs to be a 404 page for when a user tries to view a song which doesn't exist.

This ideas has a couple steps.

1. Put the packager script into a separate package.
2. Bundle it with songdown-app so that it can be run with a higher chance of working.

I want to do this so that the app can boot up using a local songdown-songs repo but if that repo hasn't had an npm install done on it, it'll still work.

The Song view needs to have a tool box. A dialog of some kind would suffice. This toolbox needs to contain all the settings the song view has, such as:

• Font Size
• Theme Selector (#2)
• Print Button
• Edit Button
• Transpose Controls
• Youtube Video (#15)
• Tags (#19)
• Song Key (#16)

These won't all be able to be implemented at once (hence the unimplemented ones are separate issues). Otherwise, all that's required is some front end UI work and copy/pasting the code from where it used to be.

Title really says it all. Add a print button on the Edit Song page.

Links on the main page need to be actual <a> tags so that a user can open them in a new tab properly.

Set the document title to the currently selected song.

Songs should be able to have tags. We could show a tag cloud for ease of searching by tag.

This project is in a bad shape atm. Need to spend some serious effort on cleaning it up.