Why is it that every time someone comments of the insufficient
documentation you Cake veterans jump in and say something along the
lines "so make it better"?

Well, guess what, there is a catch - anyone who actually NEEDS the
documentation is not in a position (yet) to contribute to it. And
anyone who knows enough about Cake to contribute to the documentation
can't REALLY see why the documentation is lacking.

Let's face it, like with any other framework/platform/language, it
looks totally different from the perspective of a total newbie to what
it looks like to someone who already comfortable with it. Over time,
when we gain knowledge and things become familiar, we tend to,
naturally, diminish the importance of documenting every little detail
and we don't understand what the newbies are complaining about when
they say they are totally lost in the documentation. That's the way it
usually works.

The only way to make any progress in this front is for the new comers
to express their problems and concerns in constructive manner and for
the Cake developers and veterans to listen to these problems and
complaints and think how to address them. There is no other way.

There is theoretically nothing wrong with saying "if you don't like
the documentation, help to make it better" but it doesn't really help
the newbie who may be raising a valid point and it doesn't help Cake
to bring new people into the community. And an active and thriving
community is essential to any project of this kind.

So please don't take it personally, all of us appreciate the hard work
that is being done both on the code and documentation but looking
through the eyes of a total newbie, the documentation is...well, can
be frustrating at times.

Cheers.
- barduck





On Mar 2, 9:21 pm, "nate" <[EMAIL PROTECTED]> wrote:
> Great, I'll take that as you voulenteering to fix it.  You can contact
> the documentation lead at psychic at cakephp dot org.
>
> On Mar 2, 1:54 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> wrote:
>
> > If you are going to continue developing with cakePHP get used to this.
> > I love cakePHP for a lot of things, but this community has some
> > terrible documentation.
>
> > skatona wrote:
> > > oh man, thank you.  I've been going crazy thinking that they wouldn't
> > > possibly let something like that slip by, so have been staring at each
> > > and every individual character in my code to see what I messed up.
> > > Over and over.
>
> > > Thanks a ton!
>
> > > On Mar 1, 2:30 pm, "bernardo" <[EMAIL PROTECTED]> wrote:
> > > > You are right. There is a bug in the code used in the screencast. I
> > > > think the problem is that edit.thtml is copied from add.thtml but
> > > > forget to include the line  <?php echo $html->hidden('Post/id'); ?> so
> > > > the id is not posted and the controller ends adding a new post. The
> > > > code in the manual is correct though.
>
> > > > I wonder how nobody noticed this before...
>
> > > > On Mar 1, 1:41 pm, "skatona" <[EMAIL PROTECTED]> wrote:
>
> > > > > I must be losing it.
>
> > > > > I'm a veteran php web developer and a friend said cakephp was awesome
> > > > > so I've checked it out and gone through a couple screencasts.  Am I
> > > > > crazy, or is the Blog Tutorial screencast wrong?  More specifically,
> > > > > the Edit functionality does NOT edit a post.  It merely Adds one.
>
> > > > > Watch the screencast again.  You click Edit, it brings up the Title
> > > > > and Body textboxes with the information from that post, but when you
> > > > > edit it and save - it just creates a new post!  I thought Edit meant
> > > > > "change", not "give me the info so I can use it in another NEW post".
>
> > > > > Someone please help me out here.
>
> > > > > -Shaun


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cake 
PHP" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to