How to have a pagetemplate last longer than a page?

[AzuxirenLeadGuy]

I am using the page template described in the SILE manual. The described page template works only as the first page, and the the default document layout seems to take over from the next page onwards.

Here is the document I am using

\begin[papersize=a5]{document}
\script[src=packages/lorem]
\par

\begin[first-content-frame=leftCol]{pagetemplate}

\frame[id=gutter, width=3%pw]

\frame[id=leftCol, left=left(content), right=left(gutter),
top=top(content), bottom=bottom(content),
next=rightCol]

\frame[id=rightCol, left=right(gutter), right=right(content),
top=top(content), bottom=bottom(content),
width=width(leftCol)]

\end{pagetemplate}

\lorem[words=3000]

\end{document}

On compilation, the described layout is only present for the first page, while the default layout is present for the remaining of the 6 page document.

[Omikhleia]

Greetings

The described page template works only as the first page

I think that it is what it does by definition = changing the page template on the current page.

The \pagetemplate command is a fairly low-level construct used in some advanced use cases.

I cannot say without more context, but you might actually be using the wrong tool -- It seems to me that the masters package is what you might be looking for. It allows to define sets of frames (\define-master-template) and switch between them either temporarily or permanently (resp. \switch-master-one-page and \switch-master).

Example:

\use[module=packages.masters]
% define a named master template 'mymaster'
% It is patterned on the \pagetemplate command
\define-master-template[id=mymaster,first-content-frame=content]{
  \frame[id=content, ... your definition ...]
  \frame[id=folio, ... your definition ...]
 ... other frames possibly ....
}
% Switch to that master
\switch-master[id=mymaster]

(Unrelated, but we should put a deprecation warning on things such as \script[src=packages/lorem], it's weird to still see it used vs. the cleaner \use[module=packages.lorem] introduced more that 1 year ago...)

[AzuxirenLeadGuy]

Thank you so much. You perfectly answered what I needed.

[alerque]

We didn't add a deprecation notice to \script[src=...] because we were not removing it entirely, only de-conflating the possible uses. Anything that loads a known SILE module tipe (class, package, inputter, outputter, etc.) should use the \use[module=...] syntax, but just throwing a raw Lua script at the wall is still supported. Personally I would suggest all cases of the latter migrate to \lua[require=...] instead. I'll look into detecting specific cases and outputting a deprecation notice that points in the right direction.

[Omikhleia]

@alerque or a recommendation, if a deprecation is felt too strong? The documentation is lacking a bit here, however (#1854)

[alerque]

Not being sure whether this should be a recommendation or a deprecation is why it never got done. I'm still open to considering that point. I'm working on a PR and I think we can give pretty solid recommendations for most use cases and I'm leaning towards it being a deprecation in 0.15.0 with removal in 0.16.0 rather than just being a suggestion.

[alerque]

c.f. #1922, lets move discussion on this point there.