+
markdown
@@ -30,19 +30,19 @@ Syntax added by MarkBind:
->Center-align<-
-
+
Alternative syntax: https://www.markdownguide.org/basic-syntax#emphasis
-
+
```markdown
**Bold**, _Italic_, ___Bold and Italic___, `Inline Code`
~~Strike through~~, ****Super Bold****, !!Underline!!, ==Highlight==, %%Dim%%, ++Large++, --Small--, Super^script^, Sub~script~
```
-
-
+
+
**Bold**, _Italic_, ___Bold and Italic___, `Inline Code`
~~Strike through~~, ****Super Bold****, !!Underline!!, ==Highlight==, %%Dim%%, ++Large++, --Small--, Super^script^, Sub~script~
-
+
diff --git a/docs/userGuide/syntax/thumbnails.md b/docs/userGuide/syntax/thumbnails.md
index 987833e994..028503dece 100644
--- a/docs/userGuide/syntax/thumbnails.md
+++ b/docs/userGuide/syntax/thumbnails.md
@@ -35,13 +35,13 @@ text | `string` | | The text to use in the thumbnail, [icons]({{baseUrl}}/userGu
If both `text` and `src` are specified, `src` will take higher priority.
-
+
```html
```
-
+
-
+
-
+
diff --git a/docs/userGuide/syntax/tooltips.md b/docs/userGuide/syntax/tooltips.md
index 74aa76bc50..65e716c216 100644
--- a/docs/userGuide/syntax/tooltips.md
+++ b/docs/userGuide/syntax/tooltips.md
@@ -66,14 +66,14 @@ content | `String` | `''` | Text content of the tooltip.
placement | `String` | `top` | How to position the tooltip.
Supports: `top`, `left`, `right`, `bottom`.
-
+
```html
Hover here to see a tooltip.
```
-
+
-
+
Hover here to see a tooltip.
-
+
diff --git a/docs/userGuide/syntax/tree.md b/docs/userGuide/syntax/tree.md
index 59e2d7ded2..a186b192be 100644
--- a/docs/userGuide/syntax/tree.md
+++ b/docs/userGuide/syntax/tree.md
@@ -93,7 +93,7 @@ Currently, Pop-Ups(tooltip/trigger) are !!not!! supported within a `tree` compon
-
+
```html
@@ -105,9 +105,9 @@ C:/course/
site.json
```
-
+
-
+
C:/course/
textbook/
@@ -116,4 +116,4 @@ C:/course/
reading.md
site.json
-
+
diff --git a/docs/userGuide/syntax/variables.md b/docs/userGuide/syntax/variables.md
index ac91fa795c..4840fe8a27 100644
--- a/docs/userGuide/syntax/variables.md
+++ b/docs/userGuide/syntax/variables.md
@@ -4,10 +4,10 @@
## Variables
-
+
**Nunjucks [variables](https://mozilla.github.io/nunjucks/templating.html#set) are ideal for reusing small bits of code** in multiple places; you can define a variable to represent the code bit in question and reuse it anywhere in the site by referring to the variable instead of duplicating the code bit.
-
+
MarkBind does not aim to alter the already robust variable features of nunjucks, but provides several extensions to it.
@@ -179,15 +179,15 @@ Only `.json` and `.csv` files are supported for now.
-
+
Global variables:
`_markbind/variables.md`:
```html
-2018
+2018
```
`The year was {% raw %}{{ year }}{% endraw %}.`
-
+
diff --git a/docs/userGuide/themes.md b/docs/userGuide/themes.md
index fcd424e756..8734f848aa 100644
--- a/docs/userGuide/themes.md
+++ b/docs/userGuide/themes.md
@@ -13,11 +13,11 @@
# {{ title }}
-
+
**MarkBind supports the ability to style your website with a variety of bootstrap themes.**
-
+
#### Specifying a Theme
diff --git a/docs/userGuide/tipsAndTricks.md b/docs/userGuide/tipsAndTricks.md
index 21129c406b..7eae6e8c8d 100644
--- a/docs/userGuide/tipsAndTricks.md
+++ b/docs/userGuide/tipsAndTricks.md
@@ -9,7 +9,7 @@
# {{ title | safe }}
-
+
##### :fas-lightbulb: Escaping Characters
@@ -22,11 +22,11 @@ For Markdown syntax: To display a literal character that are normally used for M
* item 1
-
+
More info: [https://www.markdownguide.org/basic-syntax#escaping-characters](https://www.markdownguide.org/basic-syntax#escaping-characters)
-
+
---
@@ -77,7 +77,7 @@ When you use links or triggers, you may encounter a situation where an unwanted
---
-
+
##### :fas-info: Configuring Online Deployment platforms to use specific MarkBind version
@@ -120,11 +120,11 @@ Here are the steps to set up Netlify to use a specific version of MarkBind.
-
+
---
-
+
##### :fas-lightbulb: Indent components
@@ -169,9 +169,9 @@ to the component. The following examples show how to do this.
The following box component will be included via `
`.
-
+
Some text from include
-
+
html
@@ -184,5 +184,5 @@ The following box component will be included via ``.
-
+
diff --git a/docs/userGuide/troubleshooting.md b/docs/userGuide/troubleshooting.md
new file mode 100644
index 0000000000..1b3924f5aa
--- /dev/null
+++ b/docs/userGuide/troubleshooting.md
@@ -0,0 +1,59 @@
+{% set title = "Troubleshooting" %}
+{{ title }}
+
+
+ title: "User Guide: {{ title | safe }}"
+ layout: userGuide.md
+ pageNav: 5
+
+
+# {{ title | safe }}
+
+##### HTML Rendering Issues
+
+Unexpected behavior can occur in rendered pages due to a number of different reasons. One of these reasons is when the rendered pages are not valid HTML.
+
+Incorrect HTML markup can be due to:
+- nesting block-level elements inside `` or `` elements
+- missing `` tags
+
+###### Example: block-level elements inside `` elements
+```html
+
+
+
+Animal | Trainable? | Price | Remarks
+:------|:----------:|------:|--------
+Ants | no | 5 |
+Bees | no | 20 |
+Cats | yes | 100 |
+
+```
+
+The table specified by the markdown syntax above will be rendered as a block-level element, which will be included in a inline span element. This makes the HTML output invalid.
+
+
+
+```
+vue.js:634 [Vue warn]: The client-side rendered virtual DOM tree is not matching server-rendered content.
+This is likely caused by incorrect HTML markup, for example nesting block-level elements inside ``,
+or missing `
`.
+Bailing hydration and performing full client-side render.
+```
+See [SSR guide for Vue](https://vuejs.org/guide/scaling-up/ssr.html#hydration-mismatch) for more details on hydration mismatch.
+
+
+A possible fix for the above situation is to wrap the table in a `` element instead:
+
+```html
+
+
+
+Animal | Trainable? | Price | Remarks
+:------|:----------:|------:|--------
+Ants | no | 5 |
+Bees | no | 20 |
+Cats | yes | 100 |
+
+```
+
diff --git a/docs/userGuide/usingComponents.md b/docs/userGuide/usingComponents.md
index 18735fdf26..d951195b87 100644
--- a/docs/userGuide/usingComponents.md
+++ b/docs/userGuide/usingComponents.md
@@ -14,10 +14,10 @@
# Using Components
-
+
**MarkBind provides a number of components** (e.g., expandable panels, tabbed displays, navigation bars, etc.) that you can use to enhance the appearance/behavior of your pages.
-
+
To use a component, just use the corresponding markup in your file. For example, to create a Panel, you just need to use the markup:
diff --git a/docs/userGuide/usingHtmlJavaScriptCss.md b/docs/userGuide/usingHtmlJavaScriptCss.md
index 90892b697b..3d67b3e1d8 100644
--- a/docs/userGuide/usingHtmlJavaScriptCss.md
+++ b/docs/userGuide/usingHtmlJavaScriptCss.md
@@ -13,10 +13,10 @@
# {{ title }}
-
+
**A MarkBind source file can contain a mixture of HTML, JavaScript, and CSS** as a normal web page would.
-
+
==Text within HTML tags are considered plain text unless the text is preceded by a blank line,== in which case the text is parsed as Markdown text.
@@ -27,14 +27,14 @@
html
-
+
Without preceding blank line: Apples **Bananas** Cherries
-
+
-
+
With preceding blank line: Apples **Bananas** Cherries
-
+
@@ -49,13 +49,13 @@ Alternatively, you can use `` (for _block_ Markdown elements such as h
html
-
+
Apples **Bananas** Cherries
-
+
-
+
##### Apples **Bananas** Cherries
-
+