jefflunt / fedexday Goto Github PK

Standard RSpec + Cucumber

If an idea hasn't been touched for 9 months, and it's currently "scratched", then destroy it.

There's currently no styling on flash messages. This isn't a huge deal, but they go unnoticed because they sort of blend in. A very minor highlight (green, yellow, red) backgrounds would be more than sufficient to address this.

The asset pipeline is being completely ignored right now, and as a result, it's probably slowing down the production response times every so slightly. Wouldn't it be nice if the Capistrano deploy task would automatically compile the assets on the deployment server for you?

Many of the controller actions have a json reply element that was placed there by scaffolding. I don't have any expectation of supporting json anytime soon, so I may as well take it out.

Comments and idea descriptions should be able to include sanitized email and url links.

Among these are several in the comments and endorsements controllers.

The ordering of the Ideas on the ideas#index page isn't covered in the test suite. Will would have added a test, but I didn't have a test suite at the time for him to add to.

Add the "Submitting FedEx day ideas" idea to the DB seeds, so that upon install, the database will have the instructions necessary to tell people how to use it.

Either straight up destroy, or a simple "scratch" toggle, similar to the 'idea' model.

People make mistakes all the time and/or don't read what they've written before saving the comment. Simply allowing an edit should be sufficient to correct this.

In the top-right corner of the page is the date for the next FedEx day. This should go into a config file, or maybe even be fully editable through the UI, like everything else on the site.

They're basically hard coded at this point, which is fine, but ever so slightly sloppy.

Right now it's being deployed via a manual git checkout. It works, but if the app is a success, we'll want to automate this.

When it comes to comments, it's difficult to have a conversation without some kind of mechanism of referring back to one another. That is, if users had names, you could @reply to people and have a conversation around issues.

Anonymity was implemented because it was the simplest possible way to get things going, but if the project gets used elsewhere, it would be helpful to have users with accounts. Perhaps anonymous comments, and other actions by anonymous users (being able to read anything) could still be available, in order to encourage new users to participate.

Be notified, via email, when an idea you've participated on is updated. It's the "notifications" model that keeps people coming back, and keeps them building a community.

On the index page, scratched ideas have a line through them. Problem in, this is added manually with a <strike> element around the link, instead of adding something like a scratched class to the link, and then styling scratched classes with text-decoration: line-through

It currently redirect_to :back but should redirect_back_or ideas_path