Jump to:
| Project: | Documentation |
| Version: | 6.x-1.x-dev |
| Component: | New documentation |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (won't fix) |
| Issue tags: | GHOP |
Issue Summary
Type: Documentation Outreach
Author: locutus.the.borg
Choose at least four open source frameworks or cms, Drupal included, and compare them, technically their flexibility and easy to use. Its prefered that you choose software that you have not used before.
Points to take into consideration:
a) Requierements: s.o., language, web server, database.
b) Installation: problems that you find, technical level that its needed
c) Configuration: basic and advanced
d) First content creation: create your first pages of content
And then try to find out:
e) Flexibility (creation of themes)
f) Extension (can easily grow to be better/more adapted? can be integrated with other software?)
g) Capabilities (Produces standard content?, is accesible?)
...
As a conclusion explain the good and the bad of every framework and determine which would you choose to make your next project (explain the type of project).
FRAMEWORKS SUGGESTED (any other that you find is welcome): Drupal, Joomla, Typo3, Movable Type, Wordpress, Textpattern, Alfresco, Plone.
Estimated time:
4 to 5 days.
Comments
#1
Claimed by thekiefs: http://code.google.com/p/google-highly-open-participation-drupal/issues/...
#2
#3
Work available for review from http://code.google.com/p/google-highly-open-participation-drupal/issues/...
#4
I followed the link above, and read through the Google Docs document containing your review.
I found it a very interesting article, and as far as I can tell, you did a good job detailing what you perceived as the strengths and weaknesses of each platform. The article appeared, to me, to be fair and only with the slightest of biases toward Drupal. I know nothing about Typo3 -- in fact, all I know about it is what I read in your article -- so I found that section especially interesting.
A few notes:
and in reference to Wordpress you say:
But, in the conclusion, you state:
From reading your analysis of Drupal's and Wordpress's respective installations, I was surprised to see "... make the install a little smoother..." in your conclusion. Please understand -- I'm not questioning your impression of the installations, but am instead curious about how you feel Drupal's installation could be improved, in comparison to the other packages. From the way I read your Drupal section, you felt the installation went well, but... ?
I'm really very impressed with this.
#5
I miss some kind of comparison table with strength/weaknesses of every software and maybe some sample sites that are built with them, but overall it is well written and explained.
Good work!!
#6
Updated work in thekeifs google doc: http://docs.google.com/Doc?id=ddz4j2xh_33dxj2kp
#7
Now with the Comparison Chart it looks like the task is complete.
Thanks for the addition.
#8
Great, I've marked the task complete. Now what we should do is put this in the handbook somewhere.
Any takers?
#9
Also, we need the comparison table to be cited to cmsmatrix.org. Thanks to keith for spotting this.
#10
Changed the component to reflect the new component categorization.
John
-----------------------
Drupal Norge
Det offisielle norske nettstedet for Drupal
#11
Regarding http://docs.google.com/Doc?id=ddz4j2xh_33dxj2kp I got
"Sorry, the page (or document) you have requested does not exist."
Is there a new URL or is http://google-highly-open-participation-drupal.googlecode.com/issues/att... it?
I put a copy of the HTML in that zip at http://rym.waglo.com/Compare_Drupal_with_oth.html in the meanwhile.
#12
I have a problem with this. I propose we should encourage a local copy of such documents do to these consistent short comings in 3rd party hosting and broken links. Maybe we should talk about this at the next Doc meeting. Meanwhile can we move this document into our documents in addition to the external link?
Mike
#13
Well the plan was to get the doc turned into an actual handbook page here on d.o - not to have a lonely file floating in the ether. My main concern with this now is that it is a year old, so adding it now may be more trouble than it's worth. :-/
#14
I don't think this should be added. Self reviews mean nothing to anyone. I read these things and say... BLAH, BLAH, BLAH! Read "Don't Make Me think" it makes a perfect example of the failures of these types of documents
Lets face it Joomla, WordPress, BBforums, OSCommerce, Elgg etc... all have distinct advantages... We will simply not be able to be better then everyone at everything since each open source project is focused on its own communities goals! In addition, who says we have to compete with other Open Source programs? If Joomla works for you GREAT, USE IT!
If you want to compare something, lets compare Open Source with Closed or Payed Source Solutions.
#15
I have to agree with MGParisi. I appreciate the work that's been done on this piece, but it seems completely out of scope for Drupal documentation. This is something that makes more sense coming from an outside body that evaluates CMSs.
It also adds a maintenance burden that we don't need. It's hard enough trying to keep the docs up to date with Drupal developments, let alone with three other projects.
#16
Well this was a loooong time ago and done for GHOP. I think that this is pretty much dead, so I'm won't fixing.