that is pretty much what the bakery is.
On Apr 14, 6:23 am, xbase [EMAIL PROTECTED] wrote:
Why don't we first develop our own wiki utilizing cake then start
plugging in content to the wiki afterwords?
--~--~-~--~~~---~--~~
You received this message because you
One of your points is that information is quickly out of date - I
totally agree, and I think with that in mind on the bakery there
should be some element of editorial control and natural churn on
articles.
For example, how many recent articles are still using $html-input?
Maybe when 1.2 is more
On 4/13/07, digital spaghetti [EMAIL PROTECTED] wrote:
For example, how many recent articles are still using $html-input?
Maybe when 1.2 is more advanced, say beta, start taking these articles
The applicable version is shown in the sidebar so I guess it is not so
much of an issue...
We can
Why don't we first develop our own wiki utilizing cake then start
plugging in content to the wiki afterwords?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups Cake
PHP group.
To post to this group, send email to
On 4/12/07, savagekabbage [EMAIL PROTECTED] wrote:
I'm going to attempt to create user-friendly documentation for
developers who are new to CakePHP. I think a resource like this would
be a great help for new developers, and it's a shame they took down
the old wiki.
If I remember correctly,
Yes, that's exactly why it was taken down. However, while CakePHP has
a lot of documentation on the web, the API, and the forums... Most of
it is too hard to grasp or too steep for newbies to handle. There are
countless newbies who have/have had trouble learning the framework
(including myself)
On Apr 12, 2007, at 3:04 PM, savagekabbage wrote:
Yes, that's exactly why it was taken down. However, while CakePHP has
a lot of documentation on the web, the API, and the forums... Most of
it is too hard to grasp or too steep for newbies to handle. There are
countless newbies who
