It’s probably easier to do it the other way around. That is, customize your site to show the blog posts on the front page and then insert your content before the posts.
I was working out ways to do this and at first thought of using the ol’ widget approach, but you don’t want a whole load of possibly frequently-updated content sitting in a widget.
You also don’t want a whole load of content sitting in php, where it’s harder to update, version, preview, etc.
So I came up with the idea of inserting a page’s content before the blog posts instead.
I presume that for your current front page, you have set Customizr up to show a static page on the front page. So you already have a page of content that is your front page.
Do the following :
- Change your current static page’s title to
home
and set the slug to home
;
- In Settings > Reading (not in Appearance > Customize *) , set the front page to show your latest posts;
- Put the following in your child-theme’s functions.php**:
add_action ( '__before_loop', 'add_home_page_before_posts');
function add_home_page_before_posts($path) {
if ( is_home() ) {
$post = get_page_by_path( '/home' );
$content = $post->post_content;
echo $content;
}
}
- Use a redirect plugin (e.g. Eggplant 301 Redirects — I’ve not used it myself, but it gets good ratings and seems well-supported) to permanently redirect your page called “home” to your real home/front page. (That is, redirect from what will then be https://qbservices.net/home to https://qbservices.net/ ) You need to do this because, although it will not be on your menus or anything, search engines and the odd curious user might end up there by mistake otherwise.
- Tell me if it works for you.
* Don’t use Appearance > Customize to change this because I think there’s a WP bug in there and have opened a ticket. Using it now might confuse things.
** You mention using a php plugin, but you really don’t need to do this. Read about customizing Customizr and you’ll see that it’s easy enough to do this yourself without a plugin.
Polling d4z_c0nf and nikeo to see what they think of this solution, or whether there’s an easier approach. (I’m sure there’s a better, deluxe approach, which would take time to code, but this is relatively quick and easy.)