1.)
On the defaut frontpage nodes are not clearly (optically) seperated (see attached picture). I would suggest something like
.node /* Node wrapper */
{
padding: 0 0 30px 0;
}
in the austin.css (line 342)
2.)
I think an clear a:hover on navigation-elements would improve the usability. I'm not quite clear, what Mark B. suggested in the design-specifications at http://cmsshowdown.com/. On www.drupalshowdown.com/ itself the hover-elements are used inconsistent. The slider on the frontpage uses hover-elements, but "normal" pages don't use hover-element on sub-sektions (e.g. http://www.drupalshowdown.com/about). I think some CSS like
#sidebar-right .block li a:hover /* The hover item in a Drupal menu */
{
background-image: url(images/subnav_active.png);
background-position: left;
background-repeat: no-repeat;
}
in the austin.css (line 688 ff) could be an improvement.
Sincere regards
Gluhm
Comment | File | Size | Author |
---|---|---|---|
node styling.jpg | 173.99 KB | Gluhm |
Comments
Comment #1
caroltron CreditAttribution: caroltron commentedI will look into both of these. thx.
Comment #2
caroltron CreditAttribution: caroltron commentedI just implemented both of these suggestions. #1 I added to view-styles.css b/c it directly impacts the home "promote to front" node style view. #2 I moved that css from austin.css into navigation.css since it is really belongs there instead. I have implemented the white arrow hover effect as you suggested but might change this in the future to something different. Due to the constraints of the CMS showdown Mark Boulton didn't have enough time to design a complete toolkit for this theme, so you will find that some elements like hover, etc. are inconsistent b/c no rules were added in the CSS b/c the design didn't describe how this should work. I will work with these stylings to make the theme more usable.
Thx!
Comment #3
caroltron CreditAttribution: caroltron commented