EE is an excellent CMS system (there look, praise not insults), but it seems to be hiding it’s light under a rather unwieldy bushel of documentation sources. A maze of fact.
Hi there,
Glad that the link was of some help to you. I am a system architect by nature and by profession, so I always try to understand the architecture first, before moving ahead. There were a couple of things that were encouraging about ExpressionEngine:
1) Good architecture to build on
2) Backward compatibility, which is missing from almost all open source CMSs, except for Wordpress (which has a decidedly inflexible architecture)
However, someone has to bite the bullet on getting up to speed on ExpressionEngine. I am right now moving ahead very rapidly with Drupal, since their documentation is very well organized (much better than Joomla), and it has a relatively clear and clean architecture, for building websites. ExpressionEngine, is a do-it-yourself situation, and I simply do not have the time or energy to begin plowing through the maze of information, as you described, awaiting for the ah-ha moment, which may, or may not ever come. And who knows what realization I may come to at the ah-ha moment. Maybe, after several months, I will finally realize that EE is not for me. Yikes!
Every company has the same problem of defining their business model, target users, and how to service those targeted users the best. If EE is targeted to the whole universe of potential developers and users, then the task of documentation is daunting. However, that is a business problem, which I cannot solve. Taking a more reasonable approach, can yield some very serviceable documentation such as that available on the Drupal site.
Rich