2
Hi,
I think you hit the nail on the head...when you said that you need to play around with each module more in order to get a better feel for what features each has to offer, and what the experience is like in using each. I can tell you that there are other things to consider as well, such as, who is going to be using the blog in the end. If I or someone else who is very familiar with web design was going to be using the blog, I would install the WordPress module in Xoops, and use that. However, if this blog is destined for a client, who might not be so technically inclined, I would might use the Article module... as it can be customised (on the admin side) to be more user-friendly, more easily. I once created a blog for someone using XOOPS & the Xpress module...and I ended having to redo the site (in just Wordpress, not the Xpress module, but the standalone sofware), as it was too confusing for the client in the end. Not that the WordPress back-end was confusing itself, but the fact that there were two back-end admin sections...one for Xoops, and one for XPress... it was overwhelming for this person, and very confusing. As well, there is a bug that occurs sometimes where, you first have to be logged into XOOPS to access the Xpress module, but sometimes it forces you to login through the Xpress admin as well (dual logins). Or, it boots you out of one admin section or the other...and the person has to keep logging in. We might be able to figure it out, or chock it up to a minor and occasional annoyance, but to a client it means that site is "broken", and I can understand that viewpoint.
WordPress does have a huge community of plugins and themes that you can use however... so that is another bonus over the Article module, if you need those features. If not, then it's not really relevant.
If you just want to have a blog, that isn't nessesarily connected to the rest of your site, you can still pull the content from WordPress to appear in a XOOPS block.
I hope my ramblings make some sense?
J.