<annotate src="../../images/annotateSampleImage.png" width="500" alt="Sample Image">
<a-point x="25%" y="25%" content="Lorem ipsum dolor sit amet" />
<a-point x="50%" y="25%" content="Lorem ipsum dolor sit amet" label="1a"/>
<a-point x="50%" y="25%" content="Lorem ipsum dolor sit amet" label="1b" legend="both"/>
</annotate>
add a space before '{' for block level markdown {.class-name attribute="value" attribute=value #id}
don't add a space for **inline**{.text-danger} markdown
For a more detailed guide, see: https://www.npmjs.com/package/markdown-it-attrs
<cardstack searchable blocks="2">
<card header="**Basic Card** :rocket:" tag="Basic Card" keywords="Basic">
This is a basic card.<br>
Click on this <trigger for="modal:triggerBait" trigger="click">trigger!</trigger>.
<modal header="**You clicked on a Trigger!** :rocket:" id="modal:triggerBait">
<md>You have just triggered a modal controlled by a trigger called trigger! :rofl:</md>
</modal>
</card>
<card header="A *markdown* header" tag="Markdown, header, Cool" keywords="">
You can apply markdown to headers and body elements!
<box type="warning">
<md>>**Like** *this* [cool](#cardstacks) `text` :cool:</md>
</box>
</card>
<card header="Card with Image" keywords="Super duper cool" tag="Image, Cool">
<annotate src="../../images/annotateSampleImage.png" height="500" alt="Sample Image">
<a-point x="2%" y="13%" content="I am annotated" header="Annotated point" opacity="0.2" size="20"/>
</annotate>
</card>
<card header="Disabled card" tag="Disabled" keywords="Disabled" disabled>
This card is disabled and will not show
</card>
<card header="An **interesting** question" tag="Question, Markdown" keywords="">
<question type="checkbox" header="Which of the following is correct?" hint="Think out of the box! :fas-box:">
<pic src="/images/math-question.jpg" alt="math question image" height="200" class="d-block mx-auto">
<small><md>Adapted from [Daily Mail](https://www.dailymail.co.uk/femail/article-4702868/Can-pass-intelligence-test.html)</md>
</small>
</pic>
<q-option correct reason="Multiply the numbers on the left together and add the leftmost number!">
96
</q-option>
<q-option reason="Under normal circumstances, this would be correct.">
19
</q-option>
<q-option correct reason="Simply add the running sum of the results as well!">
40
</q-option>
<q-option>
811
</q-option>
</question>
</card>
</cardstack>
<dropdown header="Action" type="primary">
<li><a href="#dropdown" class="dropdown-item">Action</a></li>
<li><a href="#dropdown" class="dropdown-item">Another action</a></li>
<li role="separator" class="dropdown-divider"></li>
<li><a href="#dropdown" class="dropdown-item">Separated link</a></li>
</dropdown>
<navbar type="primary">
<!-- Brand as slot -->
<a slot="brand" href="/" title="Home" class="navbar-brand">MarkBind</a>
<li><a href="/userGuide/components/navigation.html#navbars" class="nav-link">Highlighted Link</a></li>
<!-- You can use dropdown component -->
<dropdown header="Dropdown" class="nav-link">
<li><a href="#navbars" class="dropdown-item">Option</a></li>
</dropdown>
<!-- For right positioning use slot -->
<li slot="right">
<a href="https://github.com/MarkBind/markbind" target="_blank" class="nav-link">Fork...</a>
</li>
</navbar>
<!-- use type="checkbox" for checkbox questions -->
<question type="mcq" header="Which of these **contradicts** the heuristics recommended when creating test cases with multiple inputs?">
<!-- Insert the reason for the option using the reason attribute -->
<q-option reason="This option **does not contradict the heuristics recommended**. We need to figure out if a positive test case works!">
Each valid test input should appear at least once in a test case that doesn’t have any invalid inputs.
</q-option>
<q-option>
It is ok to combine valid values for different inputs.
</q-option>
<q-option>
No more than one invalid test input should be in a given test case.
</q-option>
<!-- Use the 'correct' attribute to indicate an option as correct. -->
<q-option correct>
All invalid test inputs must be tested together.
<!-- Optionally, you may use a reason slot instead of a reason attribute. -->
<div slot="reason">
If you test all invalid test inputs together, you will not know if each one of the invalid inputs are handled
correctly by the SUT.
This is because most SUTs return an error message upon encountering the first invalid input.
</div>
</q-option>
<div slot="hint">
How do you figure out which inputs are wrong? (or correct)
</div>
</question>
<question type="blanks" hint="Google it!">
###### German sociologist __________ called the process of simultaneously analyzing the behavior of individuals and the society that shapes that behavior __________.
<q-option keywords="Norbert Elias, Elias" reason="That's his name!"></q-option>
<q-option keywords="figuration"></q-option>
</question>
<question type="text" header="Which country did the Hawaiian pizza originate from?"
keywords="hawaii" threshold="0.5" answer="It originated from Hawaii!">
<div slot="hint">
Watch some pizza commercials! :tv:
:pizza: :pizza: :pizza: :pizza: :pizza: :pizza: :pizza: :pizza: :pizza: :pizza: :pizza: :pizza:
</div>
</question>
<quiz>
<question type="mcq">...</question>
<question type="checkbox">...</question>
<question type="blanks">...</question>
<question type="text">...</question>
</quiz>
<site-nav>
* [**Getting Started**](/userGuide/gettingStarted.html)
* **Authoring Contents** :expanded:
* [Overview](/userGuide/authoringContents.html)
* [Adding Pages](/userGuide/addingPages.html)
* [MarkBind Syntax Overview](/userGuide/markBindSyntaxOverview.html)
* [Formatting Contents](/userGuide/formattingContents.html)
* [Using Components](/userGuide/usingComponents.html)
</site-nav>
<tabs>
<tab header="First tab">
Content of the first tab
</tab>
<tab header="Second tab">
Contents of the second tab
</tab>
<tab-group header="Third tab group :tv:">
<tab header="Stars :star:">
Some stuff about stars ...
</tab>
<tab header="Moon">
Some stuff about the moon ...
</tab>
</tab-group>
</tabs>
Here is the footnote. Footnotes will appear at the bottom of the page.
Here's one with multiple blocks.
Subsequent paragraphs are indented to show that they belong to the previous footnote.
Inline notes are easier to write, since you don't have to pick an identifier and move down to type the note.
Math