Template-driven output
Use one design system while rendering article-specific audio across templates.
Bricks Integration
Use WPVoicer audio in Bricks dynamic templates.
WPVoicer can fit into Bricks-based publishing stacks where post-level dynamic content and front-end consistency are priorities.
How the Bricks integration works
WPVoicer exposes the generated post audio as Bricks dynamic data. If intro/outro text is enabled in the plugin, it is included in the final MP3 before Bricks renders it. That lets you build one Bricks template and have every article render its own audio file automatically.
Generate audio for the article
Create the audio from WPVoicer first. The plugin saves the generated MP3 as post-level audio metadata.
Open the Bricks template
Edit the Single Post template or the reusable section where the article audio should appear.
Insert the dynamic tag
Use {wpvoicer_audio_url} in URL fields, audio source fields, links or custom markup. Use {wpvoicer_audio_id} only when the element expects the attachment ID.
Render and style the output
Bricks resolves the tag for the current post, while you control layout, spacing and visual treatment in the builder.
Primary tag{wpvoicer_audio_url} returns the generated MP3 URL.
Optional tag{wpvoicer_audio_id} returns the WordPress Media Library attachment ID.
FallbackUse [wpvoicer_audio] in a shortcode element when you prefer the plugin player.
Technical note: the plugin registers Bricks dynamic tags and also replaces these tags inside rendered content, so they work in template fields and supported text output.
Fast publishing flow
Generate audio in plugin and reuse it in Bricks without custom API handling.
FAQ
Bricks implementation questions.
How to use WPVoicer audio values inside Bricks templates.
Which Bricks tag returns the MP3 URL?
Use {wpvoicer_audio_url} in URL fields, source fields, links or custom markup.
When should the ID tag be used?
Use {wpvoicer_audio_id} only when the Bricks element expects the WordPress Media Library attachment ID.
Does one template work across many posts?
Yes. Bricks resolves the tag from the current post context, so each article can render its own generated audio.
Is there a shortcode fallback?
Yes. Use [wpvoicer_audio] in a shortcode element if that is simpler for the layout.