# Use more often placeholder forms in documentation topics?

**URL:** <https://meta.discourse.org/t/use-more-often-placeholder-forms-in-documentation-topics/395360>\
**Category:** Site feedback\
**Tags:** placeholder-forms\
**Created:** [February 6, 2026, 11:46am UTC](https://meta.discourse.org/t/use-more-often-placeholder-forms-in-documentation-topics/395360 "2026-02-06T11:46:24Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![pacharanero](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pacharanero/32/500583_2.png) [@pacharanero](https://meta.discourse.org/u/pacharanero)\
**Post date:** [February 6, 2026, 12:15pm UTC](https://meta.discourse.org/t/use-more-often-placeholder-forms-in-documentation-topics/395360/2 "2026-02-06T12:15:40Z")

</div>

100% agree @Canapin! I’m a big fan of the #placeholder-forms component and I use it on all my personal and business Discourses, for documentation, creating Runbooks, and for semi-automating processes which aren’t ready for a Bash script.

Here’s an example that uses a Placeholder [Publishing a Material for MkDocs site to Azure, with automatic branch/PR preview deployments - blog - Baw Medical Ltd](https://bawmedical.co.uk/t/publishing-a-material-for-mkdocs-site-to-azure-with-automatic-branch-pr-preview-deployments/763)

I’d love to see articles in #Documentation > Self-Hosting and #community-wiki:sysadmins use placeholders wherever there is some text/command to use which needs real-time customisation with user input.

---

_[View the full topic](https://meta.discourse.org/t/use-more-often-placeholder-forms-in-documentation-topics/395360)._
