Most Powerful Open Source ERP

Latest ERP5 Documents

Guideline SVG Images must not have duplicate PNG image

Set correct references.
0 comment | Share: Facebook logo Twitter Logo |

Guideline Never Forget The Original Translation Can Be Bad

Always verify translations.
0 comment | Share: Facebook logo Twitter Logo |

Guideline Never Translate Without Tools Or Advice

Verify translations.
0 comment | Share: Facebook logo Twitter Logo |

Guideline Never Translate PO File Without Looking At The Application

Ambiguity and context matter.
0 comment | Share: Facebook logo Twitter Logo |

Guideline Never Translate Glossary Without Looking At Application

Ambiguity and context matter.
0 comment | Share: Facebook logo Twitter Logo |

Guideline Never Use Or Overload Reserved CSS Ids

To ensure the UI stays consistent.
0 comment | Share: Facebook logo Twitter Logo |

Guideline Never Allow Relation String Fields To Set Relations To Categories

Categories are too complex to relate.
0 comment | Share: Facebook logo Twitter Logo |

Guideline Never Set Search Row And Select Column On Listbox Inside Document View

It is not allowed in view mode.
0 comment | Share: Facebook logo Twitter Logo |

Guideline Never Show Or Make User Work With Document Id

Expose title and reference only.
0 comment | Share: Facebook logo Twitter Logo |

Guideline Document Content Should Never Contain Head Or Body Tag

Content represents the content of the body tag.
0 comment | Share: Facebook logo Twitter Logo |

Guideline Never Use Relative Url As Embedded Reference Inside SVG

SVG internal links are fragile.
0 comment | Share: Facebook logo Twitter Logo |

Guideline Images Inside SVG Must Be Embedded Using Reference Not With The Actual Image

Set correct references.
0 comment | Share: Facebook logo Twitter Logo |

Guideline Never Use Zodb Path In Url

Use front-end friendly url.
0 comment | Share: Facebook logo Twitter Logo |

Guideline Reference Should Never Use Arbitrary Numbers Or Abbreviations

Be concise.
0 comment | Share: Facebook logo Twitter Logo |

Guideline Document Content Does Not Contain $Macros

Macros introduce dependencies and reduce portability of a document.
0 comment | Share: Facebook logo Twitter Logo |

Guideline Never Log Level Info Or More In Execution Path

Avoid trivial logs.
0 comment | Share: Facebook logo Twitter Logo |

Guideline Never Commit Debugger Code

No pdb-related code (import, call to set_trace, ...).
0 comment | Share: Facebook logo Twitter Logo |

Guideline Never Create Interdependent Test Methods

It makes finding broken tests much harder.
0 comment | Share: Facebook logo Twitter Logo |

Guideline Never Hardcode Category In Scripts Or Classes

Reduces code flexibility and portability.
0 comment | Share: Facebook logo Twitter Logo |

Guideline Never Use Multiple Modules For Person Or Organisation

Use roles for classification.
0 comment | Share: Facebook logo Twitter Logo |