Meta data block on documentation pages
sagannotcarl - April 9, 2009 - 00:22
| Project: | Drupal.org Redesign |
| Component: | Documentation |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
| Issue tags: | drupal.org redesign |
Jump to:
Description
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 |
#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