Although the project title "Portfolio" is more generic term than blogging, but in most of the cases, blogs become the personal websites, and so the portfolio of that blogger.

I have tried some services that I would like to list their pros & cons, it's not a "vs." like post, but an issue we can benfit from to make Porftolio better, and overcome most of the cons in those platforms.

Wordpress

Maybe the most popular blogging service. I have 2 blogs one Wordpress on is selfhosted and the other is a free one on wordpress.com. I've also worked on several plugins for this platform.

  • Wordpress attracted users when it released, because of making the line narrower between programmers and normal people for simple websites. Even if you install it yourself, it's very straightforward, don't have the memory and other issues that can rise during the installation like Drupal (e.g. the email failed error message when installing D6). Second thing is the welcoming admin page that has quick statistics and quick post functuality (vs. D7 admin empty lame page). The third friendly option is the default WYSIWYG with images and video support (vs. you have to install WYSIWYG on Drupal, configure IMCE for image uploads, and die trying to make video upload works with it. D7 Media modules can make this task easier). Fourth point for non techie-users is the plugin installer with search functiuality (vs. contrib in D6, and the unnoticed "+ Install new module" on modules page on D7. Again in short, WP pros are: Installer, Admin page, WYSIWYG, plugins (modules) installer.
  • Extending Wordpress byond it's core capabilities is a painful task, like custom fields, landing pages, even writing plugins is painful.
  • Updating Wordpress & plugins is an easy task, but requires an active admin. Sometimes, users can leave their blogs for months (because of exams, work, etc...), and the fast release of WP and it's plugins sometimes has security fixes (same as Drupal). I remember when many blogs on DreamHost hacked because of this issue. Also, check #1356476: Make updates happen seamlessly.
  • wp.com hosted versions are better compared to the previous point, WP updates are installed automatically, you don't have to do this manualy (even if it's only a one-click update). But the cons of wp.com is no custom themes nor custom plugins you can add, also you can't ingore the feel of privacy of having full control of your data in selfhosted option. In short, both options should be available, some users prefer one, and others prefer the second.

Tumblr

    I created a blog with Tumblr some months ago just to try it out, not active on this platform, but I can say about it:
  • Attracted huge number of users, and I don't know exactly how. But for Portfolio we can benifit from the already huge userbase of Drupal itself. Regular users bring other users, it's a win-win factor (in fact I created my blog when I saw chx posting on his Tumblr blog).
  • It's easier to be social on Tumblr, you can link your twitter and facebook accounts direclty. You can also "follow' blogs on Tumblr itself, and their updates appear on your Tumblr main page.
  • Provides different and maybe more beautliful look-and-feel (themes) than WP and other blogging services.

Drupal Gardens

Created two personal blogs on Drupal Gardens before. Well to be straightforward I never returend to them until they sent me an email to alert me that if I didn't access my account my blogs (sites) will be archived perminantly.

  • First you can't pretend it's a blogging platform. It definitly requires Drupal skills to adminster it.
  • Default themes are ugly, and I don't want to customize the colors and font-size (and lots of work) just to make my site looks different but still ugly.
  • No huge bloggers userbase.
  • Good point is that you can at anytime export your site with all the modifications you've done, and host it somewhere else.
  • Freespace is very limited, only 50MB.

What we can learn from this quick comparsion, and pros & cons:

  • For normal people, techincal stuff is hard and most of the times ingored (updates, making themes, uploading modules, configuring the site for the first time e.g. install WYSIWYG and other modules and configuring them).
  • Free hosted verison (and pro one) attract different userbase than selfhosted.
  • Social stuff is a most nowadays. Easier social linking is a win (e.g. a one-click to auhtorize your account on Twitter).
  • Friendly, simple & easy to install Drupal themes!

Comments

s.Daniel’s picture

Title:Pros and Cons of Different Blogs Platforms» Pros and Cons of Different Competing Platforms

Thanks for sharing.
I think this can and should be extended to other similar platforms as well. The folks at Typo3, Modx and Joomla etc. do have some relevant selling points. If someone of use has experiance with the current versions it would be interesting to hear about that. If none of us currently has much knowledge than doing some research and documentation e.g. on the next code sprint may help us identify Drupals strengths and weaknesses to help sharpen the portfolio idea and image.

E.g. Typo3 is has a clean interface for translating content and the possibility to search for extensions and install them from within the admin interface.

Grayside’s picture

Market research to get some base features is a good idea, but I think making this competitive with other technologies is probably a later phase task.

Creating a Dupal flagship distribution that pushes technology for some specific use cases to the limit is not the same thing as trying to fill in the competitive weaknesses Drupal has compared to other projects. The opportunity to plug some weaknesses in passing is always a good one to take, as long as they are fixed upstream of Portfolio as much as possible.

Discussing those weaknesses and how to tackle them probably belongs in a different venue, which active Portfolio developers can raid for ideas.

s.Daniel’s picture

Agree, the Portfolio team needs to focus on getting Portfolio right and can learn from similar systems. Scope can't be to "fix" Drupal itsself at first hand. ;)

My point arises from the fact that you cannot easily compare Drupal the CMF with CMS products that tackle a specific use case but you can compare a CMS system built on top of Drupal as a product with other similar systems. And people will, so we should be prepared.