Subscribe to Our Newsletter

x

posts

Display one or more posts inside an .xml file.

<posts name="homepage_posts" format="posts_popular" source="frontpage" limit="10" section_url="entertainment" />

Variants

<posts_without_current />

It is used the same way as <posts>, but excludes the current post (on a post page). When using <posts_without_current> you must define the limit attribute (see below) with 1 more than you actually need.


Attributes

  • name - define the name of the section. Required for displaying unique posts using the <posts_without_current> tag.
  • format - defines the mustache template that will be used to render each post, relative to engine/mustache/roar/posts/ directory.Usage: create a new .html template file inside the above directory (ex: posts_most_read.html). Use <posts format="posts_most_read"> inside an .xml file to render this type of posts.
  • template - defines the mustache template that will be used to render each post, relative to engine/mustache/ directory.
  • source - post source used to fetch data from. (default is "frontpage"). It can take one of the following values:
    • frontpage - load posts for front page or any other subpage (section);
    • search_result - load posts that are result of some search;
    • tag - load posts for specified tag;
    • popular - load most popular (most read) posts for last 3 days;
    • related - load related posts (calculated by similar tags); if there's no related posts, then populate it with posts from the same section;
    • mentioned - load mentioned posts (if current post has any internal links, i.e. links to posts on the same domain, then this posts will be "mentioned" for current post).
  • limit - maximum number of posts to show in this block.
  • css_classes - add additional css classes for the posts wrapper.
  • section_url - name of the section used as source for posts.
    • If source="popular", you can specify more than one section separated by comma.
    • On article page you can use post's section as a base for displaying posts from the same section. Usage:
    • <posts_without_current format="posts-main" section_url="{{post.section}}" limit="4" />
  • no_posts_template - set a path to a jinja template that will be shown when no posts are found.
  • source_site - site used as source for posts. Use source_site="parent_site" on community pages so you can pull popular posts or posts from other sections with section_url="section-name".
  • section_template - define the template to be used for the posts wrapper (container). Default template located at: engine/community/roar/blocks/section.
  • source_unique - true OR false Posts among any source with this attribute are unique. For example if we have posts with ids [1,2,3] for frontpage source and posts with ids [3,4,5] for 'popular' source, 'popular' source excludes post 3 from its list and it becomes [4, 5].
  • tag_name - only relevant if source="tag". Name of the tag that will be used as source for posts (default to current tag on tag page).
  • exclude_section - way to omit posts (which are in certain section) when using popular source. Usage:
  • <posts format="popular-food" source="popular" exclude_section="fruits" />
  • filters - apply filters to posts. In order to minimize data transfer, your <posts> tag will not include all the data you may expect, such as author name or the section title this post belongs to. Use these filters to get more data about your post:
    • frontpage_tag - take the first tag from public_tags of the post and assign to 'frontpage_tag' key on the same post;
    • original_user_subsite - add author data to your post;
    • section - add section info on the post. If the post has multiple sections, the first not private section in the list will be returned. Usage:
    • <posts name="splash" format="splash_news" source="frontpage" filters="section" />
    • display_disclaimer - set the display_disclaimer attribute of the post to "True";
    • pretty_date - apply this function to this post. Usage:
    • <posts name="news2" format="news" source="frontpage" limit="4">  <filters>    <pretty_date field_name="created_ts" full_format="true" enable_future="false" date_format="%a, %d %b %Y %H:%M:%S +0000" new_field_name="created_ts_formatted"/>   </filters></posts>
      Now you should be able to use {{created_ts_formatted}} in your mustache template. Attributes of pretty_date:
      1. field_name required string - name of the field on the post for processing
      2. full_format optional boolean default - false.
      3. enable_future optional boolean default - false.
      4. date_format optional default - "%d %B %Y".
      5. new_field_name optional default - field_name. Name of the field on the post model where result of filter will be written. By default it will be written in the same field_name.
    • set_image_size - set the image_url context variable for desktop and/or mobile screen. Usage:
    • <posts name="popular" format="popular" source="popular" limit="1" section_url="popular">    <filters>        <set_image_size url="image528x304,image600x" mobile_url="imageWWWxHHH,image300x"  />    </filters></posts>

      You should now be able to include {{image_url}} in your mustache template

    • partial - override any partial used in your mustache template for post rendering. Example:

    • <posts name="news" format="news" source="frontpage" limit="6">    <partial name="roar/posts/partials/author/author" replace_with="custom/author"/></posts>

Applying filters

Set them in the filters attribute (if there are more than 1 filter to define, separate them with comma, no spaces allowed). Example:

<posts name="news" format="news" source="frontpage" limit="6" filters="frontpage_tag,display_disclaimer"/>

Set them in the <filters> child tag. Example:

<posts name="news" format="news" source="frontpage" limit="6">  <filters>    <frontpage_tag/>    <display_disclaimer/>  </filters></posts>

It is also acceptable to define filters both ways into a single <posts> tag. Example:

<posts name="news" format="news" source="frontpage" limit="6" filters="frontpage_tag">  <filters>    <display_disclaimer/>  </filters></posts>

Page Speed Is Crucial to Your Marketing Efforts

Most marketers don't prioritize page speed because they don't think it impacts their bottom line. However, page load has a direct impact on conversions and revenue.

Here's a very simple scenario, supported by industry data, to underscore why the way pages are built and powered is crucial for paid media initiatives and your overall business:

Let's say a paid media campaign drives 100,000 new visitors to a landing page that takes five seconds to load. Google says that 53% of mobile site visitors will leave a page that takes longer than three seconds to load. So of the 100K mobile site visitors you paid to bring to the page, ~50K are leaving immediately due to poor page performance alone.

Some studies even show that bounce rate increases approximately 100% for every two-second delay. So, if site load jumps to seven seconds, you'll pretty much lose all of the visitors your paid strategies brought in.

A Poor Site Experience Costs More Than You Realize

Page load plays a huge part in customer dissatisfaction, too. Continuing on with our previous example, let's classify the ~50K that didn't abandon the page as dissatisfied due to poor page performance. As HubSpot points out, 79% of them are less likely to buy again from the same website. That's ~40K visitors never coming back to the site due to poor page speed. The loss is even greater when you consider how valuable returning visitors are: They represent up to 48% of all transactions and spend almost 2x more than new visitors, according to Business Insider.

Plus, people love to spread the word about a bad experience, probably more than a good one. 40% of visitors who had a bad experience with a website's performance would tell a friend or a family member. So of your 50K dissatisfied visitors, 20K are talking negatively about your brand. If they tell only one person each, that's an opportunity cost of another 20K potential site visitors and customers.

The main takeaway? Your paid media has to work much, much harder when you neglect to optimize your site for performance.

Owned and Paid Media Should Work Together for Better Efficiency

And speaking of site improvements to help the bottom line, marketers can't overlook the value of owned content (e.g., articles, reviews, social feeds, etc.) and its impact on overall traffic and lead generation strategies. Sites tend to see significant lift in audience reach and conversion when content is paired with commerce: For e-commerce companies, content can account for up to 69% of total organic traffic. And, even more compelling, conversion rates have been 6x higher for companies that adopt content marketing.

RebelMouse's CMS makes it easy for brands to systematically optimize page speed performance and organic reach, which allows paid media to be more efficient.

RebelMouse allows clients to easily manage website layouts and components at any time, ensuring sites remain fast and are rewarded by Google and Facebook. Our platform features proprietary SEO tools designed to help clients optimize organic search with every post and better align paid and organic search strategies for increased efficiency. Similarly, our platform also includes proprietary social tools to organically build community and growth, and our data helps clients spot winning organic trends that can inform paid social media.

RebelMouse Is a Partner That Can Guide You

When it comes to content marketing, it's important to be mindful of the relationship between owned, earned, and paid media — it will only help your teams engage and convert more audiences into customers and brand loyalists. At RebelMouse, we're proud of how we work with brands and our ability to provide the expertise, best practices, and modern technology that help teams become better content marketers. If you're a brand marketer, feel free to reach out to us to learn how RebelMouse can help you be more strategic and effective in your content marketing efforts.

Related Articles

Target High-Value Users With Affinity Categories

Unlock valuable audience data and shape a new strategy

In today's landscape, quality content isn't enough — it's half the battle. Publishers need to produce shareable content backed by data to experience sustainable growth. At RebelMouse, we have a unique pageview methodology that provides an innovative user experience for every reader without sacrificing revenue and growth opportunities for publishers.

To do this, we track massive amounts of data across our platform through the use of custom-built Google Data Studio dashboards.

Click here to see the kind of growth our clients experience every day.

One of the best ways to discover more about your audience is by taking advantage of Affinity Categories. This feature breaks down audience demographics, including age, location, interests, and more. Affinity Categories are usually used to target audiences for ads, but we also use them to gain insights on what topics a site's visitors are interested in overall.

Normally, each category is listed out separately in Google Analytics. In the example shown above, our data experts split categories into separate levels to reveal different levels of audience depth. For instance, by splitting up the category News & Politics, we can better explore the detailed distribution of users interested in specific types of news:

  • News & Politics/Avid News Readers/Avid Political News Readers
  • News & Politics/Avid News Readers/Entertainment News Enthusiasts

From an editorial standpoint, this is useful because it allows publishers to determine and target varying levels of high-value users, improving the efficacy of a new content strategy or ad campaign.

If your site is already powered by RebelMouse, email support@rebelmouse.com to get a breakdown of your audience's Affinity Categories. If you aren't powered by RebelMouse yet, request a proposal today and start receiving the data you need to grow loyal followers at scale.

Related Articles

Infinite Scroll: An Innovative + Intuitive UX

There is a common misconception that publishers have to sacrifice monetization and professional design to deliver a high-performing, quality user experience to its readers. But in today's modern publishing environment, websites can deliver an unobtrusive site experience that's intuitive, elegant, and prosperous.

To do this consistently, RebelMouse supports infinite scroll as part of our bigger design strategy called Social UX for Media. Much like the news feeds of Facebook, Twitter, and Instagram, infinite scroll provides an endless stream of articles to its readers so they never reach the "end" of your content.

Infinite scroll is an innovative approach, but it is also a widely adopted standard that has been endorsed and is supported officially by Google, Comscore, Nielsen, and many other industry giants. It's part of a new media strategy deployed by companies with massive valuations and the highest level of visibility in the U.S. market, including Axios, Vice, and The Verge.

In fact, RebelMouse built and launched news powerhouse Axios, now one of the biggest new media companies to date, with our Social UX for Media design featuring infinite scroll. It's still a core part of Axios' successful publishing strategy today. The feature has also been key to the growth of many other RebelMouse-powered properties, including La Verità, Dance Magazine, and United Airlines.

RebelMouse's Social UX for Media design, featuring infinite scroll on hub.united.com.

The primary reason infinite scroll is so successful is because it mimics user behavior in an innovative, yet familiar way, thanks to its similarity to social feeds. On mobile, expandable posts make it easy for users to read "before the jump" and quickly expand to the rest of the article with one click, rather than being taken to another article page. This is similar to when a user expands a caption on Instagram. It's these simple design details that bring massive growth to key stats like return visits and time on site.

Our page view methodology not only keeps the user experience intact, it also includes robust ad serving technology. We use industry standard rules for page views that require at least 50% of the screen space to change before it counts as a new page view. So whether you use Comscore or Nielsen to verify your site traffic, infinite scroll will not have a negative impact on your insights.

If you're interested in launching a site with our game-changing Social UX for Media design, request a proposal today and let's start working together. If your site is already powered by RebelMouse, and you have questions about infinite scroll, email support@rebelmouse.com.

Related Articles

Particle Assembler: Ads in Slideshows Now Supported

You can now insert ads between slides in a slideshow!

Monetizing users' engagement and page views is pivotal to most digital businesses, and our Particle Assembler has been an invaluable tool in helping RebelMouse clients to insert native ads seamlessly into their content. Now we've taken this functionality one step further by introducing support for ads between slides in Assembler's slideshow layout.

Keep reading... Show less
Subscribe to Our Newsletter