Make the carousel in the home page responsive.

We need a way to generate mailing lists so officers can easily send newsletters to the club.
There are a few really good platforms to do this on that we can leverage the APIs of.

Three good ones that come to mind:

1. Mailchimp - free accounts can send to 1000 unique users at once, very nice looking emails
2. Google Groups - free, extremely powerful for announcements, leverages Google APIs
3. Postman - don't know much about, but have used in past and it worked pretty good

Thoughts?

The officers need to be updated to reflect the current EXE officers.

And a bitcoin URL, because why not?

As mentioned in #34 as a potential option for a payment/donation button, as well as Facebook feeds (solving #17), forum/blog posts, and some other "at-a-glance" information. Should also be collapsible for mobile.

We have all the names and the pictures, but the buttons on the officers page don't do anything at the moment.

We need to not only validate syntax with our tests, but also validate site functionality.

We need a favicon for our pages. A favicon is the little 15x15 icon that shows up on your tabs, and if you bookmark the page.

Local logins/signups should be removed from the site, as the net ID and Facebook logins are sufficient.

It is generally bad practice to have all the static content in the root of the repository. Could we move all the html files and the CSS and Scripts directories to a folder named "static" instead of placing the files in the root?

Navigating the forum is a bit clunky - the forum path should be visible on each post in a link chain that looks like this:

EXE Forums > Topic Name > Thread name

where EXE Forums links to /forums and Topic Name links to /forums/Topic Name. (Thread name shouldn't need to navigate to itself, as you would already be on that page.)

Routes should be in separate files pertaining to the specific functionality they provide. For instance, forum routes should all be placed in a forums.js file, payments should all be in a payments.js file etc. and they should be included in the main app.

We have CSS rules defined for mobile and tablet computers for carousel images, but currently do not have the appropriately sized images. We need to create them and insert them into the CSS @media selectors.

Topic pages have the name of the last poster and the total reply count for each thread.

The main forum page should have a link to the last updated thread within each topic, the person to last post in that thread, as well as the total thread count for the topic. View count could also be a nice feature, although that has not been implemented anywhere yet.

The link text on the career page drop down is very hard to read as is.

We need to look at all files for any accessibility issues.

The date picker on the signup page is not supported in many browsers. We should replace it with something that at least also supports Firefox.

Facebook logins fetch the user's email and name, and serve as a replacement for a username and password. However, additional information, such as shirt sizes, graduation dates, and classifications are not prompted during signup as with Facebook logins.

Instead of automatically logging in the Facebook user and rerouting them to home, the site should redirect to a "additional info" page where we can capture the rest of this information.

Swig is nice, but there are some features of Angular I really would like to have - in particular, signups and logins without leaving the page you are on, more responsive pages (especially for the career pages and the forums), and if we deliver JSON data to the website for use in angular, we can easily use the same "API" to interface with an app (perhaps in the future for our appdev team?)

However, the site would have to be converted to use Angular templating instead of Swig templating. Would it be worth it to make the switch?

We need the navigation bar to list all the projects for the project button.

It is easy to find the login with Facebook option if the login button is clicked, but can easily be missed if you go to the signup page - a link to "sign up with Facebook" should be on the signup page

At least so a user can edit their email preferences and opt-out of the newsletter if they so chose to.
Also might not be bad to have a forums preferences page, such as number of posts to display per page, forum display name etc.

The profile edit page is outdated, and should be replaced with the new bootstrap page.

As discussed in #34, we should either add this to a sidebar (per #37) or a drop down on username mouseover. The current payment page is at /pay, and really just needs to be linked to somewhere on the site.

Upon initial signup, the user should be redirected to a "success" page, and there should be a link on that page to "pay dues now" (redirects to /pay) and "skip for now" (redirects to /). This should hopefully get people to pay dues immediately after making an account.

The side navigation bar is unused in many of our pages, and looks bad on mobile. We need to either remove the sidebars completely, or make them responsive with Bootstrap.

Make the carousel in the home page responsive.

Ahem,

someone removed some function calls in the body tag when switching to using the template engine.

We should have a page to signup for events that are listed on the EXE calendar.

We have a nice calendar page, but it would be really cool if we had a way for officers to create events on the website.

We have so many pages under career that they should be in their own folder, so pages would be like /career/phoneinterview.html and what not.

We need to remove the project groups that are no longer part of EXE from the projects page.

"please refer to the official documantation." -> "documentation"

I have a few ideas for how to do this:

1. Using a homebrewed CMS on our site
2. Using a Wiki platform such as Mediawiki or Confluence
3. Not implementing anything, and letting groups create their own site on platforms such as Wordpress or Blogger and linking to those sites

Thoughts?

App.js needs a refactor.

In particular, the following ought to be done:

1. Authentication methods should be moved to a separate module.
2. All routes pertaining to a certain feature with more then just static code (i.e. forums, payments, calendar) should be moved to separate files.
3. Tests ought to be written for ALL non-static routes for ALL desired functionality..
4. A full code review should be done of existing code, and comments should be added where necessary to better explain the app.