When you read actual paper user guides, they often have sidebars with related info and tips and warnings with a special graphic or formatting to make them stand out. I would like to be able to do this in drupal.org's handbook. So I'm requesting some additions to the CSS as well as additions to the HTML filter.
There are a couple of ways this could be done. One way would be to add more div IDs so I could do, for example:
<div class="moreinfo">
Related links:
link1
link2
</div>
and have that float off to the top right (or wherever) in a seperate box with a border. There would also be div IDs for "tip" and "warning" (others?). If divs aren't an option, perhaps another sort of marker along the lines of the !--break-- one?
I'm not picky about how it gets implemented; I just hope it's possible to do one way or another. By doing it with CSS rather than trying to fudge it with what we have, these special info boxes would be standardized across all handbook pages.
Thanks,
Michelle
Comments
Comment #1
laura s commentedBig +1 from me. The more we can spruce up the handbooks with these kinds of things, the more usable the handbooks can be.
Comment #2
beginner commentednice idea. +1
Comment #3
avpadernoDoes this still need to be implemented?
Comment #4
michelleStill needs to be either implemented or won't fix'd. It hasn't ever happened. Needs someone to decide whether to allow it or not. Tagging for the redesign and moving back to the proper queue. This isn't a "textual improvement"; it's a change at the theme level.
Michelle
Comment #5
avpadernoIsn't there a component Redesign on Drupal.org webmasters queue? Actually, I meant to put it there.
Comment #6
michelleAll right, I can live with that. I don't know which method the folks actually working on the redesign prefer. I vaguely remember adding that component as a way to group things before we had issue tagging so I don't know if they still use that or just use the tag. Either way, this feature was never added, is still a useful idea, and needs someone to make the decision.
Michelle
Comment #7
avpadernoI apologize for having moved the report from a issue queue to another. I was trying to move it to a place where it could be more visible; it seems that some issues posted in the Drupal.org infrastructure queue pass unobserved, and they are kept open even when they have been fixed.
I think the feature should be implemented.
Comment #8
michelle@KiamLaLuno: That's fine. I see you've been working hard on the queues. It's just that moving something that requires a change to the theme to "webmasters: textual improvements" isn't going to have the right people looking at it. The redesign component, though, does make sense as it's not likely to be implemented in Bluebeach anymore.
Michelle
Comment #9
lisarex commentedLinking this from the Redesign project #661566: Meta issue for Drupal.org webmaster project because this issue was tagged 'drupal.org redesign'
Comment #10
todd nienkerk commentedThis is addressed somewhere in the redesign. Reassigning the issue to the redesign project.
Comment #11
lisarex commentedMoving to new section-specific component.
We can look at this after the initial design is implemented.
Comment #12
tvn commentedMoving to Bluecheese project as Redesign project is over.
Comment #13
drummThe documentation team has been great at working on improvements to their section of the site. The last roundup of efforts is at http://groups.drupal.org/node/174499. In particular, #1278256: Develop a plan to make it more clear that the current Documentation on drupal.org is community maintained. might be related to this. Their current efforts should supersede any previous work from the redesign. If something good is missing from the current efforts, look for how to fit it in.