You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Creating Pages section shows a sample which works correctly; however, if you modify it slightly by changing the level, the info layout does not appear in the generated HTML. For example, change from level 0 to level 1:
== Sample Page
:page-layout: info
However, if I move page-layout to the top, then the info layout works. For example:
:page-layout: info
== Sample Page
I don't usually start my pages off with an attribute, so I am not sure if this is a bug or my lack of understand. I did not see a related issue. Thanks.
The text was updated successfully, but these errors were encountered:
You are describing the behavior perfectly. The page-layout must be defined in the document header. That either means putting it below the document title (the single equals sign) or at the top of the document (an implicit document header).
Think of the document header as a replacement for the front matter. Perhaps this could be better explained in the README. I'm open to suggestions for improved wording.
Page variables must be defined in the document header. That means putting them below the document title (the single equals sign as shown in the sample) or at the top of the document for an implicit document header (such as two equal signs). For more details on the document header, see http://asciidoctor.org/docs/user-manual/#doc-header in the User Manual for details.
The Creating Pages section shows a sample which works correctly; however, if you modify it slightly by changing the level, the
info
layout does not appear in the generated HTML. For example, change from level 0 to level 1:However, if I move
page-layout
to the top, then theinfo
layout works. For example:I don't usually start my pages off with an attribute, so I am not sure if this is a bug or my lack of understand. I did not see a related issue. Thanks.
The text was updated successfully, but these errors were encountered: