I would like to offer to contribute to the documentation of Cake 1.2
I have been putting off working with 1.2 for various reasons, so don't
know much about it yet. However I expect that I can help at least
with proof reading, tidying up etc initially. It is also a good
excuse for me to start learning about 1.2
Any suggestions on what I could start on?
I don't have a lot of time to contribute at the moment, but hope that
I can add some value anyway.
Regards,
Langdon
Langdon,
Check out our wiki on Cakeforge:
http://cakeforge.org/plugins/wiki/index.php?id=53&type=g
Pick a section you can work on and let me know.
-- John
> Check out our wiki on Cakeforge:
>
> http://cakeforge.org/plugins/wiki/index.php?id=53&type=g
>
> Pick a section you can work on and let me know.
Looking at the list in the Wiki I am at a bit of a loss. If I had to
pick something it would be "Data Sanitization" as the notes mentions
that it is "same as current".
I don't know what needs doing, but it sounds like it is probably the
sort of job I am up to at the moment (in terms of knowledge and
time :-)
Regards,
Langdon
Great - what we need there is just someone to take the existing
content here:
http://manual.cakephp.org/chapter/sanitize
And rework it for
1. Accuracy
2. Typos, wordiness, and general readability
Just polish it a bit for 1.2 and send it my way. I'll check back with
you in a week or so.
Many thanks,
John
Sorry I missed you on IRC. Took a break to make breakfast.
> Great - what we need there is just someone to take the existing
> content here:
>
> http://manual.cakephp.org/chapter/sanitize
>
> And rework it for
>
> 1. Accuracy
> 2. Typos, wordiness, and general readability
>
> Just polish it a bit for 1.2 and send it my way. I'll check back with
> you in a week or so.
No worries, I will work through it and see how I go. How should I
deliver the finished result to you?
Regards,
Langdon
> No worries, I will work through it and see how I go. How should I
> deliver the finished result to you?
Whatever is easiest for you. Plain text, email, Open-office-
friendly.... whatever. :)
-- John
Thanks John, plain text is probably my preference. I will see how I
go.
Langdon