How psmiguelvazquez/proper works
Project type and purpose
• This is a collection of Odoo “addons” (modules). Each top-level folder (e.g. account_move_proper, carta_porte, sale_purchase_confirm, etc.) is a self-contained Odoo module that plugs into the core Odoo server.
• The purpose is to extend and customize Odoo’s accounting, sales, stock, CRM and other business flows by defining new models, views, wizards, security rules, data files and static assets.
File structure
• __manifest__.py – module metadata and dependencies
• models/ – Python classes extending Odoo’s ORM (model definitions, method overrides)
• views/ – XML definitions for forms, trees, kanban, reports
• wizard/ – Python + XML for multi-step dialogs
• security/ – access control CSVs, record-rules, groups
• data/ – initial data or sequences
• static/ – JavaScript widgets, CSS, images
• controllers/ – HTTP route handlers for web endpoints
• Common patterns: MVC (models + views + controllers), plugin architecture (each module injected at startup), layered business-logic (wizards, helpers, reports).
README
• The README (“# proper”) is minimal and only labels the project. All architectural information must be inferred from the file tree and standard Odoo conventions.