I'd love for someone to consider the content types we have on groups.drupal.org and style each of them differently so they stand out in listings. If folks want to suggest moving fields around, or adding new ones I'm open to that too. The minimal though is a visual distinction between types. The types we use are:

Event
Image
Job
Group
Poll
Story (this is a standard post)
Wiki page

We have had some proposals for icons - http://groups.drupal.org/node/6422

Comments

aclight’s picture

Status: Active » Needs work

This is a good idea but it needs to be written in task form with specific instructions on what is needed for the task to be complete.

See http://code.google.com/p/google-highly-open-participation-drupal/wiki/Ho... for notes on what we're looking for when it comes to a task. Also see http://groups.drupal.org/node/7360#tasks

I don't think your description makes it very clear what kind of styling you're looking for to make the different content types stand apart. Clearly setting the backgrounds of different types to different colors would make them stand apart, but I don't think that's something you'd be happy with. It's hard for everyone to review tasks like this that involve creativity or style, since there is no defined standard for when something like that is finished. That's why it's helpful if you can be clear up front about what is acceptable and what isn't so that both the student and reviewers have a sense of whether the student has completed the task.

Also, wouldn't this task require that the student have access to the relevant blubeach template files? If so, are you willing to provide them to the student? If not, how do you expect the student to submit the work (since you can't really roll a patch if you don't have the original file)?

dvessel’s picture

They could still provide mock-ups after a discovery phase then hand it over to someone who has access to the theme. Would still be useful.

True, it is a bit vague. How about linking to each content type to show the current state. Let the student absorb the differences so he/she can think of some ways of presenting the differences. Would require someone with creativity.

webchick’s picture

Component: GHOP Task » Task idea
matt v.’s picture

Component: Task idea » GHOP Task

I think this would be a helpful project, so here's my attempt to taskify it. My apologies if this strays too far from the original intent. I'm open to feedback and corrections on it, especially on the sections marked with "???". If Moshe Weitzman isn't available to be the primary contact, I'd be willing to do it, though I don't have access to the existing groups.drupal.org theme files.

----

Task title: Create themed mock ups of each of the node types used withint groups.drupal.org.

Task description: The groups.drupal.org website is a gathering place for a variety of special interest groups within the Drupal community. The site uses a variety of content types. This task requires the creation of distinct visually themed layouts for each of the following node types used on the site:

* Event (ex: http://groups.drupal.org/node/7054)
* Image (ex: ???)
* Job (ex: http://groups.drupal.org/node/7699)
* Group (ex: http://groups.drupal.org/ghop-2007)
* Poll (ex: http://groups.drupal.org/node/5041)
* Story (ex: http://groups.drupal.org/node/7699)
* Wiki page (ex: http://groups.drupal.org/node/7360)

The new themed nodes should blend well with the existing overall site in terms of color scheme, fonts, etcetera. Students will thus gain experience in theming Drupal, working within the constraints of an existing site design.

Deliverables include a themed node-[nodetype].tpl.php file for each node type, as well as any associated images and style.css files. These files should be posted as an attachment to the drupal.org issue associated with this task.

Resources:
* Discussion of possible icon files: http://groups.drupal.org/node/6422
* INSERT LINK TO EXISTING NODE-[NODETYPE].TPL.PHP FILES IN USE ON GROUPS.DRUPAL.ORG OR POINTER TO STANDARD TEMPLATE FILES???

Theming Resources:
* Theme developer's Guide: http://drupal.org/theme-guide
* Theme development forum: http://drupal.org/forum/3
* Theme development IRC channel (#drupal-themes on irc.freenode.net): see http://drupal.org/node/108355
* Theme development group: http://groups.drupal.org/theme-development

Primary contact: moshe weitzman???

Drupal issue: ???

aclight’s picture

Component: GHOP Task » Task idea
Status: Needs work » Needs review

I'm setting this as CNR even though there are still some things to fill in.

FYI, se use Task idea as the component for proposals, and GHOP task only for tasks that stay in this project's queue when made "official" because there isn't a better project for them to be moved to.

matt v.’s picture

I see. I misunderstood the distinction between Task idea and GHOP Task. Thanks for the clarification.

moshe weitzman’s picture

I'm willing to be primary contact. I feel like the easiest way to proceed is for users to save the example pages above to their hard drive. they can then adjust HTML and CSS as desired. Then they submit a diff of before/after. I will take care of applying their changes to the site. They should also provide any new images.

aclight’s picture

Status: Needs review » Needs work

I think Matt V's write up of the idea in comment #4 looks pretty good.

I also think Moshe's idea in #7 is fine with me. So the deliverable will need to be changed a bit to fit with what Moshe said.

My only concern with Moshe's idea is how people will review the student's work. I guess we would want to specify that the student should use those exact nodes for this task, but even then any dynamic content will probably mess up applying the diff automatically (vs. manually) to those pages. So perhaps we should request screenshots of each node type to be reviewed as well? Or if anyone has a better suggestion that would be helpful.

So, I would say to fill in the unknowns in Matt V's task proposal, fix the deliverables section to match what Moshe said, and within the deliverables section provide instructions for submitting the work that will make it relatively easy for those of us who don't have Bluebeach access to review.

This should be a really interesting task!

moshe weitzman’s picture

how about this - 'student attaches a zip containing before/after for each node type page. moshe will later diff the two and apply to bluebeach.

the only one who ever has to care or see the bluebeach theme is me.

aclight’s picture

That sounds good to me.