Preaching to the choir, my friend... I agree. Magnolia can be the best software ever, but without coherent documentation, it's next to worthless.
FYI: you can get 3.5 api documentation: google magnolia 3.5 api. However,as you mention, simple API lists won't reveal how to USE magnolia. The new config settings in the UI are another black box mystery that we've struggled with. Looks like there's all kinds of great features, but heck if we know how to apply them or what settings they require without considerable trial and error. Mike D. Jones > -----Original Message----- > From: [email protected] [mailto:[EMAIL PROTECTED] > Sent: Thursday, February 07, 2008 7:41 AM > To: [email protected] > Subject: [magnolia-user] A bit worried about Magnolia > > Dear Magnolians > > Am I the only one that is a bit worried about the state of Magnolia? > > While the development work that we see is fabulous, the documentation > lags _far_ behind. > > - Did you know, that a new tag library was introduced with Magnolia > 3.5? I'm sure it does slick things, but we will never find out about > them unless we trip over them by accident. > > - By know you probably have heard, that the access control to pages/ > URLs has bin completely modified in 3.5 - but do you know how things > really work? > > - When you visit documentation.magnolia.info it tells you that the > current release is 3.0, also the API linked there is the one from > 3.0. The last update seems to be from May 25th. > > - The new Wiki is a mess. It has no structure at all so it is nearly > impossible to browse through articles to find out what is documented > and what not. On top of that "hopefully we receive a license in the > next week" has been greeting us from the front page for a month now. > > MY GOAL IS NOT BASHING THE MAGNOLIA TEAM. As I said: They are doing a > terrific job developing Magnolia. I just wanted to emphasize that not > investing in documentation will not help at all in the long run. > > As I said before on- and off-list: I am more than happy to help > documenting things. But I would need the following before I get > started: > - Specific task: What should I document, what is taken care of by > others? > - Contact: Who can I contact when I have questions? > - Place + access: Where should I document + how? Wiki, > documentation.magnolia.info, other? > > The Magnolia developer have delivered the basis for blowing away > other CMS - if we don't deliver the missing documentation to it, the > world will not be able to honor the hard work of the developers! > > Amen! > > And now... back to work. > > Cheers, > Will > > ---------------------------------------------------------------- > for list details see > http://documentation.magnolia.info/docs/en/editor/stayupdated.html > ---------------------------------------------------------------- ---------------------------------------------------------------- for list details see http://documentation.magnolia.info/docs/en/editor/stayupdated.html ----------------------------------------------------------------
