firehosecommunity / lightningtalktopics Goto Github PK

The Navbar on the lightning talks should look like the rest of the Firehose Project navigation bars.

Remove the Firehose Links link from the navigation bar since we have a footer section with all of the relevant links. There is corresponding CSS that should be removed as well, we don't want unused code laying around.

Go through styling and setup vendor prefixes for specific CSS attributes.

Ex:

• Transition
• Flex
• Flexbox

The landing page looks buggy on Safari because of flex attributes, needs to have a vendor prefix established so it looks like it's suppose to

We can use Bootstrap glyphicons on nav bar

Ability to do basic bold, italics, etc WYSIWIG editor would be nice

Add a Resources section that will include any relevant links, videos, and slide decks that support each individual talk.

Should authenticate the user before adding a vote. Then limiting the vote to one per topic. That way any one person can't decide the flow of the next lightning talks.

As a contributor, student, alumni, or outside party I would like to see who has contributed to the project.

This will entail adding a section at the bottom of the Readme with these categories:

1. First Name
2. Last Name or Last Initial (optional)
3. Github username
4. Other potential links (Twitter, Facebook, website, etc)

All the students who have contributed should be acknowledged for all of their hard work 😄

Currently it's the Wild West with votes, there are 0 limitations to how many times a person can vote on any topic. This should be limited to 1 vote per person per topic.

The layout of the index cards need some work.

Here is what I think it should look like. If you have other suggested please post and we will discuss them.

The Firehose Project uses Open Sans font and as this is part of the Firehose Project ecosystem we should reflect that within this app.

Each time I send out a quick reminder about lightning talks to students. The reminder email looks like this:

Getting the text for the upcoming talks is a bit hard. This is because the current app lists out each of the students that is assigned, so I have to pay attention to the date:

Also sometimes I have to dig into the detail page because the description is truncated:

Here's how we should fix this.

When a user clicks the link they should be presented a page that includes the roster in a copy & pastable way. So the following text would be on the page, formatted like this.

Continuous Integration (Faisal)
What is Continuous Integration? How does it work? And an overview of two of the options out there: Travis CI & CodeShip.

Illustrator for Developers (Mikaila)
How to quickly get started with Illustrator and apply it to your workflow.

Pry for Rails (Chris McIntyr)
Pry is a powerful tool that helps debug complex programming problems. Learn how to use this awesome tool!

Scraping With Import.io (Nehemiah)
Using Import.io to quickly and efficiently scrape websites to import into your Ruby on Rails app.

Vim (Ben Ricker)
Vim, a command line editor. Why you should use it? How you should use it? Advantages/ Disadvantages.

houndci.com is a service that will check pull requests to make sure they are following the ruby style guide.

Some talks have been assigned to people for nearly a year without them having the ability to give the talk. As it stand we have no ability, through the site, to remove a talks status as being assigned.

It would be nice to have this ability so orphaned talks could be reassigned to someone else.

Votes method is currently in the talks controller which doesn't necessarily need to be there. We want to focus on skinny controllers fat models and with that we should figure out a way to move the votes out of the controller.

I suggest the "brand title" of the navbar should read "Firehose Lightening Talks"

It currently reads "Firehose Project" and that gives two potentially erroneous impressions to users:

1. That the app is PART of the Firehose Project App proper and thus doesn't require signup for folks who already have a FHP login - this is a distinct App with a distinct userbase
2. It appears the link may lead back to the Firehose Project home page rather than back to the Lightening Talks index page

For that brand title to contain "Lightning Talks" is meaningful UX for users. It will indicate clicking on that link will take them back to the main index of Lightening Talks.

Changing that to "Firehose Lighting Talks" would also agree thematically with the "Firehose Links" nav dropdown.

This is a simple change, and with approval I'd be happy to make it myself.

The Controller Needs Some TLC

The controller has a lot of repetition. I was hesitant to clean this up simply because I wanted students to be able to have the opportunity to contribute and this would be a great learning experience.

Creating a private method and using a before_action would be a great approach to cleaning up the repetition.

The about page is pretty empty right now.

We should probably add a new about page to the lightningtalks app :)

Assigned method is currently in the talks controller which doesn't necessarily need to be there. We want to focus on skinny controllers fat models and with that we should figure out a way to move the move out of the controller.

Talk topics should only be able to be unassigned by the person who assigned them or by an admin. Currently if a topic is assigned it can be unassigned by anyone, this needs to be fixed.

These should be filtered out:

Setup a Continuous Integration System

Travis CI would probably be the best to setup, however, if you have suggestion we can have a discussion on the topic.