Forums / Suggestions / Best practice for extension development

"Please Note:
  • At the specific request of Ibexa we are changing this projects name to "Exponential" or "Exponential (CMS)" effective as of August, 11th 2025.
  • This project is not associated with the original eZ Publish software or its original developer, eZ Systems or Ibexa".

Best practice for extension development

Author Message

Tony Wood

Thursday 15 May 2003 9:02:38 am

It would be nice if eZ could chair a best practice forum or document that would outline best practice for extension development.

Things to cover:
db: table naming
db: Field naming

code: variable naming convention
documentation: minimum required

This would ensure that all contributions can be at a basic level can be understood and pitch up and developed by anyone who understands extension.

Comments?

Tony Wood : twitter.com/tonywood
Vision with Technology
Experts in eZ Publish consulting & development

Power to the Editor!

Free eZ Training : http://www.VisionWT.com/training
eZ Future Podcast : http://www.VisionWT.com/eZ-Future

roland benedetti

Sunday 25 May 2003 10:19:15 am

I do agree !

I also can't see where to put my development in the file structure, which API's to use ....

I'd need a tutorial "building an extension".

also, Why not making a kind of extension repository ?
this way, one could contribute to non kernel but important features.