odoo-qweb-templates

Featured

Expert in Odoo QWeb templating for PDF reports, email templates, and website pages. Covers t-if, t-foreach, t-field, and report actions.

Data & Documents 49,938 stars 7238 forks Updated today MIT

Install

View on GitHub

Quality Score: 96/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Odoo QWeb Templates ## Overview QWeb is Odoo's primary templating engine, used for PDF reports, website pages, and email templates. This skill generates correct, well-structured QWeb XML with proper directives, translation support, and report action bindings. ## When to Use This Skill - Creating a custom PDF report (invoice, delivery slip, certificate). - Building a QWeb email template triggered by workflow actions. - Designing Odoo website pages with dynamic content. - Debugging QWeb rendering errors (`t-if`, `t-foreach` issues). ## How It Works 1. **Activate**: Mention `@odoo-qweb-templates` and describe the report or template needed. 2. **Generate**: Receive a complete `ir.actions.report` record and QWeb template. 3. **Debug**: Paste a broken template to identify and fix rendering issues. ## Examples ### Example 1: Custom PDF Report ```xml <!-- Report Action --> <record id="action_report_patient_card" model="ir.actions.report"> <field name="name">Patient Card</field> <field name="model">hospital.patient</field> <field name="report_type">qweb-pdf</field> <field name="report_name">hospital_management.report_patient_card</field> <field name="binding_model_id" ref="model_hospital_patient"/> </record> <!-- QWeb Template --> <template id="report_patient_card"> <t t-call="web.html_container"> <t t-foreach="docs" t-as="doc"> <t t-call="web.external_layout"> <div class="page"> <h2>Patient Ca...

Details

Author
sickn33
Repository
sickn33/antigravity-awesome-skills
Created
10 months ago
Last Updated
today
Language
Python
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Listed

odoo-reports

Authoring or customizing Odoo 17/18/19 QWeb reports — the printable PDF/HTML documents (invoices, sale orders, pickings, custom certificates). Use when creating an ir.actions.report, writing or inheriting a QWeb report template, adding a report.<module>.<name> parser to feed extra data, fixing paperformat / margins / page breaks, translating a report per partner language, or debugging "my changes don't show / wrong template / values undefined in the PDF". Don't guess the template id or whether a parser exists — find the existing report with the `odoo-introspect` skill first, then inherit. NOT for the dynamic financial-statement grids under Accounting → Reporting (P&L, balance sheet, tax reports) — those are the `account.report` engine: use `odoo-statutory-reports`.

5 Updated 4 months ago
tuanle96
Data & Documents Listed

html-report

Produce a report, analysis, audit, RCA, review, or summary as a standalone HTML file with ONE consistent design. Use whenever the user asks for output "as HTML" / "report html" / "bằng html" / "làm report html" / "xuất báo cáo html" / "báo cáo html", or wants an audit/review/analysis/findings rendered as a shareable HTML page instead of plain markdown. It standardizes presentation only — you still write the content. NOT for Odoo QWeb PDF/HTML business documents (invoices, pickings, certificates) — that is the `odoo-reports` skill. This is the local-tooling report layout for findings and write-ups.

5 Updated 4 months ago
tuanle96
Web & Frontend Listed

odoo-web

Building Odoo 17/18 PUBLIC web — HTTP controllers (http.route), the website (pages, QWeb website templates, snippets), the portal (/my, document access), and frontend interactivity. Use whenever writing anything under controllers/, a route an external system or browser hits, a website page/template, a portal document view, or public JS in web.assets_frontend — even if the user never says "skill". This is the PUBLIC frontend (controllers + website + portal + the v17/18 publicWidget→Interactions shift), distinct from the backend web client (that's odoo-owl). Routes run with real auth and CSRF and against real record rules — read the wiring and security from the running instance first, never guess the route, the template id, or who can reach it. Targets Odoo 17/18/19.

5 Updated 4 months ago
tuanle96