Hi! > I, for one, could help out in writing a new tutorial section for the > website, give the chance for it.
This is an great proposal, and of course having better tutorial is always great. I would recommend though starting with a plan for the tutorial - i.e., what it would cover, etc. - like table of contents, with short description of each item, so we agree on what is going there. Once we have a good plan we could take it from there and maybe also solicit help for particular topics/chapters. > world.', have tutorials that speak > about how you can write things to error_log, use xdebug, get things > from DB, put things to DB, > promote APC as a must (and many people still don't know that APC is > not just opcode cache!!!) I would rather stay away of defining specific extensions or ways to do things as "a must". There are many ways of doing things, and many solutions depending on particular setup and use case. For example, I think in generic tutorial would be better to explain how caching works, what are data caches, bytecode caches, page caches, etc., how one uses them, and then use APC as an example of the implementation. Just saying "APC is a must" it not really a correct approach - there are times where APC is not the right solution, and there are other implementations for both bytecode and data caching. > have tutorials about rest interfaces or SOAP calls or what not, things > that people do every day > and need them. Have a section where you talk about various frameworks I think content on SOAP belong to SOAP part of the manual - where SOAP extension, etc. lives. Of course, generic tutorial can explain what webservices are and refer to particular parts of the manual for specific ones. > to one, have a section that talks about ORMs, pros and cons, get some > love for PHP FIG group > and their efforts in standardizing stuff out. Have a section where you What FIG is standardizing is a nice work but I do not think php.net should be promoting any specific code style or API or such. We can have a reference to FIG work as an example of a standard that organization could use for their best practices, but I do not think we should prescribe it and make an impression this is the only right way. > I'd really love to type a tutorial to guide newbs to DB usage instead > of going on stackoverlow and > respond to the same question over and over and over again ;) "DB usage" is a very broad topic. Specific advice would depend a lot on what your requirements are, what your environment is, what you actually need to do with the db, etc. If you just need basic CRUD - any SQL tutorial plus mysqli manual pages will do it for you. If you need something more - please define what is that more. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227
