Can we use include tag for our use case?

[kavin2208]

We have an use case where we use capture block to define some content in a markdown file and then use include tag to refer that markdown file once , then continue to use the capture block names as variables to render the content wherever we need within that markdown file. I observed that this works only with Include tag and it's not working with Render tag. Also, saw that render tag specifically controls what level of parent variables are exposed to the referenced markdown context.

My major question: Will Liquidjs continue to support Include tag or should we create our own custom tag for this use case? Because I saw that Include tag is deprecated. Any help will be appreciated.

Our use case for better understanding:

shared/partials/content.md:

`{% capture content-reuse-prerequisites-node-version %}
Ensure Node.js 18.x or later is installed on your machine. Run node --version
in your terminal to verify. If you need to upgrade, use nvm to manage multiple
Node.js versions without affecting other projects.
{% endcapture %}

{% capture content-reuse-prerequisites-cli-setup %}
Install the SFDocs CLI globally:
npm install -g @salesforcedocs/cli
Verify the installation by running:
sfdocs --version
The CLI provides commands for previewing, validating, and publishing your documentation.
{% endcapture %}
`

content-reuse.md

`{% include "shared/partials/content-reuse-prerequisites.md" %}

{{ content-reuse-prerequisites-node-version }}
{{ content-reuse-prerequisites-cli-setup }}
`

[harttle]

It is deprecated and may be removed in the future, but not before v12. Currently we are still working on v11 thus it’ll be there for a longer time as it doesn’t cause problems as in the Ruby version.

…

On Mon, 13 Jul 2026 at 6:13 PM, kavin2208 ***@***.***> wrote: We have an use case where we use capture block to define some content in a markdown file and then use include tag to refer that markdown file once , then continue to use the capture block names as variables to render the content wherever we need within that markdown file. I observed that this works only with Include tag and it's not working with Render tag. Also, saw that render tag specifically controls what level of parent variables are exposed to the referenced markdown context. My major question: Will Liquidjs continue to support Include tag or should we create our own custom tag for this use case? Because I saw that Include tag is deprecated. Any help will be appreciated. Our use case for better understanding: shared/partials/content.md: {% capture content-reuse-prerequisites-node-version %} Ensure Node.js 18.x or later is installed on your machine. Run node --version` in your terminal to verify. If you need to upgrade, use nvm to manage multiple Node.js versions without affecting other projects. {% endcapture %} {% capture content-reuse-prerequisites-cli-setup %} Install the SFDocs CLI globally: npm install -g @salesforcedocs/cli Verify the installation by running: sfdocs --version The CLI provides commands for previewing, validating, and publishing your documentation. {% endcapture %} ` content-reuse.md `{% include "shared/partials/content-reuse-prerequisites.md" %} Content Reuse Prerequisites {{ content-reuse-prerequisites-node-version }} {{ content-reuse-prerequisites-cli-setup }} ` — Reply to this email directly, view it on GitHub <#934?email_source=notifications&email_token=ABBZBRXDM2XG6NEDNUVPUD35ESY6HA5CNFSNUABBM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63RPGEYDIMJZGE3TFJTSMVQXG33OVJZXKYTTMNZGSYTFMSSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABBZBRSXHM5GTB7CK2IBVQ35ESY6HAVCNFSNUABHKJSXA33TNF2G64TZHM3DCMBRGY4DIMZ3IRUXGY3VONZWS33OHMYTANBRHEYTOMVBOYBA> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/ABBZBRVROQSTJB2AHBICY7D5ESY6HA5CNFSNUABBM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63RPGEYDIMJZGE3TFJTSMVQXG33OVJZXKYTTMNZGSYTFMSSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android <https://github.com/notifications/mobile/android/ABBZBRTOUI75SWTW7W7PJAD5ESY6HA5CNFSNUABBM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63RPGEYDIMJZGE3TFJTSMVQXG33OVJZXKYTTMNZGSYTFMSSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. Download it today! You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[kavin2208]

Thanks for the quick response !! Any timelines on when we can expect v12?

[harttle]

not yet, at least one year after.

…

On Mon, 13 Jul 2026 at 7:14 PM, kavin2208 ***@***.***> wrote: Thanks for the quick response !! Any timelines on when we can expect v12? — Reply to this email directly, view it on GitHub <#934?email_source=notifications&email_token=ABBZBRQKWWHIFP4ZJCYRKJT5ES773A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZWGIYTKOBRUZZGKYLTN5XKOY3PNVWWK3TUUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-17621581>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABBZBRQPOUI7EPHJITMAEBT5ES773AVCNFSNUABHKJSXA33TNF2G64TZHM3DCMBRGY4DIMZ3IRUXGY3VONZWS33OHMYTANBRHEYTOMVBOYBA> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/ABBZBRWMPQZD7MOGEEASRBT5ES773A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZWGIYTKOBRUZZGKYLTN5XKOY3PNVWWK3TUUVSXMZLOOSVGM33PORSXEX3JN5ZQ> and Android <https://github.com/notifications/mobile/android/ABBZBRXRTHBBOF25LR7S75T5ES773A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZWGIYTKOBRUZZGKYLTN5XKOY3PNVWWK3TUUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>. Download it today! You are receiving this because you commented.Message ID: ***@***.***>