Plugins overview

Drop-in components that get you a working Yatmo integration without writing API calls. Start with the iframe plugin on any site; use the JavaScript plugins when you need more control; or pick the plugin made for your CMS, framework or no-code tool and keep your usual workflow.

Iframe (recommended starting point)

• Iframe plugin: one <iframe>, configurable via URL parameters. Display a map, a summary, both side-by-side, scores, or a stacked variant. Easiest possible integration, no JavaScript required. Every platform plugin below embeds this one.

JavaScript plugins

• JavaScript Map: interactive map, single config object + one script tag.
• JavaScript Summary: table of nearby POIs with distance & travel time.
• JavaScript Summary-as-text: narrative paragraphs you can place anywhere.
• npm packages: @yatmo/elements (one HTML element, no framework), @yatmo/react and @yatmo/vue (React and Vue components), @yatmo/astro, @yatmo/nuxt and gatsby-plugin-yatmo, @yatmo/maps (the plugins above from a bundler project) and @yatmo/sdk (the typed API client for Node and edge servers).

Real estate search

Search features for portals and agencies, built into the JavaScript Map plugin: search by travel time from an address, draw the search area on the map, lifestyle search (minutes from work, near a school, near a given metro line), and the display of your listings on the map with the search area. Yatmo computes the area, your backend filters the listings. Start with the overview and flow.

Advanced features

Optional configuration the iframe, JS Map and platform plugins all expose: isochrones, favorite addresses, map styles, route from origin, full-screen mode.

Plugins for your CMS, framework or no-code tool

The same map, nearest places and indexable neighbourhood text, packaged for the tool you already use: the key and the defaults are set once in its settings, the pieces are placed from its editor or its templates, and the neighbourhood text is rendered on the server for search engines. Each one is published on the platform’s own marketplace or package registry and mirrored on github.com/Yatmo.

WordPress

• WordPress plugin: the iframe plugin as a block and a shortcode [yatmo-map], with the options set in the WordPress admin.
• WordPress neighbourhood text: the neighbourhood description as indexable HTML, block and shortcode [yatmo-text], in the same plugin.

Odoo

• Odoo module: the iframe plugin and the indexable neighbourhood text as website building blocks and QWeb templates, with the defaults set in the Odoo settings.

Drupal

• Drupal module (drupal.org/project/yatmo_map): the iframe plugin and the indexable neighbourhood text as blocks on your property content type and as field formatters of a Geofield, with the key and the defaults in a settings page. Drupal 10.3 and 11.

TYPO3

• TYPO3 extension (yatmo_map on TER, composer require yatmo/typo3-yatmo-map): three Fluid ViewHelpers, <yatmo:map>, <yatmo:pois> and <yatmo:text>, with the key and the defaults in the extension settings and the text rendered on the server and cached. TYPO3 12.4, 13.4 and 14.

Webflow, Wix, Squarespace, Framer, Bubble

• No-code tutorial: the map, the nearest places and the neighbourhood text in an Embed element fed by your CMS fields (address or coordinates), with an embed code generator. No backend, no developer.
• Framer plugin: the same three pieces as code components with property controls, inserted by a plugin and bound to CMS fields.
• Bubble plugin: three visual elements fed by an address or coordinates from your database.

Laravel and Symfony

• Laravel package yatmo/laravel (Composer): <x-yatmo-map>, <x-yatmo-pois> and <x-yatmo-text> Blade components, keys in .env, a Yatmo facade for the rest of the API, the neighbourhood text rendered on the server and cached. Laravel 10 to 13, built on yatmo/yatmo-php.
• Symfony bundle yatmo/symfony-bundle (Composer, Flex recipe): Twig functions yatmo_map(), yatmo_pois() and yatmo_text(), keys in .env, a Yatmo service for the rest of the API, the text cached in the application cache pool, the language following the request locale. Symfony 6.4 to 8, built on yatmo/yatmo-php.
• Other stacks: the typed clients for Python, .NET, PHP and Node, and the mobile SDKs.

n8n

• n8n community node n8n-nodes-yatmo: the Yatmo node in your automations (neighbourhood summary and text as HTML, listing enrichment, scores, geocoding, isochrones, routes, static map image) with a credential holding your backend key. Enrich every new listing from a CRM or portal feed, generate the neighbourhood paragraph on publication, score a portfolio nightly.