I’ve built my company’s new blog on wordpress, and love it. Now I want to migrate my entire site to WordPress so I can benefit from CMS, SEO, and plugins that let me do stuff that’d be WAY over my head outside the world of WordPress.
All the advice I’ve seen says to handle the blog itself and non-blog-site with a single instance of WordPress. Appealing. But there’s some site content that it’d be cool to handle as ‘posts’ instead of ‘pages’ — namely press releases and job postings. That way when my PR and HR people add them, a category page would display excerpts just like the main page I have to create manually today.
But I can’t have those posts appearing in my Recent Posts widget, on my home page, and in my RSS feed.
I was on the verge of keeping them out of my sidebar and off my homepage, but the solution isn’t working across all browsers because of some weird </div> recognition. Haven’t looked into the matter of RSS exclusion yet.
No way am I the first person running into these issues, but can’t find relevant info or threads. Maybe I’m a bad searcher. : (
Are there any “best practices” for building a blog+site with wordpress? One shared instance or two discrete? Non-blog content as posts or all pages? Masking some categories of ‘posts’ from the blog experience — recent posts widget, homepage, rss feed, etc.
Any advice or info is much appreciated.
- The topic ‘WP for Blog Site CMS; One instance or two?’ is closed to new replies.