# Embed additional explainer text in Form Template **URL:** https://meta.discourse.org/t/embed-additional-explainer-text-in-form-template/286250 **Category:** UX **Tags:** form-templates **Created:** [October 19, 2023, 10:40am UTC](https://meta.discourse.org/t/embed-additional-explainer-text-in-form-template/286250 "2023-10-19T10:40:56Z") **Posts on this page:** 1 **Showing post:** 16
### Author: ![Drew-ART](https://avatars.discourse-cdn.com/v4/letter/d/8edcca/32.png) [@Drew-ART](https://meta.discourse.org/u/Drew-ART) #### Post date: [November 25, 2025, 5:39pm UTC](https://meta.discourse.org/t/embed-additional-explainer-text-in-form-template/286250/16 "2025-11-25T17:39:47Z")
I built something slightly different which can be used to put composer templates on tags (or anything else). One of the use-cases is i have a `/report` tag so it can also be used as a simpler intermediary solution for this issue. For example at a tag intersection with /report/[thistypeofissue] Just a few more bugs to work out on it. > [@Url Composer Templates](https://meta.discourse.org/t/url-composer-templates/389546/3): > > Thanks for pointing that out @NateDhaliwal No, it just sniffs the url looking for a specific string and pre-fills the the composer with one of a few a templates when it finds that string. The Docus plugin puts that string into urls as one of its functions, but this component will work with any string or delivery mechanism someone wants to use, so it can stand alone. I’ll update the readme to explain that. For example, you could tell it to look for: ‘/tag/introductions’ and it would become a t… --- _[View the full topic](https://meta.discourse.org/t/embed-additional-explainer-text-in-form-template/286250)._