[theme-reviewers] Are there any shortcodes appropriate to include with a theme?

[Justin Tadlock]

And, here's the plugin I created for this very purpose:
http://wordpress.org/extend/plugins/grid-columns/

You can even roll your own styles for it.  Just dequeue the plugin 
styles and enqueue your own if you have a special grid you want to set up.

On 3/16/2013 6:40 PM, Chip Bennett wrote:
> Why not just release it as a Plugin, and let any user of any Theme 
> make use of such handy shortcodes?
>
>
> On Sat, Mar 16, 2013 at 7:35 PM, Josh Pollock <jpollock412 at gmail.com 
> <mailto:jpollock412 at gmail.com>> wrote:
>
>     So one of the reasons I haven't submitted a theme I'm working on
>     is it has shortcodes that allow for creating responsive columns in
>     the post editor. For instance: [one third]content[/one third] puts
>     that content in a 4 column wide div, as the theme uses a 12 column
>     grid. I agree this type of shortcode shouldn't be
>     allowed, because when the user switches themes they'd be left with
>     all those random shortcodes showing up as plain text.
>
>     But what if I included a function in my theme that was hooked to
>     switch_theme that did made WordPress to a mySQL query that
>     replaced the opening shortcode with <p> and the closing shortcode
>     with </p>.
>     That could be done with something like UPDATE wp_posts SET
>     post_content = REPLACE ( post_content, '[one third]', '<p>' );
>
>     Hypothetically if I figured out how to get WordPress to do the
>     mySQL the right way, would this scheme make this type of shortcode
>     that is designed to be used in the post editor acceptable?
>
>
>     On Sat, Mar 16, 2013 at 2:57 PM, Chip Bennett
>     <chip at chipbennett.net <mailto:chip at chipbennett.net>> wrote:
>
>         The determining factor is: where are the shortcodes intended
>         to be used.
>
>         If the shortcodes are intended to be used in the post content,
>         then they are not allowed.
>
>         If the shortcodes are intended to be used in other places in
>         the template (footer, sidebar, etc.) then they are acceptable.
>
>
>         On Sat, Mar 16, 2013 at 2:51 PM, Bruce Wampler
>         <weavertheme at gmail.com <mailto:weavertheme at gmail.com>> wrote:
>
>             I'm working on a new theme, and would like to clear up
>             what might or might not be acceptable for shortocodes.
>
>             I know that shortcode are really discouraged because at
>             the least they will leave undefined [theme_shortcode] text
>             if the theme is switched.
>
>             But I also got the impression there is room for some theme
>             specific shortcodes. Where is the line? Some specific
>             examples I am struggling with (just using generic 'theme'
>             as a name):
>
>             [theme_info] - shows diagnostic information about the
>             theme - this would seem ok as it serves a possibly useful
>             diagnostic function very theme specific.
>
>             [theme_show/hide_if_mobile] - Show or hide content
>             depending on desktop/mobile view. Many users want this
>             capability, and it seems really related to how the theme
>             works on mobile views. It could be done with @media and
>             settings for transition points, I suppose, but it really
>             seems the theme is in control of those decisions.
>
>             [theme_show_posts options='xxx'] - Show some posts on a
>             page or sidebar. This capability is also very popular with
>             users. To function correctly, it really need to know how a
>             theme formats posts, so separating it from the theme would
>             lead to showing content that doesn't match the rest of the
>             theme. (Same logic could apply to RSS feeds)
>
>             [theme_menu] - display menus in alternate locations in
>             format that matches standard theme menu.
>
>             -----
>             I'm especially having difficulties imagining how to write
>             a plugin version of a [theme_show_posts] shortcode that
>             could work across themes and provide any kind styling
>             consistent with the theme.
>
>             So I'm curious if any of the higher ups here have an
>             opinion on what kind of shortcode would be acceptable to
>             include with new themes.
>
>             Bruce Wampler
>
>
>
>
>
>             _______________________________________________
>             theme-reviewers mailing list
>             theme-reviewers at lists.wordpress.org
>             <mailto:theme-reviewers at lists.wordpress.org>
>             http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>
>
>
>         _______________________________________________
>         theme-reviewers mailing list
>         theme-reviewers at lists.wordpress.org
>         <mailto:theme-reviewers at lists.wordpress.org>
>         http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>
>
>
>     _______________________________________________
>     theme-reviewers mailing list
>     theme-reviewers at lists.wordpress.org
>     <mailto:theme-reviewers at lists.wordpress.org>
>     http://lists.wordpress.org/mailman/listinfo/theme-reviewers
>
>
>
>
> _______________________________________________
> theme-reviewers mailing list
> theme-reviewers at lists.wordpress.org
> http://lists.wordpress.org/mailman/listinfo/theme-reviewers

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20130316/a87df26f/attachment-0001.htm>