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
To keep in line with our EOxElements, the storytelling itself could and maybe should be a web component as well. This would offer portabilty and also maybe two "APIs" on how to program a story. Example:
<eox-story format="pages" style="background: lightgrey">
<eox-story-page style="background: #004170">
<h1>Page 1 title</h1>
<p>Page 1 text</p>
</eox-story-page>
[...]
</eox-story>
The markdown input could then also "translate" into the story format:
// INPUT
---
layout: scrollytelling
background: lightgrey
---
# Section 1
Text for section one
---
[background-color]: #f00
[scrub-direction]: vertical
[element]: chart
# Section 2
Text for section 2
// OUTPUT
<eox-story format="scrollytelling" style="background: lightgrey">
<eox-story-block>
<h1>Section 1</h1>
<p>Text for section one</p>
</eox-story-block>
<eox-story-block style="background: #f00" scrub-direction="vertical">
<h1>Section 2</h1>
<p>Text for section 2</p>
<eox-chart slot="sticky-element"></eox-chart>
</eox-story-block>
</eox-story>
The text was updated successfully, but these errors were encountered:
To keep in line with our EOxElements, the storytelling itself could and maybe should be a web component as well. This would offer portabilty and also maybe two "APIs" on how to program a story. Example:
The markdown input could then also "translate" into the story format:
The text was updated successfully, but these errors were encountered: