Most Powerful Open Source ERP

Developer Documentation

Guideline Document Should Have Explicit Predecessors And Successors Defined

To improve overall document strucute.

Guideline Documentation Document Should Have License Specified

Determining how this document may be used.

Guideline Documentation Document Anchor Uses Software And Publication Section Split By Hyphen

Documentation reference convention.

Guideline Document Title Uses Capitalized Keywords Prefixed By Publication Section

Convention for Documentation title.

ERP5 Design Philosophy

Design documents explain core principles on which the source of ERP5 is based on to ensure code is understandable and usable by everyone.