tips-and-tricks with best-practices

thread: 2 messages  |  last: about 3 years ago  |  started: sunday, july 27, 2008, 5:35 pm pdt


#1  |  activeserver (India)
Sunday, July 27, 2008, 5:35 PM PDT

Hi all,

would it make sense to add a subsection to “Tips-and-Tricks” to list out “Best Practices” in QCodo development as well as deployment?

Reasoning:
I personally feel that if a document of this nature is publicly available it shows the technical maturity of the project as such. IMO, QCodo is not marketed corresponding to its capabilities.
Just in case someone feels that to be counterintuitive, I must say that I feel the more newcomers that read and try out QCodo, the more they will use it and inevitably, the more support requests will be generated. See the posting trend, here on the forums, after the “revival” of Q/ZCodo :-)
My two cents of “marketing expertise” ;-)

So,
Qcodo (+QDrupal maybe) development best pratices - aimed at productivity and learning
Qcodo (+QDrupal maybe) deployment best pratices - aimed at security and scalability.
Agreed security comes in development, so we just write that on the first page and ask the user to read both, before designing his final/live system.

Criticisms, suggestions, ideas welcome :-)

#2  |  VexedPanda (Calgary, AB) Canada
Monday, July 28, 2008, 10:54 AM PDT

If any QDrupal documentation is done, it will be kept on the QDrupal project pages, and not mentioned in any main QCodo documentation.

If you've got some ideas for what to put up, feel free to start. The nice thing about a Wiki is that if anyone disagrees at a later time, they can change it. :)



Copyright © 2005 - 2012, Quasidea Development, LLC
This open-source framework for PHP is released under the terms of The MIT License.