A difference when rendering a tiddler on its own as against rendering as part of a tab structure

If I am reading this correctly, @Bob_Jansen and @Sapphireslinger are looking to use the standard ViewTemplates within the contents of the tabs macro?

If so, you can feed the tab content through the standard ViewTemplate items. Make a new tiddler to bring in the ViewTemplate using currentTab instead of currentTiddler:

title: tab-template-test

code-body: yes

text:

<$let currentTiddler=<<currentTab>>>
{{||$:/core/ui/ViewTemplate}}
</$let>

Then use that tiddler as the template for tabs content:

<<tabs tabsList="[tag[.Grammar]]" template=tab-template-test>>

This will show the entire tiddler chrome as the tab content:

If you want to exclude the tiddler frame, title, tiddler controls, etc… make a copy of the $:/core/ui/ViewTemplate tiddler then edit it down to keep what you need. Use that as the content template:

title: tab-template-test

code-body: yes

text:

\procedure temp-exclude()
   $:/core/ui/ViewTemplate/title
   $:/core/ui/ViewTemplate/subtitle
   $:/core/ui/ViewTemplate/tags
   $:/core/ui/ViewTemplate/classic
   $:/core/ui/ViewTemplate/unfold
   $:/core/ui/ViewTemplate/lazy-loading
\end

<$let currentTiddler=<<currentTab>>>
<$list filter="[all[shadows+tiddlers]tag[$:/tags/ViewTemplate]!is[draft]] :except[subfilter<temp-exclude>]" variable="listItem">
<$transclude tiddler=<<listItem>>/>
</$list>
</$let>

The above is a quick example of only showing personal additions to the ViewTemplate tiddlers: