Subscribe to Our Newsletter

x

How to Style and Add Badges to Posts

Badges have multiple uses. Some clients use them to flag their promoted content, others just like to have a cool way to categorize their content.


If you want to set up some badges for your site, here's a full step-by-step tutorial:

1. Set up your badge images. Go to Badges in the left-hand navigation menu.

2. Then, add a new badge. You'll be asked to:

  • Select a design for your badge by uploading an image or pasting a URL to an image.
  • Select your badge's name to identify it.
  • Link your badge to a tag so it appears automatically when that tag is used.

For tags to appear, you'll have to assign them to posts in the Entry Editor during their creation. If you haven't been doing this, no fear — you can edit older posts to add them after the fact. For example:

In the Advanced Settings menu (gear icon) of the Entry Editor, I've selected a badge for an existing post.

There is some other flexibility to be had with badges. You can:

  • Choose to have more than one badge displayed (but you'll always need to create them first as described above).
  • Choose which badge should be the primary one for a post.

You can also customize how your badges look in the Layout & Design tool. First, make sure your layout is set to be displayed in Element Order, in the settings of the Lead Media element inside the Post page:

You can add CSS per element to badges as well. To do so, click on the Styles card and scroll down to the badges' sub-elements:

Here's an example of a post displaying a customized badge:

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

Inside RebelMouse’s Quality Assurance Operations

How We've Perfected Stress-Free Publishing

At RebelMouse, we like to refer to our enterprise publishing platform as "lean tech." Most publishers have a natural inclination to start doubling down on teams of developers who try to build unique experiences to help stand out above the noise. But they should actually be doing the opposite: Lean tech is the preferred way to cut through content saturation. By allowing RebelMouse to obsess over your product, content producers, editors, managers, and everyone in between can focus on creating quality content and taking advantage of opportunities to leverage distributive publishing strategies that create real revenue growth.

One of the major reasons we're able to maintain a lean tech environment is thanks to our approach to quality assurance (QA). We make updates to our platform daily to ensure our clients always have access to the most robust, high-performing, and secure version of our platform. Behind the scenes, this means having a solid QA structure that's efficient, creates less bugs, and catches the ones that do pop up before they go live. It's a system of checks and balances that's hard and costly to replicate on a custom CMS. Here's a glimpse into how it works.

Our Tech Stack Toolbox

  • Cucumber
  • Java
  • Junit
  • Maven
  • Selenium WebDriver
  • TeamCity
  • Zalenium (Selenium Grid)

Our Checks and Balances Workflow

Automated Regression Testing Cycle

The Lifecycle of a Product Update

When an update is first made to RebelMouse, TeamCity immediately triggers the start of automated tests to review integrity.

TeamCity Build

TeamCity Agent

The tests run in parallel on TeamCity's Build Agent. Next, Zalenium creates docker containers with browsers that matches the count of parallel threads. An Allure report is then generated from the test results, which shows the state of the application after the update.

Allure Report Pass

If a test doesn't complete successfully, the testing framework receives a video with a failed test and attaches it to the Allure report.

Allure Report Issue

Based on the report analysis, a QA specialist will create a "bug" ticket in our product management software to address the issue if needed. Then, information about the bug is immediately sent to the project manager and we begin the process of correcting the problem.

The media powerhouses we power can publish with confidence knowing that any product issues that arise are met with a tried-and-true process to fix the problem with little-to-no disturbance to their workflow. If you have any questions about this process, please email support@rebelmouse.com.

Related Articles

Related Posts vs. Posts in Assembler

Here's the difference between Related Posts and Posts in Assembler.

By using Related Posts and Posts in Assembler, you can help your audience stay engaged with your site's content and generate more traffic. Both of these features can be added to any post through Entry Editor.

When creating or editing a post, you can add a Related Posts section to the bottom of it that consists of a selection of existing posts on your site that you choose to surface. Only the main image and content headline are pulled, along with a link to the original post. This is similar to the Around the Web section that also shows up at the end of your post when you enable it from the SEO tab of Entry Editor.

Keep reading... Show less
Subscribe to Our Newsletter