I would agree with the above posts. Love Sitefinity and what it's capable of - I've been using it since v2.0, however developing with it has always been somewhat of a self-discovery model and can be frustrating. You have to dig through using intellisense, reflector and other tools to really understand what is going on because the manual is often out of date or imcomplete. This doesn't say a lot for the documentation available when many people resort to digging through the assemblies.
The fast release cycle of new versions is a double-edged sword. New features fly out the door all the time which is great, however two things suffer - documentation and stability. To introduce new features to developers, the documentation must
keep pace with the code. Ideally, the documentation would actually precede the changes, so we have a chance to understand what is coming. It cannot be an afterthought. Following this model would promote documentation upkeep since a release would not come until properly documented.
As for the comment on API changes, I would agree with this too. With each new version, I never know what is and isn't changing in the API. More documentation is needed on what has changed. A one page general overview is not enough. For example, the most current developer doc has this explanation:
This is far too general
, not to mention references v3.2 which is extremely out of date in terms of documentation.
Below is the type of thing most of us would hope for with each release. It explains exact differences between two Telerik products and
versions. The same should be supplied for sitefinity releases where
significant API changes occur:
Like the previous posters, I think Sitefinity is a great product, but agree these issues are holding it back greatly. If the product tagline "Web Development Simplified" is the goal, then please increase resources assigned to documentation.