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
First of all: thank you for all the work put into this library. I did unfortunately run into a possible use case with columns that is not covered yet: what if only part of the slide should be in columns?
From what I understand, the [.columns] needs to be put before the slide separator as in the example below. However, when the header you want to show is of a lower level than what triggers a new slide (i.e. == or ===, that header is also put in a column instead of across the whole width of the slide.
In the example below, the text "Some explanation goes here..." should also be across the whole width of the slide.
Any help appreciated.
[.columns]
=== !
==== Two columns with a list in each
Some explanation goes here...
[.column]
--
* List item 1
** Item 1-1
** Item 1-2
* List item 2
--
[.column]
--
* List item 3
** Item 3-1
** Item 3-2
--
The text was updated successfully, but these errors were encountered:
[.columns.wrap]
=== Two columns with a list in each
[.column.is-full]
--
Some explanation goes here...--
[.column.is-half]
--
* List item 1
** Item 1-1
** Item 1-2
* List item 2
--
[.column.is-half]
--
* List item 3
** Item 3-1
** Item 3-2
--
First of all: thank you for all the work put into this library. I did unfortunately run into a possible use case with columns that is not covered yet: what if only part of the slide should be in columns?
From what I understand, the
[.columns]
needs to be put before the slide separator as in the example below. However, when the header you want to show is of a lower level than what triggers a new slide (i.e.==
or===
, that header is also put in a column instead of across the whole width of the slide.In the example below, the text "Some explanation goes here..." should also be across the whole width of the slide.
Any help appreciated.
The text was updated successfully, but these errors were encountered: