My guess at what the submitter meant is to be able to include a section in an article - manually or automatically - that says something like "other articles with the tag (some-tag-name) are listed below".

Essentially this would be the same dynamic list as produced on the page of the tag itself (https://<my-site-domain>/docs/tags/some-tag-name), but included in the body text of the article.

I think that the original submitter assumed that each article would have only one tag and that this tag would be picked up automatically, then the list of other articles generated from it. However, our use case is that articles have many tags, so the markup to generate a list of articles with a given tag would need to take a tag name as an argument; possibly similarly to the way that glossary entries are referenced: {{glossary.glossary-entry-name}}.

Convincing Gopher Thanks for your feedback. I'd like to clarify that, as a user, based on tags, you would like to list of articles in a single event ( not one by one ).

Since your example contains "page" , does it mean , there is an already created tag "X1" which has been associated with 10 articles already (for instance). Now you are creating a page (Page Name P1) which contains keywords which is "X1", then in this page P1, all the articles about X1 should be associated with this page?

So based on the content similarity and tag associations, when a page is created then all those articles with tags should be listed in this page?