How to configure Plumbit blog and single-post layouts

Choose the blog page#

In Settings > Reading, choose whether the site shows latest posts or a static page. With a static front page, choose the page used as Homepage and a separate page used as Posts page. The assigned Posts page controls the theme blog index. A page containing an Elementor post widget is not the Posts page unless WordPress assigns it there.

Plumbit's index displays the published posts assigned to the blog index and its pagination. The assigned page's editor content is not used as the blog card list content, so editing that page alone does not change the posts shown by the index.

Configure the Blog section#

Open the Customizer's Blog section. The active controls include Blog Index Design, Blog Index Image Size, Blog Single Image Size, Read More Button Title, Post Length, Related Posts Title, Featured Image on Single Posts, Read More Button on Blog, Navigation below single posts, Enable Posts Meta Info, and separate date, author, category, and comments metadata toggles.

The same section also exposes Related Posts below articles and Author box below posts. Save the Customizer changes, then verify both the index and a single post.

Understand the blog index#

The theme index displays each post with its featured image when available, entry metadata, title, excerpt or full content according to Post Length, and a read-more link when enabled. Blog Index Design changes the image placement between the available Image Top, Image Left, and Image Right choices. The index uses the WordPress post list and theme pagination; it is not populated by the content of an unrelated Elementor page.

Understand the single-post page#

The single-post template renders the post's featured image when the matching setting is enabled, title and metadata, main content, tags, the configured entry footer, optional previous and next navigation, the optional author box, optional related posts, comments, and the active sidebar layout. Individual post page settings can override supported global values without changing other posts.

Elementor edits content placed in the post editor when that integration is available; do not assume it replaces the complete single-post template or its comments, navigation, author, related-post, page-header, and sidebar areas.

Use archive contexts#

Category and tag archives are WordPress archive contexts. Author and date views are also WordPress archive contexts. They use the archive query and the theme archive template rather than the assigned Posts page selector. Search results use the search query. If a title, page header, sidebar, or pagination differs, first identify the context before changing the Blog controls.

Comments, related posts, and navigation#

Comments depend on the site's discussion settings and the individual post's Discussion controls. Plumbit renders the comment list, reply form, closed-comments state, and pagination through the single-post comments template. Related posts are an optional single-post section that matches the current post's category query, excludes the current post, and displays available thumbnail-backed results. Previous and next navigation is separately controlled and appears below the single post when enabled.

Check the blog sidebar#

The blog index, single-post, and archive layouts use the theme's page/sidebar arrangement. Review the active sidebar and its left or right layout in the relevant page or global settings. An empty sidebar area can have no visible widgets, while Elementor Canvas pages follow Elementor's canvas behavior rather than the normal theme columns.

Verify a layout change#

1. Save one setting at a time#

   Change the relevant Blog control, save the Customizer, and refresh the index and a single post.

2. Compare ownership#

   If a card or title does not change, check whether it comes from the theme index, a single post, an archive, or an Elementor widget with its own settings.

3. Check a narrow viewport#

   Review long titles, images, metadata, related cards, comments, and pagination on a phone-sized viewport before publishing the layout.

Get help safely#

Record the context, URL, provider, affected Customizer control, post-level override, sidebar state, and browser result. Send that information with the site and component versions to support; do not send passwords.

Related articles