Forum Moderators: rogerd
They look very similar to me. Two of my sites would probably need several images on the index page.
I don't know of any specific examples of sites using a blog as a CMS that I could check out & compare though I know they are out there :-)
Especially of interest is WP2's static page support. But even without that, I've removed the blog-ish bits from the templates (like post date and pingback stuff) for a long time to use WP and other tools as CMS.
The only downsides I can see are:
1) even if you disable comments and trackbacks, you'll attract a lot of comment spam. Removing it from the templates stops it from being displayed, but not from being submitted.
2) If you aren't alert to RSS, you may wind up sending feeds to aggregators before you're ready. WP by default will ping pingomatic every time you post. It's not obvious that you should shut that off while you build your site up.
3) stay alert to vlunerabilities. But that goes for any popular software really. It's just that if you aren't using xml-rpc (for example) you probably won't think about it a lot. I just remove the thing from my WP installs.
Do a google and hopefully you will find one.
Are you referring to trackbacks, pingbacks, comments, etc...?
Added: just reread your previous post, rogerd. We're in agreement. My main point is: if you want the comments, go in armed with a strategy to manage the spam. There are plugins that help, but there really isn't a set-and-forget anti-spam feature in any tool I know of.
As far as usage goes, the learning curve is a little bit steeper, but I find that to be a good thing.
WP does SE-friendly URLs with the "page slug" feature, though it doesn't offer custom titles as a standard function.
Slightly OT, but what does the xml-rpc do and what happens if I don't need it and delete it? Nothing?
If you don't use that sort of tool, removing xml-rpc.php reduces the attack surface of WP. Look at it as a programmable way to post. There have been some worms targeting vulnerabilities in xml-rpc (although not necessarily in WP's implementation).
We should do a "locking down Wordpress" thread.
Great idea, linear, and thanks for volunteering to kick it off! ;)
