Widgety API
Widgety integration experience formed part of the custom development delivered during Duffion’s approximately five-year AdventureSmith engagement.
Where the engineering matters
The integration work belonged to an established travel website inherited from Noble Studios. It sat alongside custom frontend loaders, major hand-coded refactors, and new ACF-backed blocks rather than replacing the whole engagement with a single API feature.
Work represented in the portfolio
- Widgety integration within the inherited AdventureSmith website
- Custom frontend loading behavior
- Related block and editing-handler development
The case study records the historical performance improvements across the broader engagement. Those Lighthouse gains are not attributed solely to Widgety. The later solo nine-month rebuild was completed in a separate full-time developer role at AdventureSmith.
Widgety integration experience: planning a similar project
A travel-content integration has to fit the site’s existing publishing and browsing experience. Describe where third-party content appears, what editors still control and what visitors should see while content loads. AdventureSmith is the documented example in this dossier. Its broader refactoring and performance work had several contributors and causes; the case does not attribute those results to one API connection.
For a new project or changes to an existing system, explore custom API integration services.