We are going to try jump starting this project again. I need everyone who intends to continue working on this project to respond to this forum message with their intentions.
Thanks,
Bryan
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi everyone
Nice to have a sound-off once in a while.
This might remind developers who forget that the project is still around. :D
Thanks Bryan for adding me.
Anyway, lets get to the point.
I am not a pro in php but have been developing sites since the past 2 years or so. Listed below are a few thoughts of mine.
1.) Packages like CakePHP and Symfony have a lot of docs and guides, but they are tough to use too. No noob in PHP can get started with that quickly. If they find something easier to use then they might look above those well-known frameworks. So keep the whole thing simple.
2.) Docs and Guides must be inhouse on the package's site. I see many packages don't offer docs in PDF format or Windows Help Format or in anyother downloadable format. They only offer an online version of the docs. This sometimes downgrades the package. Example: Mootool (a JS toolkit) doesn't offer online docs. Many users are making their downloadable version of the docs with content from the main docs site, by re-packaging it in chm or pdf format. Prototype(another JS toolkit) offers good, downloadable docs.
3.) I remember someone once said "Documentation is like sex. If its good, its too good. If its bad, just have it. Because something is better than nothing". But lets go the angel way. Lets have clear docs for users. Again sighting the example of Mootools and Prototype. Mootool's docs are pro-developer friendly. Prototype's docs are neatly tailored with code samples that can make even a newbie a pro with the toolkit!!! Now thats the kind of docs that users want.
4.) Messing with these MVCs for a few months, I have noticed one thing. Users look for add-ons. Suppose I am developing a site and I need an MVC-kit that's easier to use and after taking all the factors mentioned in the above points into consideration, I would choose over a package that has many add-ons that ease my work.
Any comments? Anyone else... please add to this list if you have any ideas...
Hey is anyone's got any ideas for this one just post them below and as Burnin says also please respond to this sound-off if you are still on with this project.
--
akash
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I just have 1 year 3 months in php/mysql.. But I have confident that I can able to understand the flow if I work under an experienced person.. To put it simple.. My contribution may be such as.. project Documentation, testing.. So that I can learn a better.. Is that ok? Where shall I start?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello everyone,
We are going to try jump starting this project again. I need everyone who intends to continue working on this project to respond to this forum message with their intentions.
Thanks,
Bryan
Hi everyone
Nice to have a sound-off once in a while.
This might remind developers who forget that the project is still around. :D
Thanks Bryan for adding me.
Anyway, lets get to the point.
I am not a pro in php but have been developing sites since the past 2 years or so. Listed below are a few thoughts of mine.
1.) Packages like CakePHP and Symfony have a lot of docs and guides, but they are tough to use too. No noob in PHP can get started with that quickly. If they find something easier to use then they might look above those well-known frameworks. So keep the whole thing simple.
2.) Docs and Guides must be inhouse on the package's site. I see many packages don't offer docs in PDF format or Windows Help Format or in anyother downloadable format. They only offer an online version of the docs. This sometimes downgrades the package. Example: Mootool (a JS toolkit) doesn't offer online docs. Many users are making their downloadable version of the docs with content from the main docs site, by re-packaging it in chm or pdf format. Prototype(another JS toolkit) offers good, downloadable docs.
3.) I remember someone once said "Documentation is like sex. If its good, its too good. If its bad, just have it. Because something is better than nothing". But lets go the angel way. Lets have clear docs for users. Again sighting the example of Mootools and Prototype. Mootool's docs are pro-developer friendly. Prototype's docs are neatly tailored with code samples that can make even a newbie a pro with the toolkit!!! Now thats the kind of docs that users want.
4.) Messing with these MVCs for a few months, I have noticed one thing. Users look for add-ons. Suppose I am developing a site and I need an MVC-kit that's easier to use and after taking all the factors mentioned in the above points into consideration, I would choose over a package that has many add-ons that ease my work.
Any comments? Anyone else... please add to this list if you have any ideas...
Hey is anyone's got any ideas for this one just post them below and as Burnin says also please respond to this sound-off if you are still on with this project.
--
akash
I just have 1 year 3 months in php/mysql.. But I have confident that I can able to understand the flow if I work under an experienced person.. To put it simple.. My contribution may be such as.. project Documentation, testing.. So that I can learn a better.. Is that ok? Where shall I start?