Deprecated: Assigning the return value of new by reference is deprecated in /nfs/c03/h06/mnt/47169/domains/themehybrid.com/html/community/bb-settings.php on line 186

Deprecated: Assigning the return value of new by reference is deprecated in /nfs/c03/h06/mnt/47169/domains/themehybrid.com/html/community/bb-includes/backpress/functions.wp-object-cache.php on line 108

Deprecated: Assigning the return value of new by reference is deprecated in /nfs/c03/h06/mnt/47169/domains/themehybrid.com/html/community/bb-includes/backpress/pomo/mo.php on line 171

Deprecated: Assigning the return value of new by reference is deprecated in /nfs/c03/h06/mnt/47169/domains/themehybrid.com/html/community/bb-includes/functions.bb-l10n.php on line 484

Deprecated: Assigning the return value of new by reference is deprecated in /nfs/c03/h06/mnt/47169/domains/themehybrid.com/html/community/bb-includes/backpress/class.wp-taxonomy.php on line 581
Name Hybrid widget sections and other ideas « Community

Welcome, guest!

Feel free to read the blog, browse for themes, or join the club.

The community forums are currently being phased out. At the end of February or early March 2012, you will no longer be able to post here. This is because the entire site is being restructured. Please use the main forums for discussions.

Name Hybrid widget sections and other ideas

  1. I'm hoping to add new "utility" widget sections to Hybrid in the future. I've also got an upcoming Hybrid magazine-style child theme. So, I figured I'd try and kill two birds with one stone.

    The layout of the magazine-style theme is here:
    http://themehybrid.com/blog/wp-content/uploads/2009/01/widget-areas.png

    Notice the areas with the question mark? I need to name those.

    I also want to make Subsidiary and the two ?s before and after the content area permanent featues for the Hybrid theme.

    I generally call these "Utility" widget sections. I could easily call them "Header," "Before Content," and "After Content." However, with how Hybrid's hook system is set up, you could actually move these sections anywhere you want.

    Subsidiary is definitely going in as a default section because widgets in the footer are clearly wanted according to the survey results:
    http://themehybrid.com/archives/2009/01/theme-survey-results-part-1

    Removing widget sections

    With the advent of the Widget Logic plugin and others like it, I don't see much point in having Primary Home, Primary Single, Primary Page, and so on. See plugin:
    http://wordpress.org/extend/plugins/widget-logic

    Plus, many people just default to the home sections. I also think the WP team is revamping the widgets page in the dashboard to be more like the plugin.

    What would you think about removing those and building the Widget Logic plugin into the theme?

  2. A little less well known is "Tertiary," which comes after Secondary (primary, secondary, tertiary...):
    http://www.askoxford.com/asktheexperts/faq/aboutwords/primary

  3. Having just finished the text widgets with Exec-PHP and Widget Logic calls on http://savvyhealthfitness.com/ (which has a very similar front_page layout to your magazine style image), I am now in a better position to offer my comments on the above.

    In regards to the naming conventions I would opt for something simple along the lines of Header or Top, Top Feature and Bottom Feature (depending upon what you see as their main usage) for above and below the content, and Primary, Secondary and Tertiary in the sidebar area.

    I would certainly support removing the extra widget sections as I have never needed to use them, even previously when I was using Structure for my websites. Personally I found them a bit of a distraction, especially when I added an extra widget section and everything moved up or down one place. Plus now, with Widget Logic you have much more control over where your widgets will show and not show.

  4. Thanks for the feedback.

    I actually know very few people that use the widget sections that I want to remove. I recommend Widget Logic enough that I just about got everyone around here using it.

    I'm thinking of adding two other widget sections as well — After Single and After Page (would come after the post/page but before the comments section).

  5. After single would be handy as I like to add a small 'box' with an "email this post' 'print this post' and 'PDF' icons for users - similar to Joomla options.

  6. Maybe Before Comments instead of after single or after page, since those two are hooks.
    I agree with the Top and Header or Header Right, even though that Top (before content) will totally break my child theme I'm working on at the moment, if someone puts a widget in it.
    Tertiary I'm not thrilled with, maybe outside, with secondary as inside?

    I never use the other widget sections either. Just the home ones. I know they were confusing when I first saw them in Structure, so I support removing them also.

  7. "Before Comments" implies that there will be a comments section but is a pretty solid name. "After Single" and "After Page" make more sense, at least to me, because they are connected to the existing hooks in the theme. I think consistency would help keep any confusion down.

    I'm not thrilled with Tertiary either. But, "outside" implies that something is on the outside when it could easily be somewhere else. Switching two lines of CSS would switch the position of Secondary and Tertiary.

    One thing I'm trying to do is to keep everything semantically correct. Outside, inside, top, bottom, left, right, and other names such as these imply that something is positioned in a certain way. I tend to lean toward "before" and "after" if I can come up with no better name because elements have to literally come before or after other elements in the source code. I'm not satisfied with before and after either though.

    even though that Top (before content) will totally break my child theme I'm working on at the moment, if someone puts a widget in it.

    I'm hoping that this is the last major change to the widget system for a while. I hate to make such a drastic change in the theme, but it would be better to do it early in the theme's life rather than later.

    I never use the other widget sections either. Just the home ones. I know they were confusing when I first saw them in Structure, so I support removing them also.

    That's good to know. I've always felt they were kind of messy and in the way.

  8. Another neat thing coming to widget sections is a sort of "future proofing." For example, if you add/remove an entire widget section now, it displaces widgets. What I'm up late working on tonight is making sure your widgets stay in the correct widget section.

  9. What I'm up late working on tonight is making sure your widgets stay in the correct widget section.

    Now that will be nice! Just today when I switched themes I had to go through every section to find where my widget ended up.

    Just for the record, I miss the Recent posts widget and the Video widget, like in Options. ;o)

  10. I'm not sure how well that'll happen between themes other than Hybrid child themes, but I'll test it out. Basically, what I've done is give Hybrid widget sections specific IDs by name instead of number (like most themes).

  11. I would like to second PegasusTeam on the Recent Posts widget - I know that you said it was not likely to re-appear in Hybrid, but what about as a plugin? The existing Archve widget doesn't have anywhere near the flexibility or customizability (is that a word) of the old Recent Posts widgets with images.

  12. I won't be putting together the Recent Posts widget as a plugin in the form of what we had with Options and Structure.

    However...

    I do have plans for releasing a Query Posts widget in the future though, which will be much more advanced than anything we've seen yet in a widget. It will take advantage of the query_posts() function in WP, which has a ton of options you can set. So, putting it together is taking a lot of time.

    It'll be a widget/plugin I release on my blog (non-specific to themes). I'll probably add in a check for get_the_image() to make it compatible with thumbnails.

    When I say it's taking me a while to code, I truly mean it. Just take a look at the documented parameters for query_posts() and you'll have an idea of what I'm talking about:
    http://codex.wordpress.org/Template_Tags/query_posts#Parameters

    You could essentially have a theme that is entirely widgetized using this one widget.

  13. That sounds like quite an expansive widget/plugin with all the parameters available, I can see why it would take a while to code.

    Will it have the capability to give each instance it's own ID, or will it be generated automatically? Plus J Mehmett adapted your Recent Posts widget slightly for me so that I could input how many posts to show with a thumbnail/image and how many to show as a list below, eg. say 1 post with image followed by say 4 posts as a list, or 5 posts all with image and etc. - would that capability be available in your proposed widget/plugin?

    As you say with this much flexibility you could almost widgetize a theme completely. I must get back to the new Hybrid release now! I assume that your final widget area naming conventions are as per http://themehybrid.com/support/topic/upcoming-widget-sections-in-hybrid-04.

  14. I have an alpha version available if you want to test it out:
    http://justintadlock.com/downloads/query-posts.zip

    I'll probably be putting out a beta in a few days for the general public to test.

    Will it have the capability to give each instance it's own ID, or will it be generated automatically?

    This is something a theme does, not widgets.

    Plus J Mehmett adapted your Recent Posts widget slightly for me so that I could input how many posts to show with a thumbnail/image and how many to show as a list below, eg. say 1 post with image followed by say 4 posts as a list, or 5 posts all with image and etc. - would that capability be available in your proposed widget/plugin?

    No, this won't be going into the plugin. There's not really room to add it. Those kinds of things are more for custom work.

  15. That's just a cool plugin Justin.

    Especially for a php dummy like myself. All one need to know then is a little css to style the widgetareas to correspond with the existing ones. :-)

  16. Wow! That's one comprehensive plugin - looks like you almost need a licence to drive it!

    So far it works great with no apparent problems as yet - tons of combinations and uses! One thing, if I want to use it in the sidebar, is there a way to exclude the byline and post meta data?

Reply

You must log in to post.

Topic Info

Topic Tags: