Most remote-first announcements get shared with a generic banner that says 'remote-first' in a slab serif font. That tells a candidate nothing about how the policy is implemented, where the team is, or what they should expect on day one. SleekPixel handles the case with a preset that reads the actual structure from the WordPress post: how many countries the team is in, how many timezones the working day spans, and where the public handbook lives. The card surfaces those facts, which is what candidates evaluating remote roles actually want to see.

The setup uses three custom fields: countries_count, timezones_count, and handbook_url. The first two render in the subhead as a fact line. The third is a footer anchor that hints the policy is documented rather than aspirational. The accent color is restrained, the typography is calm, and the corner mark uses RMT to signal the post category at a glance.

The card is square at 1200 by 1200 so it fits LinkedIn, Instagram, and Slack equally well. Because the source fields live in the post, updating the country count when a new region opens regenerates the card automatically. There is no risk of an outdated number sitting on a recruiter's pinned post six months after the team grew past it.

Candidates evaluating remote roles read announcements with a specific filter. They look for signals that the company has actually built for distributed work, not just labelled itself remote-first. A slogan banner does not carry those signals.

A card that shows the country count, the timezone span, and a link to a public handbook does, because all three facts are checkable and they tell the candidate exactly what to expect on the inside. SleekPixel makes those facts the structure of the card rather than copy points buried in the post body. The team fills in the custom fields once, the template renders them in the subhead and footer, and the card stays current as the numbers change.

That last part matters more than it sounds. A remote-first announcement that says '5 countries' six months after the team is in 11 actively undermines the credibility the post is supposed to build. A card that updates automatically when the field is edited keeps the pinned post honest.

The same template can be applied to follow-up posts that announce a new region or a new timezone block, so the series of remote posts reads as a continuous policy rather than a one-time launch. Over time the card becomes the canonical visual for the policy, and the post body becomes the place where the implementation details live. That is the right split.

Cards summarise, posts explain, and SleekPixel handles the summary automatically so the team can keep writing the explanation as it grows.