A survey of silly sidebar issues

  • Author
    Posts
  • #319348

    gwideman
    Member

    Hi folks:
    In the process of trying to get situated with respect to theme choices, I decided to step back and spend some time looking into issues with the CSS for sidebars and widgets. So I surveyed all the themes having flexible width and two columns. As it happens, 84% of them have problems that are significant visual distractions that seem unintended.

    If you’re interested, take a look at:
    http://grahamwideman.wordpress.com/2009/01/17/sidebar-style-silliness-survey/

    For all I know, this may merit a “yeah, they’re workin’ on it” or “send this to the QA interest group”.

    If not, then perhaps it prompts some productive ideas on how to raise the base level quality of the off-the-shelf themes, in the area of freedom from rough edges that are easy to fix upstream for the benefit of all.

    Thoughts?

    #319525

    rosclarke
    Member

    Interesting! Just so you know, themes are almost never changed after they have been made available. Occasionally a second version of a theme is added (The Journalist, Sandbox). But it’s a good thought for future theme-makers.

    #319528

    gwideman
    Member

    > themes are almost never changed
    Yes revisions obviously present an issue. If a theme were to be changed after it was already adopted, then the changes might surprise existing users.

    That said, having a lot of friction for revisions means WP.com misses out on iterative refinement (along with us too!). It would be encouraging if there were more in the way of successive theme versions. (But is there even a mechanism for proposing such improvements and getting that feedback to the theme devs?)

    A second interest in such refinement is the situation where taglines are missing from many themes (notably most of the flex-width, 2-col themes). Now that’s a case where WP could create a revision that includes the html for the tagline at a sensible position in the code, but then default it to hidden (via theme option or CSS) with option to show.

    #319532

    rosclarke
    Member

    <i>Yes revisions obviously present an issue. If a theme were to be changed after it was already adopted, then the changes might surprise existing users.</i>

    Exactly. What one person sees as a bug is another person’s pleasing quirk. I think the only way of getting suggestions back to the theme developers is to try and contact them directly through whatever contact information is provided within the theme. You could report it to WP staff too, but they are unlikely to be able to do anything.

    There is a workaround for adding taglines using CSS. I’ll see if I can find the link.

    #319533

    rosclarke
    Member

    Here. You’ll need to scroll down a bit.

    But I agree it’s not the neatest solution, and it does require the paid upgrade.

    #319558

    vivianpaige
    Member

    I could have sworn that I saw a way to put the tagline in without CSS (other than by putting it in a text widget at the top of the sidebar) but perhaps I was misstaken.

    #319563

    rosclarke
    Member

    I don’t think I’ve seen any other way, Vivian.

    #319568

    I’m sure there are many other “quirks” that could be added to this list. The one that is most puzzling to me is the theme that allows a custom image but ends up with a big black vertical stripe breaking that image into two unequal parts (even though the theme’s original image doesn’t have this stripe over it). I can’t recall which one it is, but it’s dark.

    As for taglines, I think an option to show them or not would be great (and probably easy to implement without breaking anyone’s existing blog by setting the user’s initial setting based chosen theme’s current behaviour).

    #319578

    You’re probably talking about Chaotic Soul, but it does have the black bar with the original header – at least for the 2 years I’ve been here. Perhaps you just didn’t notice it because the image has dark elements near the center.

    #319592

    vivianpaige
    Member

    WordPress.COM’s desire to release the theme the way the theme designer made it is the key to understanding why some of these issues – such as taglines – exist. But I have found them to be willing to make changes to themes when there is an error. The OP’s list seems to me to be errors in the coding and as such, if I were the OP, I’d send that information to support and ask it to be fixed.

    #319673

    gwideman
    Member

    vivian: Yes I had seen threads on techniques for getting a tagline to appear, but they seem to involve either CSS pseudo elements (:before or :after) that not all browsers support, or insertion of html via a text widget, where positioning may not suit all types of page. In this thread…
    https://en.forums.wordpress.com/topic/add-tagline-to-rubric?replies=26#post-151293
    … it seemed like you settled on making the tagline part of the header image… was that your final answer?

    #319674

    devblog
    Member

    … or insertion of html via a text widget, where positioning may not suit all types of page.

    Would you please elaborate more on this or give an example where it wouldn’t suit the theme?

    #319675

    gwideman
    Member

    I’m interested to hear more of how the themes come to be created and adopted, and perhaps revised, for wordpress.COM. Are these primarily themes that have been adopted from a pool of themes available for use with regular WordPress? Is wordpress.com mostly relying on original theme authors for continued dev, or is there a distinct in-house fork of those themes? Or perhaps it’s all kind of ad hoc?

    For regular WordPress, theme devs might well expect users to be free to make customizations in either the php or the css, so aren’t necessarily obliged to expose all useful data as html (for example taglines). This would be less suited to WP.com’s CSS-only customizability.

    #319677

    devblog
    Member

    As far as I know the themes used in wp.com are GPL, that’s why the wp staff can adapt them to work for the mu platform. For your other questions, such as “how the themes come to be created and adopted”, I believe someone from staff would be more qualified to give you an answer.

    Now, I asked why you think positioning may not suit all types of page because then I would probably give you a more informed opinion. I believe, however, that positioning shouldn’t be an issue since, obviously, the user would play with the text-widget values to suit their needs.

    #319678

    gwideman
    Member

    >Would you please elaborate more
    I was inferring that from the discussion I pointed to.
    https://en.forums.wordpress.com/topic/add-tagline-to-rubric

    You wrote:
    > This cannot be fixed using CSS only because the single post
    > page source code is messed up. The only way to fix it would
    > be modifying the source code of the template itself.
    […etc…]

    … where you put considerable effort into getting to the bottom of the problem. I now see that perhaps this precipitated correction of that theme’s code, so maybe it’s fixed in that case.

    Regardless, between themes, and between the different page types (eg: front page vs individual past, with/without various options) there is understandably variation in the html output and thus in the specifics of addressing the elements relative to which one needs to place the tagline.

    So, the insertion of tagline using text widget is a trick that has some chance of being sufficient in specific cases, but in advance one doesn’t know that it will work, and whether a request to support will be needed to get some minor code anomaly fixed. Ie: when a user’s at the point of comparing themes, including ones that lack taglines, they don’t know whether activating a tagline is going to be easy, hard or impossible.

    It’s a lot less robust and fiddle-free than simply having themes consistently output the tagline in a predictable unambiguous way, with a simple option to show/hide, possibly via CSS.

    That said, I’m not the one to set priorities around here, for sure. Just commenting on what seem like relatively easy-to-address issues that make adoption easier, users happier, reduces support issues etc etc.

    #319679

    gwideman
    Member

    … or maybe I should just try the Text Widget method and get over it :-).

    #319681

    vivianpaige
    Member

    You wrote:
    > This cannot be fixed using CSS only because the single post
    > page source code is messed up. The only way to fix it would
    > be modifying the source code of the template itself.
    […etc…]

    … where you put considerable effort into getting to the bottom of the problem. I now see that perhaps this precipitated correction of that theme’s code, so maybe it’s fixed in that case.

    Yes, it was fixed. devblog was helping me with The Journalist theme. And because of his great skills, he was able to isolate the problem, which I then forwarded to support and they fixed it. That was what I was thinking about when I wrote that errors in themes are fixed.

    You are not going to convince the tech support folks to put a tagline in a theme that wasn’t in it originally. So yes, the text widget method is your best bet.

    #319689

    gwideman
    Member

    Ah — thanks vivian for filling in that extra piece.

    #319695

    devblog
    Member

    Thanks for elaborating more. Yeah, in the same thread, Vivian contacted support and they fixed the problem.

    I believe you make some valid points. It’s true that adding a tagline like that may be sufficient or will make a bug in the code to come up; but as users we ‘have to trust’ that staff ported the theme correctly, and tested it thoroughly before rolling it to production, but we won’t know till we try adding a ‘feature’ the theme lacks, such as a tagline.

    To finish my comment, I believe that your idea of giving the user the option to have, or not, a tagline is a good one. It’d would be more user friendly than creating a text widget and position it using CSS.

    #319697

    devblog
    Member

    slow much? I need to type faster…

The topic ‘A survey of silly sidebar issues’ is closed to new replies.