Make WordPress Core

Tagged: featured content Toggle Comment Threads | Keyboard Shortcuts

  • Scott Taylor 4:06 pm on November 12, 2013 Permalink
    Tags: featured content   

    Featured Content: Epilogue 

    If you’ve been following along with 3.8/Twenty Fourteen development, you probably know that Featured Content is being handled by the theme now. It is being moved to the Customizer. This approach is wildly different that what I was doing in the plugin, and I am ok with that. Their approach is lighter weight and might be all a theme needs to display a section of featured posts.

    My original idea after @obenland approached me to work on it was way more complex, and it was something  that might not belong in core. Or it might, but the plugin didn’t make a compelling case – once again, no biggie.

    What did we learn from this?
    Having multiple active developers is a must. 15 people had commit, and our meetings had a healthy share of lurkers, but we only had one person doing development. I became the bottleneck for everything, which was enjoyed by no one.

    I like the idea of using plugin development to drive feature development. For plugins to be successful projects, I think the teams working on them need to be staffed properly. I think our team went into like “oh cool, we’ll all kinda work on it and then it will happen” – wasn’t the case. We could have benefited from more planning and tasking.

    The Future
    If anyone would like to continue working on the plugin, please do. I would prefer to focus on core development instead.

    • Lance Willett 5:26 pm on November 12, 2013 Permalink | Log in to Reply

      I look forward to seeing this come back in a future “features-as-plugins” sprint.

      • @ubernaut 5:50 pm on November 12, 2013 Permalink | Log in to Reply

        agreed think that it’s a crucial feature for any content driven site and every theme seems to have it’s own solution, would be good i think to have something more universal.

    • Manny Fleurmond 2:13 pm on November 15, 2013 Permalink | Log in to Reply

      Wouldn’t it have made sense to use widgets to do this?

      • shaunandrews 2:19 pm on November 15, 2013 Permalink | Log in to Reply

        I think so, but all I can think about these days is widgets. I think a “Featured Content” widget would have (and still does) make a lot of sense.

  • Scott Taylor 8:47 pm on October 4, 2013 Permalink
    Tags: featured content   

    Featured Content, 10/4 Update 

    I finally put a bunch of work into the coding of the plugin, and I think it is fairly robust at this point. Whether it makes it into core ( or whether it even should) is up for discussion, but I would like to share what I have.

    First, check out the latest code in trunk here: https://plugins.svn.wordpress.org/wp-featured-content/trunk/

    To guide development, I made the following list of requirements. It should also be easier for people to follow along when we can all agree on an initial set of facts:


    Wherever possible, existing WP functionality and screens will be used. The user should be able to associate posts with Featured Content theme areas as easy as selecting a category or making a post sticky, but, to be more robust, the user should be able to override certain features of a post when it is displayed as a Featured Item in a theme. Example: different title when featured vs what is displayed for a the full post, different image when in a featured module vs the featured image for the post when displayed in single.php.

    Post Type / Taxonomy

    1. A Featured Item uses the featured_item post type
    2. A featured_item belongs to a Featured Area
    3. Each Featured Area is a term in the featured_area taxonomy
    4. Post types can opt in to featured content by adding featured_area taxonomy support
    5. Themes can opt-in by supporting  ‘featured-content’  (the plugin currently brute-forces it)

    Creating / Deleting

    1. Add a post with featured area(s), make sure featured item(s) are created
    2. Trash the post, delete permanently, make sure featured item(s) are deleted
    3. Featured item should not have a title when created, it should inherit from the parent post when empty – view in list tables to verify
    4. If a featured item’s title is edited, it should show that in the list table, unless it is empty
    5. Add a post with a featured area, item is created. Edit post to belong to a featured area, 2nd featured item should be created.
    6. Delete one of the featured items, the other should remain, the post should be linked to only one featured area.

    Transitioning Post Status

    1. Add a post in draft status, make sure featured item is in draft status
    2. Move a post in draft to publish, make sure featured item is moved as well
    3. If a post was created with 2 featured items and one is trashed: if the term is re-linked to the post, the item in the trash should be untrashed, instead of creating a 3rd item

    Trash / Untrash

    1. Trash a post, make sure the featured item(s) are deleted
    2. Untrash a post, make sure the featured item(s) are not created
    3. Trash an existing featured item, make sure post loses tax association
    4. Untrash an existing featured item, make sure post regains tax association
    5. Permanently delete existing featured item, make sure post loses tax association

    Quick Edit

    1. The Taxonomy box for featured items should be present in Quick Edit
    2. All saving logic should fire in AJAX save routine for Quick Edit


    1. All featured items should be re-orderable via the Re-order items screen
    2. menu_order should be set when items are reordered, only those that change should be sent
    3. When new items are added to a featured area, they should be appended to the end of the list, not the beginning

    Returning Data

    1. By default, featured item contains the post data of the post it belongs to
    2. If any fields have been overridden(post_title, post_excerpt), the post data is a merge of the 2
    3. If the featured item has a featured image, the theme can override by using the property ‘image_id’ to grab the featured image on one of the decorated $posts that is returned when applicable

    Yeah, so that is a mouthful. All of these use-cases are listed in the comments at the top of the plugin file as well. There’s been a lot of discussion about new UI. If someone wants to think way outside of the box and introduce new screens, keep the above in mind.

    • Sam Sidler 7:27 pm on October 8, 2013 Permalink | Log in to Reply

      Be sure to tag your posts here with “Feature Content” so those following the tags can keep an eye on your progress. 🙂

    • Robert Dall 4:39 pm on October 10, 2013 Permalink | Log in to Reply

      Ok Thanks Scott… I will review all of your notes and then rework them in to the UI mockups I have done. When will be the next meeting. So I know to be fully prepared for it…

    • EkoJr 2:21 am on October 11, 2013 Permalink | Log in to Reply

      Thanks for posting this. It really helped fill in some gaps on how to operate it. I’ve been taking a look at Featured Content to see how it works, but tonight I’m going to try and take a deeper look into the code before I start posting questions. Lately, I’ve been working on my own plugin (Advanced Post List) as well.

      However, when I first booted up FC, I started thinking about the practicality, and how it might be overlapped by a theme or plugin. By default, I would have one featured area already setup and ready to go for the user/admin to use. Maybe even give it a similar feel like the Featured Image in WP. Just a couple ideas right off hand, but the Featured Area tab for other post types is laid out nice. The Featured Items menu I imagine still has some work.

      Btw Robert, do you have a repository setup? I wanted to check yours out too.

    • redundans 10:57 am on October 11, 2013 Permalink | Log in to Reply

      Hi Scott, will there be a meeting this monday? We are som devs from sweden that taken big interest in this project (basically because we have a similar plugin that we need to rework https://wordpress.org/plugins/cursorial/). We would really like to help out one way or another.

    • Scott Taylor 7:07 pm on October 11, 2013 Permalink | Log in to Reply


  • Scott Taylor 7:38 pm on September 24, 2013 Permalink
    Tags: , featured content   

    Featured Content Update 

    Sorry for no meeting this week, it’s been busy at my j.o.b. In addition to the weekly IRC meeting, we now have a Skype conversation going. Add me as a contact on Skype if you want to join in. My Skype username and Trac username are the same.

    The plugin is in the repo:

    Last week, I made a screen to sort featured items within their respective areas. The logic to save the order when sorting still needs to be hashed out.

    Currently, one person is doing the coding (me). This is not ideal, and I could use help. There have been a bunch of mockups, but I don’t currently have time to build a prototype for all of them. If would like to help with coding, please let me know in the comments.

    • notaternet 8:35 pm on September 24, 2013 Permalink | Log in to Reply

      Hello, I would love to help with the coding.
      I have just added you to skype.

    • Robert Dall 8:58 pm on September 24, 2013 Permalink | Log in to Reply

      I am working on the UI today… Regardless of my work scheduled…

    • Robert Dall 1:41 am on September 25, 2013 Permalink | Log in to Reply

      The Feature Content Mockups


      My proposed UI for the Featured content is based on the fact that we have already set a lot of the variables up in the content. We already have a field for: The Content, The Excerpt and the Featured Image all in the post editor. So using this to our advantage we only need to tell the featured content what why want in the plugin.

      What Twenty Fourteen did was to call a featured image, the except, categories and put all of that on the front page. This was a great for this one theme. But what if we wanted the full content or only the title and the excerpt?

      First we need to create a featured content area. This can be done in the featured content main screen (also available in the drop down from the main menu on the left)

      Then we need to tell WordPress which posts it will be part of. We can one of two ways.

      1. We hit the Feature this content check mark box in the post editor window and that then shows a drop down of all featured content area’s available. (Which was suggested by Tammie Lister) We should also have the ability much like the tags and the categories to create a new featured content block from with in the post editor.
      — But this could be problemattic if we want to add multiple posts to a featured content area that have already been created.

      2. We can also select the featured content in bulk from the edit posts screen using the bulk actions. We could then assign which posts or pages we want added to the post format. ( I still need some feedback or am fuzzy on how this would actually work but we should have the ability to bulk add / remove from the edit post screen imho. )

      Ok now we can decide what to call in the featured content area. I have learnt that WordPress development is more about Design Decisions rather then Design Choices but to create different featured content we need to give those choices to the user.

      In this example we have the Bread Feature Content. Which we can then choose what featured content we want via check boxes. (I am still looking for a better word then everything)

      • If people wanted to add only a title and the featured image that is available to them. If they want the title and the content area also available.

      • I haven’t added tags and categories because those don’t exsist for pages in my example. But they could easly be shown for posts.

      • If we want add a description like we do for categories / tags that would be an easy add on.

      • Like the WordPress menus / widgets we just drag and drop what post we want in what order.

      • A short code would then be created and put into any page or post you desired (Although I am not sold on the short code solution I don’t know how we would implement different featured content blocks)

    • Scott Taylor 5:05 pm on September 25, 2013 Permalink | Log in to Reply

      Your mockup completely ignores the overrides, which we have discussed ad nauseum, and was in the first iteration of the plugin.

      • Robert Dall 5:51 pm on September 25, 2013 Permalink | Log in to Reply

        Hi Scott

        A little confusion on my part here. In the last meeting you told us to download the latest version of the plugin and install it and get familiar with it. I did that. There is no reference to the overrides that you spoke of already in the plugin. I made some mockups on integration of how I though the latest version of plugin would integrate best into the WordPress core.

        I also couldn’t find reference to the word overrides in the #WordPress-core-plugins or the channel.

      • Robert Dall 6:23 pm on September 25, 2013 Permalink | Log in to Reply

        I wasn’t able to accomplish the interaction of the “overrides” you speak of in the plugin.

        All I get is:

        This is meta box to display fields, etc about the featured post that does exist.

        I can edit my mockups… But with out seeing this functionally it would be a guess on my part as to how it operates…

    • OpenSource Technologies 10:04 am on October 15, 2013 Permalink | Log in to Reply

      When we the next Skype meeting and how to join that?

  • Scott Taylor 4:48 pm on August 19, 2013 Permalink
    Tags: , featured content   

    Featured Content: Getting Started 

    Ahead of our first official office hours, here is an overview of what I would like to discuss:

    What is Featured Content?

    Obenland discussed the high-level concept here: https://gist.github.com/obenland/3010432c8edcfcbf95a9

    To me, Featured Content is a flexible way to show one or many posts in one or many places in your theme. A blog might have 1 featured post area that will support 1-4 posts, as an example. A more complex site using WP as a CMS might program its homepage using many “featured areas” that contain varying numbers of post-like entities.

    Featured Content, in the end, is just a way to return posts chosen by a content producer. The way in which featured content is selected should be intuitive, easy to manage, and use existing WP technology/terminology whenever possible. A featured post-like thing should an entity that points at a canonical post, while having the ability to override any of the parent post’s attributes on display. Example: I should be able to use a different title and image for a post that is featured when it is rendered in a featured area.

    I should also be able to schedule featured items, much like I can schedule a post.

    How are we going to implement it?

    Here are my ideas:

    I think we can get a lot of immediate mileage using a custom taxonomy, working name: “Featured Area” and a custom post type, working name: “Featured Item”. By default, a function like `wp_get_featured_content()` can return all featured posts. Passing a parameter can return posts matching that featured area slug that are published – `wp_get_featured_content( ‘mini-header’ )`. A custom taxonomy can be registered to post and featured_item. Themes can register the taxonomy for more post_types as necessary.

    The plugin, in its current form, implements all of the above: https://wordpress.org/plugins/wp-featured-content/

    Things to consider:

    • How do we always keep the post and its featured_item brethren in sync?
    • Do featured_items and posts always share the same post_status? Should they be independent?
    • How do themes opt in to multiple featured areas if the terms have not be created for the featured_area taxonomy?
    • What are alternate ways to implement the above?
    • George Stephanis 4:56 pm on August 19, 2013 Permalink | Log in to Reply

      This may be a bit out of scope, but I would like to also consider a wp_get_featured_content( array( 'post_id' => 123 ) ) contrasted with that may wp_get_featured_content( array( 'location' => 'mini-header' ) ) — that could be used to fetch related posts or the like?

      Just have it accept an $args array, rather than a string, so it’s more extensible for plugins to offer new ways to use.

    • shaunandrews 4:59 pm on August 19, 2013 Permalink | Log in to Reply

      I haven’t been following to closely, so please excuse my ignorance, but what if featured content was just a widget (or content block) that you could place into any sidebar area, post, or page?

      A blog might have 1 featured post area that will support 1-4 posts, as an example. A more complex site using WP as a CMS might program its homepage using many “featured areas” that contain varying numbers of post-like entities.

      This sounds very similar to widgets and sidebars…

      With the rethinking of widgets and post-formats-as-blocks, there’s been chatter about combining the two concepts. Widgets would become content blocks, which could then be dropped into a post, page, or widget area. There could be a “featured content” block (né widget) that allows you to pick posts to feature. You could place this block into a “content area” (né “widget area”), post, or page.

      • paaljoachim 9:08 pm on August 24, 2013 Permalink | Log in to Reply

        + 1. Creating consistency is very important. I would suggest merging Featured Content into CEUX. As featured content would be a natural content block one of many that can be added into CEUX. As Content Blocks gets going more and more blocks will naturally also be added.

        Featured Content to me would be like using the short code that I am using through the themify.me shortcode panel. A panel for which categories to show, how many posts to display, order, list/thumb/4-grid/etc. Below is a screenshot from the Themify Page Builder:

        What other good options exist today can we learn from?
        Any good plugins to show features categories/content?

    • Manuel Schmalstieg 5:01 pm on August 19, 2013 Permalink | Log in to Reply

      Here are my 2 cents, from my experience implementing custom themes for various clients. A “featured post” functionality is something i’m using all the time. What I use for that is generally a custom Taxonomy, which holds all the “display settings” that are needed for a site.

      Using a regular Category is generally bad, because it blurs the role of the “visible categories” (visible on the frontend, and in URLs), which for clarity shouldn’t be mixed with “settings” categories, of which the “featured item” is a perfect example. So a custom “Settings” taxonomy is what I consider the cleanest and most logical way.

      Using a Custom Post Type is a bad idea, in my experience, as you cannot easily switch a regular post into another CPT. Imagine that you wrote a post with title, content, image attachments, categories and tags – then you decide this should be a featured item. You would have to copy everything over to the “Custom Post Type”. Bad user experience…

      @ Shaun Andrews: indeed, if we had a “Archive of any Taxonomy widget”, we could use a widget area, and define “last X posts of with Taxonomy:Display Settings and Term:Featured Item…

      • Chip Bennett 5:15 pm on August 19, 2013 Permalink | Log in to Reply

        I think combining custom post meta data with a new “Featured Content” taxonomy is all that’s needed here, and would be quite powerful. The post meta data designates the post as “featured”, and the taxonomy associates the post with other related posts, allowing for multiple groupings of “featured” content. WP_Query calls (with appropriate post meta and taxonomy parameters) in the template handle the rest.

    • Chip Bennett 5:02 pm on August 19, 2013 Permalink | Log in to Reply

      I think creating a CPT is probably too heavy for “featured” content. The status of being “featured” is independent of content type, and as such would be better suited either as a custom taxonomy – or, perhaps better yet: as custom post meta data.

      Using custom post meta data allows any content type – posts, pages, or any custom post types – to be designated as “featured”, and to be queried/displayed accordingly.

      • Manuel Schmalstieg 5:04 pm on August 19, 2013 Permalink | Log in to Reply

        Using custom post meta data allows any content type – posts, pages, or any custom post types – to be designated as “featured”, and to be queried/displayed accordingly.

        Full agreement, as per my comment above.

      • Rohit Tripathi 5:46 pm on August 19, 2013 Permalink | Log in to Reply

        I totally Agree. Using CPT is not feasible at all. Custom post meta data does make a lot of sense. That would be the right way to proceed.

    • Chip Bennett 5:08 pm on August 19, 2013 Permalink | Log in to Reply

      Pet peeve alert:

      …A more complex site using WP as a CMS…

      WordPress is a CMS, and is always used “as a CMS”.

      Pet peeve/rant aside: The front-page.php template file has been around for a long time now, meaning that it is simple for any Theme to designate a custom site front page template. The normal use-case for such a template is “featured” content, so I’m all in favor of standardizing on how content is designated as “featured”.

    • Jonathan Desrosiers 5:19 pm on August 19, 2013 Permalink | Log in to Reply

      I created a quick solution for this (https://wordpress.org/plugins/post-type-spotlight/) because it comes up frequently on our projects. Our plugin adds a check box for content editors to designate something as featured.

      I like the placement, and I think that could work well with the scheduling aspect of featuring, because it could function similar to the Publish & Visibility fields.

      Would there be any disadvantages to assigning it to a specific featured area? Instead of using an area, it could be simply featured, or not featured, and wp_get_featured_content() could accept other parameters, such as which categories/custom taxonomy terms it should also have, or what publish dates, etc..

    • Weston Ruter 5:41 pm on August 19, 2013 Permalink | Log in to Reply

      It seems a key feature to include with these featured content areas is the ordering of posts within them. Consider a news site that has homepage sections for different news categories (Local, National, Sports, Entertainment, etc). Editors need to have control over the ordering of the posts that appear in these featured content areas. Hacking the publish date to ensure proper ordering is not an option, as the same post may appear in a different order in other featured content areas.

      • Chip Bennett 5:43 pm on August 19, 2013 Permalink | Log in to Reply

        That can be custom post meta data, also: “Featured Content Sort Order”

        • Fab1en 7:19 am on August 20, 2013 Permalink | Log in to Reply

          No: the custom post meta data can only be present once : it is not linked to the area. What if my post must appear first in Local category and second in Sports one ?

      • Manuel Schmalstieg 12:44 pm on August 20, 2013 Permalink | Log in to Reply

        Oh, if we could come up with a good solution for “custom-ordering” things, that would be amazing (and would be useful beyond the scope of featured content)! If we would apply the taxonomy logic to featured content, could we imagine that we give to some taxonomies “support for custom-ordering”? And provide a new interface, where the content of each taxonomy term could be ordered by drag-and-drop?

        My typical use case would be: a “Series of posts” or “Related content” custom taxonomy, which gets used by the theme to display “other articles in this series”. Each term then becomes a group of related content (or “featured content”). If that term/group could be ordered, it would be CMS heaven…

    • Chris Olbekson 5:47 pm on August 19, 2013 Permalink | Log in to Reply

      Sorting by postmeta requires a meta_query and I think we can all agree that this is not ideal. I think the term_order column would be great here. See my comments on https://core.trac.wordpress.org/ticket/9547#comment:26

      • Chip Bennett 5:59 pm on August 19, 2013 Permalink | Log in to Reply

        I don’t think there’s anything inherently “not ideal” about using a meta_query, but I certainly agree that term_order would be a better solution all around.

        • Scott Taylor 6:13 pm on August 19, 2013 Permalink | Log in to Reply

          meta_query falls apart at scale

          • Chip Bennett 6:17 pm on August 19, 2013 Permalink | Log in to Reply

            How much scale is needed for “featured” content? Having even 10 “featured” posts would probably be near the edge case.

            As for scale: if I’m understanding the concept properly, the idea is to mimic custom nav menus, and have a CPT that identifies an existing post/page/whatever, so there will be a one-to-one relationship between “featured” CPT and existing content. The CPT is queried, and then each associated post must then be queried from within that query, in order to display post data?

            That seems like a far bigger scale/performance issue than using post meta.

            Alternately: users will have literally have to duplicate content in order to designate a post/page/whatever as “featured” – and I would hope that idea is a non-starter?

            • Zack Tollman 6:19 pm on August 19, 2013 Permalink

              Alternately: users will have literally have to duplicate content in order to designate a post/page/whatever as “featured” – and I would hope that idea is a non-starter?

              I think a better term than “duplicate” is “fork”. It copies the content to the post featured content type. It can then be changed without ever re-syncing the content.

            • Scott Taylor 6:22 pm on August 19, 2013 Permalink

              There is no duped content – the featured_item has the post as post_parent/foreign id. That’s normalized. The only content that is even populated is overrides. “Featured” is really content that is “designated” to an area. The use-case is more for programming a homepage, or ad areas. That won’t be the default use case. But if all we care about is a flag, why not stay with stickies or a category?

            • Chip Bennett 6:29 pm on August 19, 2013 Permalink

              I’m guessing that the most common use-cases will be front-page sliders, and single-post/page feature boxes.

              In any case, the biggest win here is standardizing the method of designating content as “featured”, so that such designation is portable among Themes. Using “stickies” is common, and works, but is limited. Having an actual “featured content” taxonomy would allow for far more flexibility, while retaining standard conventions.

          • Chip Bennett 6:26 pm on August 19, 2013 Permalink | Log in to Reply

            Looking at the referenced Plugin, running two queries is exactly what’s being done:

            $args = array(
            	'fields' => 'id=>parent',
            	'post_type' => WP_Featured_Content::POST_TYPE,
            	'orderby' => 'menu_order'
            if ( ! empty( $term->term_taxonomy_id ) ) {
            	$args['tax_query'] = array(
            			'taxonomy' => $term->taxonomy,
            			'field' => 'term_taxonomy_id',
            			'terms' => $term->term_taxonomy_id
            $query = new WP_Query( $args );
            if ( empty( $query->posts ) )
            	return array();
            return get_posts( array( 
            	'post__in' => wp_list_pluck( $query->posts, 'post_parent' ), 
            	'post_type' => 'any',
            	'orderby' => 'post__in'
            ) );

            The contention is that this is faster/more scalable than a single meta_query?

    • swissspidy 5:51 pm on August 19, 2013 Permalink | Log in to Reply

      Just as Helen noted on Trac, querying for post metadata would be too slow: https://core.trac.wordpress.org/ticket/24857#comment:17

      I think CPT + taxonomy is fine and allows for better flexibility e.g. (multiple) custom featured items for a post.

      • Scott Taylor 5:54 pm on August 19, 2013 Permalink | Log in to Reply

        that’s the main point – a post should be able to be featured in multiple featured areas, with different display data in each, like a different title/image per area

      • Chip Bennett 5:58 pm on August 19, 2013 Permalink | Log in to Reply

        Using a CPT means that one bit of content must be both its original content type (e.g. “post”), and also a second content type (e.g. “featured”). That means that content is inherently duplicated. I don’t get how that is in any way ideal.

        • Helen Hou-Sandi 6:01 pm on August 19, 2013 Permalink | Log in to Reply

          Given that this is exactly how nav menus work (CPT + taxonomy), this seems like a non-argument.

          • Chip Bennett 6:04 pm on August 19, 2013 Permalink | Log in to Reply

            Except that nav menus aren’t a separate type of content; they are a link to content. Featured content is actual content, that already exists as an appropriate content type. “Featured” is merely a designation that describes that content, and correlates that content to other content. Thus, post meta and/or taxonomy is the correctly analogous data type.

        • Zack Tollman 6:17 pm on August 19, 2013 Permalink | Log in to Reply

          I think that the “duplication” is a good thing. Once the content is “featured”, it becomes a different type of content. It then takes on different properties. It is reasonable to think that when content is featured, it takes on a different title, featured image, post content, etc. “Forking” this from the original post makes sense in that we can use the CPT API to manage all of that content. Moving this content into post meta fundamentally changes how we would work with the pieces of content associated with a post. For instance, if we change a title of a post when it is featured and save it as post meta, do we run the “get_the_title” filter on it when retrieving it? I think it makes sense to use the API that is developed for the purpose of interacting with post content and using a new CPT for this purpose makes sense.

          • @ubernaut 3:41 pm on August 20, 2013 Permalink | Log in to Reply

            i think the main issue here is that you end up with a bunch of old no longer featured CPTs and expiration feature for these would resolve that issue imo.

      • Chip Bennett 6:01 pm on August 19, 2013 Permalink | Log in to Reply

        Also, regarding query speed: improve the query if/where need be – and that speed discussion compares taxonomies to post meta, and does not address CPTs particularly.

    • Taylor Dewey 6:35 pm on August 19, 2013 Permalink | Log in to Reply

      Here is an initial round of mockups based almost entirely on a featured item solution that we built for Global News (http://vip.wordpress.com/2013/04/25/global-news-qa/). I took out some of the UI that was more specific to them.

      The architecture we build uses a CPT + CTT. Featured areas are a hierarchical taxonomy. Featured Items are a custom post type generally derived from, and linked to original content. Curating a featured item is done from a separate admin screen (I’d love to see a way to do this from the content itself, too). Each item is sortable within it’s featured area. Adding a new curated item is a three step process that takes place in a modal.


    • karmatosed 8:01 pm on August 19, 2013 Permalink | Log in to Reply

      I’ve gone with the easiest option for my first batch of sketch mockups. These show just a single checkbox option. I then explored some potential placing for an editor/allocator/collection (*needs funky name) interface.

      I will be back with a second round of wireframes but wanted to get these out as the easy end of things.

    • karmatosed 9:57 pm on August 19, 2013 Permalink | Log in to Reply

      I have explored some potential allocation screens. I don’t feel either are there yet but worth sharing the experiments.

      The first is the simplest. This can have a theme defined image to allow for users to at a glance understand what areas are featured. To the side are the featured areas and you click into each to see the posts assigned. I’m not sold we should move from the edit post screen assigning I explored earlier but allowing myself to explore.

      The second I like a bit better but still would like to see how more of this could be done in the post edit screen / single post (that’s going to be my next experiment). This has the ability to add or take away so we could even just strip back to the short code. This nods to your work @taylorde so thank you.

      Neither covers fully everything discussed but I’m still playing.

      • karmatosed 5:10 pm on August 20, 2013 Permalink | Log in to Reply

        Building on from the last wireframe, I have explored what collections could be like. This focuses on collections you then assign to content areas for featuring.

    • paaljoachim 9:09 am on August 20, 2013 Permalink | Log in to Reply

      What about adjusting the Create/edit Category to look similar to make a new page/post? To keep the consistency of the overall design method? This way the user can easily create a new category and create a design for it at the same time. I am using templates for the pages/posts/categories. Use an existing template and see the visual changes in the layout area. Modify and save as a new template to be used in other places.

      I do agree that creating a listing through a category page or regular page of specific posts within a specific category can also be done with a widget/element/content block.

    • karmatosed 10:57 am on August 20, 2013 Permalink | Log in to Reply

      I continued today and moved onto what would things look like if all done in the post edit screen. I’ve added in the ability to pick a featured image (or have it auto select one) and not just using the featured post image. This probably requires some thought about how but it’s something I know was mentioned in the chat so seeing where it could fit.

    • @ubernaut 3:36 pm on August 20, 2013 Permalink | Log in to Reply

      i put this on the trac ticket yesterday it very rough (some missing bits as well) but illustrates my idea of borrowing the menu ui:

    • karmatosed 4:56 pm on August 20, 2013 Permalink | Log in to Reply

      I had a look for another wireframe at what a box would look like on the single post edit screen. This is a simplified format.

    • Robert Dall 10:59 pm on August 20, 2013 Permalink | Log in to Reply

      One of the reason I wanted to part of this group was the ability to show a bunch of content together. What was once template and query based could now be done in the UI would be a great addition to WordPress.

      After reading most of the posts I have seen any reference to see if the user only wants to use a post excerpt as the featured content.

      Or if they wanted more of a Featured Image, Title, Excerpt. Read more link.

      What if they only want featured content that is only the titles of other posts?

      I have done this via wp_query and template for a number of websites and as it helped people who liked to click on both the header and for people who like to click on the drop down.

      See Annotated Screenshot:


      See actual page here: http://www.uprisingbreads.com/bread

      Or here is another page

      Couple Questions?

      • Is this the actually direction of this plugin or is it an iteration that is heading off in another direction?

      • Also the order of this content could it be controlled by the actual menu order? Or would have to create the “featured content” and then create the drop down menu of the same order?

      And if I have jumped the gun on these topics my apologies…

    • Scott Taylor 2:14 pm on August 21, 2013 Permalink | Log in to Reply

      We are in an exploratory phase. If something interesting pops up, we may move in a different direction.

    • Matt McLaughlin 4:06 pm on August 21, 2013 Permalink | Log in to Reply

      I have to say that I’m with @shaunandrews in thinking that this should not be a new high level UI concept but rather a canonical implementation of how to use Content Blocks/Widgets to achieve the same goals. The absolute last thing I want for my users is yet more UI concepts to confuse them. A grand unification of all the types of static and dynamic content blocks whether they appear on the front page, a post, page, or in a sidebar is just exactly what the doctor ordered.

      That said, I think there’s a lot that can be done in terms of simplifying the act of choosing and formatting content for highlighting using a really well thought out core Content Block for featured content.

      More musings here: http://mattnamclaughlin.wordpress.com/2013/08/21/featured-content-as-a-widget-or-content-block/

      • Taylor Dewey 6:52 pm on August 23, 2013 Permalink | Log in to Reply

        I agree. In fact, I’ve used my version of a featured item curator as a replacement for the menu system on one of these projects.

        However, it was significantly less flexible than the current implementation. And same with widgets. Making a UI that can manage all of those will require some serious work. However, I’d love to see a UI that can accomodate everything that we need to go this route in the future.

    • magicroundabout 8:21 am on August 29, 2013 Permalink | Log in to Reply

      Hi Everyone,

      I’ve been following some stuff on core but have not contributed before. This conversation caught my eye.

      There’s a couple of requirements that I have for this that hasn’t been mentioned yet:

      • you might want links to things other than single content items. Custom links to external resources, media items, archives of posts
      • different images have been suggested, but you might want to display a different title too. Some of my featured areas have limited space and you might need an alternative title to fit the space.
      • Sometimes these areas need to contain multimedia. So would it be possible to have an option to insert an oembed code?

      I definitely think a menus-like interface with defined areas and drag-and-drop organisation would work better than a meta-box on existing post types, or as a custom post type or taxonomy. For me that’s just not flexible enough. But the ability to be able to choose posts to go in a featured area remains a must.

      Hope that’s useful. I’ll keep an eye on the conversation and try to contribute if I can.


      Ross W

  • Konstantin Obenland 6:59 pm on August 16, 2013 Permalink
    Tags: , , featured content   

    Featured Content Office Hours 

    As my last task as acting lead for Featured Content, I’m happy to announce our first IRC chat on Monday, 1700 UTC in #wordpress-dev, led by @wonderboymusic.

    We will talk about the project organization and intended functionality for the plugin (on a high level!). Goal of the meeting is that everyone has a clear understanding of where the project is headed, what the next step in the process will be, and who is working on that.

compose new post
next post/next comment
previous post/previous comment
show/hide comments
go to top
go to login
show/hide help
shift + esc
Skip to toolbar