Posted by sagannotcarl on April 9, 2009 at 12:22am
Jump to:
| Project: | Drupal.org customizations |
| Component: | User interface |
| Category: | task |
| Priority: | normal |
| Assigned: | drumm |
| Status: | closed (fixed) |
| Issue tags: | drupal.org redesign, drupal.org redesign sprint 4 |
Issue Summary
There is a meta data block on documentation pages. This block needs to be generated by the template and styled.
See: http://infrastructure.drupal.org/drupal.org-style-guide/prototype/docume...
| Attachment | Size |
|---|---|
| Picture 34.png | 49.23 KB |
Comments
#1
Some of this is already implemented in the drupalorg_docs module. Many of what should be done here is coding, so it was done in the module. See http://staging.dosprint.org/getting-started for current output. Please continue development there.
#2
I mean coding in that module, theming in the theme, so issue applies to both projects.
#3
Also, please note that we are not ready to implement everything in the prototype. Specifically:
Authors: should not be listed at this time. There was a big hubbub about this just last year with strong opinions on both sides. At the least, if they are listed they should not link to the user profile.
Languages: are not implemented yet and probably won't be for a while.
Tags: we have multiple vocabularies for book pages right now and none of them are free tagging. We probably need to think about how we will handle this. Do we just list all terms, regardless of vocab here? If so, then "add a tag" does what? etc.
Quality Alert and notes: these are not implemented yet. We do have a "status" vocab and we have been planning to use term_message module to display a meaningful message for each status. Not sure if that fits with this or not. We also do not have a "discuss" area and there is even an issue to disable comments on book pages altogether in favor of tying issues to pages, #413882: Integrate issue queue and pages: disable doc comments. So not sure what discuss will even mean for us. Maybe a list of issues associated with the page (assuming we go the issue routs, which I have no idea if we really will or not)?
So, anyway, I guess I am saying we need to implement a bare minimum meta block for now and leave out anything that is actually a feature until we decide how we are implementing certain things.
#4
I am moving the report to the correct issue queue.
#5
Removing the "Bluecheese theme" tag, as we need to retire it. The "drupal.org redesign" tag is better suited for these cross-project issues.
#6
#7
We should probably also put the existing taxonomy for pages in that block: Audience type and Page Status
#8
The placement introduces a fair bit of noise that blocks the eyes when you go from the heading to the start of the article.
Could we style this to default to a collapsed state so that only people who care would have to look at it? It definitely shouldn't be the most prominent thing on the page. Maybe the version number would be worth seeing on page load but not the rest of it. I think the tags actually belong at the bottom because they fit with the natural flow of a reader who says "ok, now that I've read this article what else is there?" whereas if we put the tags at the top it's a bit weird because we're already pointing the reader to other places before she even gets a chance to look at what's on this page.
Also I think the "authors" credit is really not going to work for many reasons.
#9
although lee's suggestions are great, i know that new suggestions aren't really on the table right now - for the time being, like jennifer pointed out, as long as the tags we currently use are all there, that'll be fine.
#10
- Page status taxonomy should map to an alert
- Audience type taxonomy should be shown like Drupal versions already is
- Borders need to change from black to orange, plus any other details
Specific code is at http://drupalcode.org/viewvc/drupal/contributions/modules/drupalorg/drup...
#11
Can someone post a mockup of what is currently planned to be in the meta-data block on doc pages, so we can comment on it intelligently?
Looking at the current staging site (for example http://redesign.drupal.org/handbook/modules/node), we seem to have lost the existing "Audience" and "Page Status" taxonomies that exist on drupal.org -- otherwise, what is there now looks fine to me, but I am confused about what is planned for this block.
#12
#13
Set this up to use all terms in all vocabularies, except 'no known problems'. Other terms in 'Page status' get a alert icon since they are all bad.
#14
Automatically closed -- issue fixed for 2 weeks with no activity.