Skip to content

Commit 76a2780

Browse files
committed
fix: correct fenced code block syntax in introduction documentation
- Updated the introduction.md file to fix the syntax for fenced code blocks, ensuring proper rendering of markdown examples. - Adjusted the opening and closing markers for clarity and consistency in documentation.
1 parent 1ab2ff8 commit 76a2780

1 file changed

Lines changed: 5 additions & 5 deletions

File tree

‎content/docs/introduction.md‎

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ ShellDocs is the "just use this" answer. Point it at a folder of markdown, get a
3333

3434
Author a page as plain markdown with frontmatter:
3535

36-
```markdown
36+
````markdown
3737
---
3838
title: Button
3939
description: A pressable UI element.
@@ -48,15 +48,15 @@ The `<Button>` component ships in three variants.
4848
```razor:preview
4949
<Button Variant="primary">Click me</Button>
5050
```
51-
```
51+
````
5252

53-
Drop in fenced components anywhere:
53+
Drop inline components anywhere in prose:
5454

55-
```markdown
55+
````markdown
5656
<Callout Variant="warning" Title="Heads up">
5757
This behavior changed in `0.2.0`. Older versions used `OnClick` instead of `Pressed`.
5858
</Callout>
59-
```
59+
````
6060

6161
The whole thing renders : Callout with icon and variant styling, live Button component, syntax-highlighted code samples, working TOC : with zero JavaScript beyond what Blazor and Shiki need.
6262

0 commit comments

Comments
 (0)