Integrate once
Manage content centrally in Verbison

Your website stays in its existing CMS. The planned Universal JavaScript connects it to Verbison, bringing scripts, languages, voices and approved recordings into a shared management workflow.

The integration approach · illustrative view
Your website
your-website.example
FEATURES & IDEASGood stories have a voice
Listen to this article
Verbison
Universal JavaScript
<script
  src="…/verbison.js"
  data-site="your-site-id">
</script>
ContentLanguageAudio

Planned integration. We agree the technical approach for your website.

Your website and Verbison
A common path to audio

This explains the integration approach. We establish production code, content assignment and publication arrangements for your website during the trial.

  1. Website

    The article or information page stays in your CMS.

  2. JavaScript

    A common integration connects your website to Verbison.

  3. Site ID

    An identifier connects the website to its relevant content.

  4. Approved audio

    The player offers the assigned, approved recording.

A shared connection
Across different websites

A website, a script and a site ID connect content to its audio edition. This illustration explains the product approach; the actual setup is agreed with your technical contact during the trial.

Start with the CMS you have

Convenience integrations are intended to make setup easier within each system. They connect to the same audio platform, rather than creating a separate product for every CMS.

Universal JavaScript

The planned shared approach for CMS platforms and custom websites. The trial covers placement, page matching and technical requirements.

Shopware

A future convenience integration for guides and editorial store content. Scope and compatibility will be defined with the integration.

Shopify

A future convenience integration for blog posts, guides and information pages within your store.

API

Planned access for custom publishing workflows. A public interface will come with a documented product contract.

Put play next to the story

A well-placed player is easy to find and leaves room for the article. It offers the prepared recording while text, images and references remain on the page.

Alongside the article

An editorial page may work well with audio after the headline or introduction. Review the placement using your actual sample page.

Across screen sizes

The player should be clear to use on phones and desktops. Discuss page layout, available space and keyboard access as part of setup.

One sample page
A practical integration plan

Start with your website address and CMS. Together, we agree the content, possible languages, placement and technical approach for your trial.

Integration questions

Do I need to rebuild my website?

A complete rebuild is not the product approach. The planned JavaScript integration complements your existing website. We examine requirements, placement and technical constraints in your system during the trial.

Where does the player appear?

The player is intended to sit with the selected content, for example below the title or before the article text. Placement and presentation are agreed for your website; the illustration above explains the approach.

Does Verbison work with Shopware and Shopify?

Universal JavaScript is the shared foundation. Shopware and Shopify are planned as future convenience integrations. We establish what your specific website can support during the trial; finished CMS apps are not offered here.

What happens when a page changes?

A change can affect the script, translations and recordings. The central approach is intended to keep these versions connected. We agree when to reproduce, review and republish them during your trial.

Ready to
be heard?

Bring a page that matters to you. Let’s discover how your content sounds.