Blog page design examples

A blog index helps readers find something worth reading and keeps them browsing. Our examples lead with a featured post on an illustrated cover, then add category filter chips, search and a grid of six posts with authors, dates and read times, so you can see how one listing adapts across eight visual styles on desktop and mobile. Every example is an original design that comes with its HTML code and a DESIGN.md of colour, type and spacing tokens, in light and dark. Free to use and adapt.

DeviceAll Web Mobile

StyleAll Minimal Editorial Brutalist Luxury Playful Corporate Retro Monochrome

Theme

16 examples

Web · minimal

Web · editorial

Web · brutalist

Web · luxury

Web · playful

Web · corporate

Web · retro

Web · monochrome

Mobile · minimal

Mobile · editorial

Mobile · brutalist

Mobile · luxury

Mobile · playful

Mobile · corporate

Mobile · retro

Mobile · monochrome

Blog index design tips

Give the featured post noticeably more space than the grid, and change it regularly so returning readers see that the blog is active.
Keep category chips to a short, stable set and show which one is active, so filtering feels predictable rather than like a tag cloud.
Show the date, author and read time on every card, because readers use them to judge whether a post is current and worth the time.
Keep card images to one aspect ratio and crop consistently, which stops the grid from jumping about when titles run to different lengths.

Questions

What makes a good blog homepage layout?

A clear hierarchy: one featured post at the top, a simple way to filter by topic, a search field and a grid or list of recent posts. Each card needs a title, short excerpt or image, date, author and read time. Pagination or a load-more button keeps the page fast as the archive grows.

Should a blog index use a grid or a list?

Use a grid when posts have strong cover images and short titles, and a list when titles and excerpts carry the weight. Grids look richer but make long titles harder to scan. On mobile, both collapse to a single column, so test how the cards read at that width.

Do blog posts need read times?

They are not essential, but they help readers decide what to open. An estimate based on word count, usually around 200 to 250 words per minute, is good enough. Round to whole minutes and keep the format consistent across every card and article page.

Browse by pattern

App screens

Dashboard
Data table
Analytics charts
Login
Sign up
Forgot password
Two-factor code
Welcome
Onboarding step
Permissions request
Home
Feed
List view
Detail view
Kanban board
Calendar
File manager
Search results
Editor toolbar
AI chat assistant
Chat list
Chat thread
Video call
Image viewer
Map view
Video player
Create post
Class schedule
Booking details
Booking confirmed
Product detail
Cart
Checkout
Order confirmation
Settings
Profile
Notifications center
Team members
Roles permissions
Audit log
API keys
Integrations
Billing plans
Invoice
Paywall upgrade
Cancel subscription
Empty state
404 error
Loading skeleton
Success confirmation
AI workspace
AI settings
Version history
Approval queue
Doctor directory
Telehealth visit
Clinic home
Music player
Playlist
Portfolio home
Case study
Security dashboard
Project tracker
Course dashboard
Multi-step form wizard
Bank onboarding
Product scan
Split view (master-detail)
Canvas editor
Floor plan
Voice call
Toast / snackbar with undo
Confirm dialog (destructive)
Side drawer
Command palette
Date range picker
Form validation errors
Sign-in error
Card declined at checkout
Find a pro (home services)
Book a home-service visit
Job tracker
Account email
Order email
Shift scheduler
Leave calendar
Time-off request
Multi-location operations dashboard
Inventory stock
Savings goal
Onboarding carousel

UI components

Tabs
Cards
Pagination
Popover
Tooltip
Dropdown menu
Accordion
Radio buttons
Breadcrumbs
Toggle switch
Stepper
Sidebar navigation
Loading spinner

Website sections

Website templates

Building with an AI coding agent? Every screen here is also in the free Made Good Designs MCP server: ask Claude, Cursor or ChatGPT to search_ui_screens (e.g. “billing settings, editorial style”), get_ui_flow for a whole journey, and get_ui_screen_code to pull the HTML and DESIGN.md straight into your project.