04/08

Avrei questa idea

Giffoni Innovation Hub

WordPress in front. Odoo behind.

Role

Moved Avrei questa idea onto Odoo 18 behind its WordPress site: a connector plugin, a custom Odoo addon with its own REST API, one sign-in across both and a repeatable migration of the old data, with editors still building pages in WPBakery.

In numbers

REST endpoints in one Odoo addon: 50+
shortcodes bringing Odoo into WordPress: 35+

Problem

Giffoni Innovation Hub’s platform, Avrei questa idea, needed its people, projects and contest entries in Odoo 18, without taking editors away from the WordPress and WPBakery pages they build.

Constraints

Odoo 18 holds the people, projects and contest entries
Editors keep building pages in WordPress and WPBakery
People sign in where they always have, on WordPress
The old data moves across without being retyped

Decisions

A WordPress connector plugin on one custom Odoo addon and its REST API.
WordPress renders the pages, and the plugin’s shortcodes bring Odoo’s profiles, projects and forms into them.
WordPress checks the sign-in, and Odoo trusts it through a signed token exchange.
People sign in once. Odoo finds or creates their account and issues its own token, and its pages open inside WordPress with a one-time ticket.
A repeatable migration: restore the production data, upgrade the addon, turn the old author records into Odoo users, then check the result.
It runs the same way on every fresh copy of production, so nothing is copied by hand.
Company profiles next to personal ones, with collaborators and an approval step.
Companies take part as themselves, and their teams join under them.

Outcome

Launching at avreiquestaidea.it: editors publish in WordPress while Odoo 18 holds the people, projects and contest behind it, with AI help for drafting an idea’s logline, synopsis, treatment, storyboard and poster.