The ccf from chadfennell

Create a new "About" widget

Create a new "About" widget on the right-side of the main "Campus Codefest 2014" page (above the existing "Schedule" light gray widget).

Leverage the use of content from the http://apps.oir.umn.edu/campus_codefest/about page's "About" section in order to populate this new widget.

Please touch base with Chad Fennell before proceeding with this issue.

Relabel "Settings" to "Preferences"

Under user's profile drop down (upper right hand corner), relabel "Settings" to "Preferences"

Add a more detailed event schedule

Add a more detailed event schedule. In addition to the high level overview of dates and hours, include more detail of the daily schedule (e.g., 8:00 - 9:00 breakfast, 9:00 - 9:30 pitches, etc.)

Create an editable "Department" field

On the "Settings" page (to be relabeled "Preferences" - see issue #19 ), create an editable "Department" field (mapped to the USER.DEPARTMENT database field).

User: "So I just visited http://apps.oir.umn.edu/campus_codefest, clicked the "Get Involved" link and found Chad was displayed as the logged in user. A partial is being cached that shouldn't be, or worse - something wrong with session handling."

(Originally reported 3 months ago by mjb)

Reply from pete2786: "Thanks, I think it's due to an old cookie from the beta testing... but I will take another look at the logic."

Order Names and Avatars alphabetically by first name

Under the "Who's attending" section, default order the Names and Avatars alphabetically by first name.

Remove UMN-specific branding from theme layer

Remove UMN-specific branding from theme layer. Make theme generic (see related issue #9).

Update information from Google Auth when logging in

As is, we never again touch the information we get from Google after a user is created in our database. To improve this, we should check the information google sends (particularly the image, which we use for our avatar) to update if the user has new information.

Would be a nice task to check out omniauth, how it works and what it returns from a provider. Check out the SessionController and User model to see how this currently works.

Move the location of the "Register" / "Unregister" button

Move the "Register" / "Unregister" button from the right side of the page to a location toward the upper left side of the page instead.

One Config File to Rule Them All (well, most of them)

Move oauth, email, and other various config into a single yml file to simplify installation and code.
Leave Rails standard things, like database.yml in their original locations.

Improve formatting of drop downs

Improve formatting of the drop down menus. For example, modify the alignment of the "Events" drop down menu options.

Site Stickiness - Revamp Notifications

Generalize messaging
Push messages to a cue for background processing
Investigate twilio integration for SMS messaging, just for fun

Use Bootstrap tooltips on Avatar icons

Use Bootstrap tooltips on Avatar icons (in both the "Who's attending" section and in list of Volunteers under the "Proposed project ideas" section).

Pretty Codefest archiving, marketing and long-term project tracking

Display individual's department under the "Who's attending" section

Under the "Who's attending" section, display the individual's department behind his/her name within both the Name list and in the Avatar tooltip. (See issue #20 for the creation of an editable Department field)

Reminder to users to use their likes

It would be neat to have a little warning or message to people to tell people that they should use their likes/thumbs ups.

(Originally reported 7 days ago by kemal)

Create / display functionality for user to un-register for Codefest

Create ability for user to un-register / cancel registration for the Codefest event. If this functionality already exists, make it more obvious / intuitive to the user.

UX/Usability testing

Implement "moderator" role

Implement "moderator" role, for approved non-admin users to clean up projects, comments, volunteers, etc.

Create a new

Upon registration close out, auto-update app's text to specify that registration is now closed

The app's admin can set a timeout for when registration is to close. When this timeout occurs and registration is closed, in addition to hiding the registration login button, also auto-update the text on the site to specify that registration is "now closed."

Specifically, modify the text of "Registration is now open for the second annual Campus Codefest!" to something like: "Registration is now closed for the second annual Campus Codefest. Please join us next year!"

Project tagging, organizing

Prepare app for future Hackathons

Pull the UMN specific language and static text from the app, package it up, put it on github.com as OSS for future Hackathons.

User deactivation/deletion

Need to decide how to handle user deletion/deactivation. Should we allow users to delete their account? If so, what happens to the following entities:

Projects they proposed
Their likes/helps
Their comments
The record of events they registered for in the past

I was thinking a good and easy workaround would be to add a "de-active account" link in the account settings, which simply detaches their account by nulling uid/email/image and re-assigns their name to something like "Former user", "Deactivated User" or something similar.

(Issue originally reported 3 months ago by pete2786)

Investigate Migration of Email to Mailgun

Initial migration simply replaces current smtp setup
Potential secondary project: allow users to post comments via email

Revisit and possibly add/modify text within the "Proposed project ideas" section

Under the "Proposed project ideas" heading, consider adding brief text to describe this section in order to inform participants of its use and purpose. For example, include text such as:

"While you aren't required to sign up for a project in advance, by signing up for a project now, you are helping the Campus Codefest committee plan for the event. Please do not sign up for more than 1 - 3 projects."

And / or consider modifying the project sign up button's text from "Sign in to help" and "Help with idea" to something like: "Express interest in helping" so that it conveys the notion of "wanting to help with a project" (without the user necessarily feeling bound / constrained to that project when s/he shows up at the Codefest event).

Please touch base with Chad Fennell before proceeding with this issue.

Change the way registration works

Need to make sure it is clearer to the user that they registered, and the links to registration are in the best possible place, UX-wise.

(Originally reported 7 days ago by kemal)

Adding moderator role to edit comments (role vs cancan ability)

Just to be clear, its ok to add "Moderator" as an ability using cancan? The gem is there, so I thought I'd ask. Or should "Moderator" be a full fledged role?

Address "Email us" functionality on the Contact page

Depending on the browser, upon clicking the "Email us" link on the Contact page, nothing happens or an error message is displayed (e.g., if user doesn't have e-mail program installed). Since many UMN attendees use web-based Gmail, address / modify the "Email us" functionality.

Move the "Voting enabled" checkbox so that it is displayed above the "Voting end date" date drop downs (so that it's consistent with the order of the "volunteering" check box and date drop downs).
Remove the asterisks from the "Voting enabled" and "Volunteer enabled" check boxes (because these don't seem to be required).
Default the "Voting end date" and "Volunteer end date" date drop downs to NULL (so that the admin has to proactively select an end date).
Modify the text of "Voting end date" to: "If voting is enabled, set the voting end date to:"
Modify the text of "Volunteer end date" to: "If volunteering is enabled, set the volunteer end date to:"

Please touch base with Chad Fennell before proceeding with this issue.

Improve design, theme, logos, etc.

Flash pertinent information to users upon registration

/via @pete2786

"making the registration controller point to a "success" or "thanks" action after registration is complete which contains the most pertinent information a registrants needs to know. A call to "like" and "help" on projects. Also, it should include a link to the event page."

Migrate from current server to shared/CCF specific platform

chadfennell / ccf Goto Github PK

ccf's People

Contributors

Stargazers

Watchers

Forkers

ccf's Issues

Recommend Projects

Recommend Topics

Recommend Org