Post Grid Pro for HubSpot

A filterable grid of the blog posts already on your portal. Tag chips come from the tags carried by the posts on the page, search runs across title, excerpt and tag as you type, and the list pages with numbered pages or a load more button. Every colour, size and radius is a field.

Instance 1

Defaults, untouched

Only the blog is picked. Everything else is the module as it drops onto a page: the page font, hairline borders on a white card, three columns, tag chips that stack, live search and numbered pages.

Journal

Latest posts

Filter by tag or search the list.

12 posts

Growth

How many form fields is too many?

Every field you add to a contact form costs you some inquiries. Here is how we decide which ones earn their place, and how to get the rest o…

Ryan Mitchell 5 min read
Read more
Instance 2

Four columns, single-tag chips, load more

A blue accent on the active chip and the read more link, Open Sans from the font field, four tighter columns with 4:3 images, and a load more button in place of numbered pages. Picking a chip swaps the tag rather than stacking it.

Briefing

From the newsroom

Pick a tag or search the list.

14 articles

Instance 3

List layout with author photos

The list layout puts the image on the left at a width you set and the text on the right, and stacks below the mobile breakpoint. Author photos sit in the meta row, dates are numeric, four posts to a page.

Archive

Every post, in order

Search runs across the title, the excerpt and the tag.

14 entries

Growth

Should you put prices on your website?

Owners worry that publishing prices scares buyers away. In our experience it mostly scares away the buyers who were never going to sign, and it speeds up the ones who were. Here is…

Olivia Bennett 3 min read
Open
HubSpot tips

Five settings to check on every HubSpot form

A form can look perfect and still lose leads. The problems hide in the settings tab, where nobody looks after launch day. These are the five settings we check on every HubSpot form…

Grace Thompson 3 min read
Open
Growth

How many form fields is too many?

Every field you add to a contact form costs you some inquiries. Here is how we decide which ones earn their place, and how to get the rest of the information later.

Ryan Mitchell 5 min read
Open
Content

Your about page is a sales page. Write it like one

Most about pages open with a founding year and a mission statement. Visitors skip both. They came to answer one question: are these people the right fit for my problem, and can I t…

Olivia Bennett 3 min read
Open
Instance 4

Text cards, no images

Two columns of text-only cards with a long excerpt, full dates and author photos. The result count is off, and load more reveals four posts at a time. Accent in green.

Reading

Longer pieces

Two columns, no images, a wider excerpt.

Growth

Should you put prices on your website?

Owners worry that publishing prices scares buyers away. In our experience it mostly scares away the buyers who were never going to sign, and it speeds up the ones who were. Here is how we think about it with clients.

Olivia Bennett
Continue reading
HubSpot tips

Five settings to check on every HubSpot form

A form can look perfect and still lose leads. The problems hide in the settings tab, where nobody looks after launch day. These are the five settings we check on every HubSpot form we inherit, usually in under fifteen mi…

Grace Thompson
Continue reading
Instance 5

Borderless cards, centred header, no toolbar

Chips and search switched off for a plain latest-posts block. The card has no border and no padding, so the square image carries it. Centred header, three columns, numbered pages of three.

Documentation

Module Guide

What it does

Post Grid Pro renders the blog posts already on the portal as a grid of cards that filters, searches and pages in the browser. HubSpot's own blog listing has no client-side filtering, so a visitor who wants one topic has to load a topic listing page. This module keeps the visitor on one page: the tag chips and the search field narrow the same set of cards without a round trip.

Data source

Posts are fetched with blog_recent_posts against the blog chosen in Blog source › Blog. On a portal with several blogs, that field decides which one. Leaving it unset falls back to the portal's default blog. Posts to pull sets how many are fetched, and everything downstream, including the chips, the search and the pagination, works over that set.

Restrict to one tag narrows the fetch to posts carrying a single tag before anything renders, which is useful for a topic page. Exclude the current post drops the post being read when the module sits on a blog post template.

Filters

The chip row is built from the tags carried by the posts that were pulled, so a tag with no post never gets a chip and a new tag appears as soon as a post uses it. An All chip sits first and clears the selection.

Chips are buttons, so Tab reaches them and Enter or Space activates them. Each carries aria-pressed reflecting its state, and the group carries a label for screen readers. Filtering returns to the first page.

Search

The search field filters as you type, across the post title, the excerpt and every tag on the post. It runs over the whole pulled set rather than the page on screen, and combines with the chips: a card has to satisfy both. The running total sits in a polite live region so a screen reader hears the new figure. When nothing matches, the grid is replaced by an empty state whose title and text are both editable.

Pagination

Pagination › Mode switches between three behaviours, and Cards per page drives the two that page.

Card contents

Each element on the card has its own switch, so the card can be as full or as bare as the page needs.

Layout

Grid or list, and the column count is set separately for desktop, tablet and mobile with the two breakpoints on the Style tab. The list layout puts the image on the left at a width you set and stacks it above the text below the mobile breakpoint. Column gap and row gap are separate fields.

Style

Every colour, size, radius, border width, gap and duration writes a CSS custom property on the section element, so no markup carries an inline style and two instances on one page never collide. Leave the font field empty and the module uses the page's font; the accent colour starts from the host theme's primary colour.

Accent is the field to reach for first. The active chip background, the title hover colour, the read more colour, the focus ring and the current page button are all left empty by default and follow Accent. Setting any of them individually overrides it for that element alone.

Card motion is three fields: duration, delay between cards and travel distance. The delay is applied per card rather than to the grid, so cards arrive one after another as the row enters the viewport, and the sequence restarts for cards revealed by a page change or a load more.

Accessibility

Notes on this page

The first instance runs on field defaults. The other four change accent colour, density, layout, toolbar and card structure. Four inherit the page font (Inter here); one sets Open Sans in the font field. All of them read the Northline demo blog. Each instance is wrapped in a full-bleed stage so the module can be judged on its own, and the module's container padding matches the stage padding so a card edge lands on the same line as the heading above it.