jklina / fixelpuckers Goto Github PK

Right now there's arrows for up and down voting for reviews. The following are some interface questions:

• How can someone unvote?
• How is it marked when a user has already voted?
• Where does the vote tally go?
• Should we have a list of people who voted up and down?
• Should reviews be sorted by vote tally?

Could be just a link and JS popup, but whatever you think is best.

Maybe like a banner or badge or something to let the author know that the submission he's viewing is trashed.

On the index page we have a list of submissions. I'm trying to figure out the best way to organize these and have some thoughts/questions.

• Do we force all the submission thumbnails to be the same size?
• What information do we want to display on the index?
  • Author and Title feel important
  • I was thinking of encoding other dimensions as well such as:
    • badges for different configurations of reviews. Maybe there's a badge for a bunch of really good reviews, or a badge for a controversial submission, or a badge that says you're popular among tough reviewers
    • If we don't want to go all out on badges we can maybe put some rating information on the index page
    • something that says if a submission was an update on an existing submission

My point is that we can (but this might be a bad idea) be more creative than just throwing up a grid of thumbs. It might be a neat opportunity to be creative and figure out sexy ways of encoding useful information that might encourage more involvement.

What ya'll think?

Just need some markup to make the login pages fall in line with the rest of the site. Info on the form locations can be found here:

https://github.com/thoughtbot/clearance#overriding-views

Currently most of the views are still in the Clearance Gem, but if the markup needs to be changed we can override them. If you need help with this just let me know!

Think it would be a good opportunity to put some element that encourages someone to give a rating on a submission that doesn't have one.

User's need to:

• Edit
• Trash

Admins need to:

• Feature
• Moderate

The following line causes some CSS interference:

https://github.com/jklina/fixelpuckers/blob/master/app/views/layouts/application.html.haml#L12

You see it when you're on the user page and try to update an existing user comment with a blank comment.

Right now ability tests are in the user spec file.

The Idea

This is a personal thing, but I felt like it should be discussed. The forums on PF seem like they have potential, but they are less than an afterthought at the moment, where a lot of life and activity for the community could be happening, projects, ideas, tips, top lists, etc, there's a ghost town. What if PF had a more advanced and better integrated forum, so that the front site could be reserved more for the best screenshots, while others who are just beginning could learn how to customize more?

What brought this idea on?

I'm thinking a lot about MacThemes.net, which recently went down, for what seems to be indefinitely. That forum was thriving, and I feel like PF could really be a cross-platform version of what MacThemes was, people with a love of custo, on windows, mac and every flavor of the linux rainbow.

What do you all think, should PF have a more advanced forum?

Should PF ditch the forum?

Or finally, should the forum just be left the same, and we see what happens with v2?

Was thinking we could give an option to host submissions on github. Then we can show github info on PF. Thoughts?

Hey p-fuckers,
We can add info about what a person uses,like hardware and software,on his profile page.Little like usesthis.com. awesome site it is.

Currently we use 1-100 to rate submissions. We also have separate rating categories for admins/staff and users. Should we keep this or role with something different?

The slider is nice, but I think we should also have a text field where users can enter their rating directly since it will be faster. We can bind the slider to the text field. My main purpose for a slider is actually to use it as a cue and guide to give the user a sense of relevance as to how good of a rating is being given.

Rolify is overkill and can be removed.

Currently Submissions and Reviews belong to a User, but that relationship should be aliased as "Author" to be more clear and less confusing.

If reviews can have comments we'll need an interface for handling that.

Currently the body part of the Review model is called "comment" which is confusing with the model called Comment. We would rename a Review's "comment" column to "body".