🗣 Easy text-to-speech for your Gatsby site, powered by Amazon Polly.

gatsby-mdx-tts

Demo

Check out the ▶️ LIVE DEMO!

Also check out the example project repository!

Installation

npm install --save gatsby-mdx-tts

How to use

Prerequisites

1. In order to use this plugin you need an AWS account. You can use the text-to-speech service (AWS Polly) for free for the first 12 months (up to a couple million words to be precise).

   Attention: If you exceed the limits or use it after your initial free tier, using this plugin will generate costs in your AWS account! Read how you can save money by using an external cache.

2. As this is a plugin for gatsby-plugin-mdx it will only work if you have that plugin installed and configured properly as well.

Mandatory configurations

gatsby-config.js

To include the plugin just add it to your gatsby-plugin-mdx configuration in the gatsbyRemarkPlugin section. In case you have multiple gatsbyRemarkPlugins configured is very important that you put the gatsby-mdx-tts plugin to first position!

Also, you need to include a couple of mandatory configurations:

1// In your gatsby-config.js
2plugins: [
3  {
4    resolve: `gatsby-plugin-mdx`,
5    options: {
6      gatsbyRemarkPlugins: [
7        {
8          resolve: "gatsby-mdx-tts",
9          options: {
10            awsRegion: "us-east-1",
11            defaultVoiceId: "Justin",
12          },
13        },
14      ],
15    },
16  },
17],

AWS credentials

The plugin requires your AWS credentials in order to generate the text-to-speech files.

Important: For security reasons it is not a good idea to keep access keys with administrator permissions on your local machine, without at least using MFA authentication. Even better is to restrict the AWS user's permissions to AmazonPollyReadOnlyAccess, which is all this plugin needs.

There are various ways to provide your AWS credentials to the plugin. For example:

• Create a shared credentials file and add a profile for your AWS user that will use AWS Polly. You can either configure it as your default profile or use the awsProfile plugin option or AWS_PROFILE environment variable to pass the custom profile name to the plugin.

1// In your gatsby-config.js
2  {
3    resolve: "gatsby-mdx-tts",
4    options: {
5      awsProfile: "gatsby-mdx-tts",
6    },
7  },

• Use environment variables AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY to directly configure your user's access key (e.g. to build in a CI environment).

All configurations

Option	Required	Example
awsRegion	Yes	"us-east-1"
defaultVoiceId	Yes	"Justin"
awsProfile	No	"gatsby-mdx-tts"
defaultSsmlTags	No	"<prosody rate='70%'>$SPEECH_OUTPUT_TEXT</prosody>"
defaultLexiconNames	No	["LexA", "LexB"]
ignoredCharactersRegex	No	/·/
speechOutputComponentNames	No	["CustomComponent"]
skipRegeneratingIfExistingInPublicFolder	No	true

About defaultSsmlTags:

• For an overview of all supported SSML tags check out the supported SSML tags list in the AWS docs.
• The surrounding <speak> tag is added automatically.
• The variable $SPEECH_OUTPUT_TEXT will be replaced with the speech output text.

About ignoredCharactersRegex:

If your text contains special characters that should not be vocalized (e.g. fear·ful should be just read as fearful) you can use the ignoredCharactersRegex to define the characters to be ignored.

You might also want those words not to be split up during word marking. Therefore also check out Ignore word splitting characters.

About speechOutputComponentNames:

If you want to use your own component to handle the generated speech output you can specify its name using the speechOutputComponentNames option. The plugin will then use this instead of SpeechOutput to extract the text to be used for TTS generation. It is also possible to define multiple component names. Like that you can customize the way speech output is handled. Find more information about this in the customization chapter.

About skipRegeneratingIfExistingInPublicFolder:

Regenerating all the files for every cache invalidation can quickly get costly. To avoid regenerating files that are already existing in the public folder, activate this flag. Be aware that this will lead to outdated files if you change the MDX files!

Embed speech output in your MDX

After configuring the plugin you can now add the <SpeechOutput></SpeechOutput> component to your MDX files. The surrounded content will then be playable. You can add multiple speech output blocks to your content, but make sure the id is always set to an unique value over all occurrences. Also, it is important that there is an empty line between the SpeechOutput tags and the content to get it working.

1import SpeechOutput from "gatsby-mdx-tts/SpeechOutput.js"
2
3This text will be outside the speech output.
4
5<SpeechOutput id="inside">
6
7But this text will be playable. Please consider that:
8
9- The play button is added automatically.
10- The words in this text are marked one by one during text output.
11
12</SpeechOutput>

Customize

Define individual speech output parameters

To define speech output parameters for individual <SpeechOutput> components you can pass them as props. This will override the eventually configured default parameters.

Prop	Required	Example
id	Yes	"my-individual-speech-output"
lexiconNames	No	['LexA', 'LexB']
ssmlTags	No	"<prosody rate='70%'>$SPEECH_OUTPUT_TEXT</prosody>"
voiceId	No	"Hans"

Example

1<SpeechOutput voiceId="Hans" ssmlTags="<prosody rate='70%'>\$SPEECH_OUTPUT_TEXT</prosody>" id="my-individual-speech-output" lexiconNames={['LexA', 'LexB']}>

As you can see the order of the props does not matter. However, it is important to pass the props in the correct types (e.g. do not pass the lexiconNames as a string but as an array).

Play button

To customize the play button you can use the optional SpeechOutput component prop customPlayButton. Just pass in your custom play button component.

If you choose to use a custom play button component, make sure it uses the PlayButtonProps exported from this plugin.

Speech output handling

You can replace the whole speech output handling by using your own React component instead of the default SpeechOutput component. Like that, the TTS files are still generated during build phase but you can then do whatever you want with those files inside your component at runtime. To do so, use the speechOutputComponentNames configuration option (see About speechOutputComponentNames).

If you choose to use your own component, make sure it uses the SpeechOutputProps exported from this plugin.

Custom useSound hook

In case you would like to manage playing sounds by yourself you can pass an optional hook to the useCustomSoundHook prop of the SpeechOutput component. It has to follow the UseSoundHookSignature type as exported from UseSound.ts (which is the default sound hook).

Ignore word splitting characters

You might use characters that split a word into two, e.g. fear·ful. Those word parts are now marked individually by default. To avoid this, you can define the characters to ignore with the ignoredWordSplittingCharactersRegex prop.

Probably you also don't want this character to be vocalized during speech output. Therefore make sure you also configure the ignoredCharactersRegex in the plugin options.

Event listeners

To be able to react to certain events you can register the following event listeners:

onWordMarked

When a speech output is played the spoken words are highlighted in the text simultaneously. The onWordMarked listener is called as soon as a new word is highlighted and delivers the currently highlighted word as a string. When no word is highlighted (anymore) the string is empty.

Save money using an external cache 💸

Every time the internal Gatsby cache is cleared and your TTS files are regenerated AWS will bill you for it after exceeding the free tier. This can get quite expensive, especially for large projects.

To prevent this from happening too often you can use external caches. Here is a list of plugins you can use for this purpose:

• https://github.com/axe312ger/gatsby-plugin-netlify-cache
• https://github.com/axe312ger/gatsby-plugin-sftp-cache

Contribute 🦸

Contributions are more than welcome! I would love to see text-to-speech becoming a thing in the already very accessible Gatsby ecosystem. If you agree with this and would like to join me on this mission it would be awesome to get in touch! 😊

Please feel free to create, comment and of course solve some of the issues. To get started you can also go for the easier issues marked with the good first issue label if you like.

License

The MIT License

Credits

The gatsby-mdx-tts library is maintained and sponsored by the Swiss web and mobile app development company Florian Gyger Software.

If this library saved you some time and money please consider sponsoring me, so I can build more libraries for free and actively maintain them for you. Thank you 🙏

Current sponsors

A big thank you goes to the current sponsors of this library:

Andrin Meier