Test Demo
Summary: 本文用于测试和展示网站功能, 并作为博客功能的说明书.
Markdown 基本语法
FixIt 主题作者已经提供了一个很好的 markdown 基本语法介绍, 这里仅对个人不太熟悉和常用的进行记录. 本节内容大量来自于主题作者提供的 文档.
锚点
标题锚点
标题自带锚点, 即标题的内容(空格用 - 替代, 大写用小写替代). 如 点击这里 可以链接到本节标题. 如果有同名标题, 则按顺序在后面添加 -1, -2等后缀, 如: #锚点, #锚点-1, #锚点-2.
注意
要想自定义标题锚点名称, 请在与标题相同的行中将自定义 ID 放在花括号中, 或者用正文锚点:
| |
前者会导致默认生成的锚点 (上例中即为 #markdown-基本语法) 无法使用, 取而代之为自定义的锚点名称 (上例中即为 #custon-id). 后者则是两个锚点名均可使用并且定位到相同位置. 个人推荐使用后者.
正文锚点
可以在正文中任意位置处添加锚点:
| |
这样我就可以跳转到相应的地方.
粗体和斜体
按照个人习惯规定, 粗体使用 ** 包裹, 斜体使用 _ 包裹. 但是 粗体中有斜体 除外, 使用 __粗体*粗斜体*粗体__ 形式.1
| |
粗体粗斜体粗体
粗体_粗斜体_粗体
斜体粗斜体斜体
斜体__粗斜体__斜体
全体对比: 正常|加粗|斜体|粗斜体|斜体包含粗体斜体|粗体包含斜体粗体.
预格式化文本
如果想要保留原格式输出一些文本, 可以使用预格式化文本.
| |
这是一些
预格式化的文本.
文本中的空格 和 换行符
都会被保留.
超链接
基本格式:
| |
Markdown 扩展语法
本节内容为 FixIt 主题定制版语法. 与上节相同, 本节内容基本全部来自于 FixIt 官方介绍文档.
Callout
Callout 是特殊的 用于强调关键信息的 引用块. FixIt 中基本兼容 obsidian 中的 callouts 用法.
FixIt 有两种类型的 Callouts:
基本 Callout
如果给这些基本 Callout 加 title, 或者选择是否折叠, 则会变成扩展版.
| |
注意
Lorem ipsum dolor sit amet
WvW-Note: 这是排版中常用的无意义拉丁文
提示
Lorem ipsum dolor sit amet
重要
Lorem ipsum dolor sit amet
警告
Lorem ipsum dolor sit amet
小心
Lorem ipsum dolor sit amet
扩展 Callout
扩展 Callouts 可以 在类型后面加 + 和 - 来表示其默认状态.
注意
Obsidian 自定义 callout 标题的方法和 FixIt 不太一样:
| |
只要包含空格, 数字, 汉字或者符号(连字符, 下划线, 句号)就不能使用以下方式自定义 callout
| |
FixIt 支持在配置文件中自定义 callout. FixIt 主题原生支持以下类型扩展版 callouts.
| |
type: note
type: tip
aliases: important, hint
type: warning
aliases: caution, attention
type: abstract
aliases: summary, tldr
WvW-Note: TL;DR means: too long; didn’t read.
type: info
一些不太重要的信息.
type: todo
type: success
aliases: check, done
type: question
aliases: help, faq
WvW-Note: faq means: frequently asked questions.
type: failure
aliases: fail, missing
type: danger
alias: error
type: bug
type: example
type: quote
alias: cite
任务列表
FixIt 在 markdown 基本的待办事项表示方法上增加了许多新的状态, 所有支持的状态如下:
| |
- 未完成
- 已完成
- 进行中
- 已取消
- 已计划
- 已重新计划
- 重要
- 问题
同 callout, FixIt 支持自定义待办事项.
删除线, 下划线, 高亮 和 上下标
在 加粗, 斜体 的基础 markdown 语法上, Hugo 定义了类似的扩展语法:
| |
这是删除线.
这是下划线.
这是高亮.
这是^上标^.2
这是下标.
其他高亮颜色:
Primary
Secondary
Success
Info
Warning
Danger
数学公式
FixIt 原本使用 KaTeX 对 LaTeX 语法提供支持. 但由于个人对宏包有较多需求, 故暂时使用了一个 破坏性的 方法强制使用 MathJax. 具体情况见:
[FEATURE] Add MathJax Support as an Alternative Renderer
重要
在 20250630, FixIt 增加了对 MathJax 的支持. 详情见官方文档.
警告
目前若加密文章, 公式则无法渲染.
以下是具体测试:
| |
这是一个行内公式 $a^*=x-b^*$.
| |
| |
警告
< 后 一定 要接一个空格 (或使用 \lt 代替 < 以强制提醒自己加空格), 否则会当成 html 的标签而无法渲染.3
| |
根据 SonnyCalcr的博客 所说:
…数学公式如果有超过了三对花括号, 那么, 其解析和转义就会出问题…
但在本文中尚未遇到, 可能是此 bug 已被修复?
| |
字符注音 或 注释
FixIt 主题支持一种 字符注音或者注释 Markdown 扩展语法:
| |
MMA 是一个很好用的计算软件.
分数
FixIt 主题支持一种 分数 Markdown 扩展语法:
| |
浅色/深色
99/100
Font Awesome
FixIt 主题使用 Font Awesome V6 作为图标库, 可以轻松使用其中的图标:
| |
转义字符
在某些特殊情况下 (编写这个主题文档时 ), 你的文章内容会与 Markdown 的基本或者扩展语法冲突, 并且无法避免. 转义字符语法可以帮助你渲染出想要的内容:
1{?X}->X
| |
[link](#escape-character)
Markdown 属性
Hugo 支持图像和块元素上的 Markdown 属性, 包括块引用、围栏代码块、标题、水平线、列表、段落和表格.
在大多数情况下, 将属性列表放置在标记元素下方. 对于标题和围栏代码块, 将属性列表放在右侧.
| |
分割线
| |
呈现的输出如下所示:
引用
| |
呈现的输出如下所示:
The quick brown fox jumps over the lazy dog.
表格 和 列表
目前有一些限制: 对于表格, 你目前只能将其应用于完整表格; 而对于列表, 仅适用于 <ul>/<ol> 节点, 例如:
| |
呈现的输出如下所示:
- 水果
- 苹果
- 橙子
- 香蕉
- 乳制品
- 牛奶
- 奶酪
代码块
请注意, code fences 中的属性和其他高亮处理指令必须位于开始标记之后, 例如:
| |
title
| |
highlight
| |
no-header
| |
data-open
| |
代码块拓展语法
GoAT
GoAT 是 markdeep.mini.js 图像生成器的 Go 语言实现.
要使用 GoAT, 只需将 ASCII 输入放在代码块中, 并将语言设置为 goat.
Trees:
| |
Overlaps:
| |
Line Decorations:
| |
Line Ends:
| |
Dot Grids:
| |
Large Nodes:
| |
Small Grids:
| |
Big Grids:
| |
Complicated:
| |
Mermaid
Mermaid 是一个基于 JavaScript 的图表工具, 它允许你使用文本和代码创建图表和可视化.
要使用 Mermaid, 只需将 Mermaid 的代码输入放在代码块中, 并将语言设置为 mermaid.
Flowchart:
| |
graph TD;
A-->B;
A-->C;
B-->D;
C-->D;graph TD;
A-->B;
A-->C;
B-->D;
C-->D;graph TD;
A-->B;
A-->C;
B-->D;
C-->D;graph TD;
A-->B;
A-->C;
B-->D;
C-->D;Sequence diagram:
| |
sequenceDiagram
participant Alice
participant Bob
Alice->>John: Hello John, how are you?
loop HealthCheck
John->>John: Fight against hypochondria
end
Note right of John: Rational thoughts
prevail!
John-->>Alice: Great!
John->>Bob: How about you?
Bob-->>John: Jolly good!sequenceDiagram
participant Alice
participant Bob
Alice->>John: Hello John, how are you?
loop HealthCheck
John->>John: Fight against hypochondria
end
Note right of John: Rational thoughts
prevail!
John-->>Alice: Great!
John->>Bob: How about you?
Bob-->>John: Jolly good!sequenceDiagram
participant Alice
participant Bob
Alice->>John: Hello John, how are you?
loop HealthCheck
John->>John: Fight against hypochondria
end
Note right of John: Rational thoughts
prevail!
John-->>Alice: Great!
John->>Bob: How about you?
Bob-->>John: Jolly good!sequenceDiagram
participant Alice
participant Bob
Alice->>John: Hello John, how are you?
loop HealthCheck
John->>John: Fight against hypochondria
end
Note right of John: Rational thoughts
prevail!
John-->>Alice: Great!
John->>Bob: How about you?
Bob-->>John: Jolly good!Gantt diagram:
| |
gantt dateFormat YYYY-MM-DD title Adding GANTT diagram to mermaid excludes weekdays 2014-01-10 section A section Completed task :done, des1, 2014-01-06,2014-01-08 Active task :active, des2, 2014-01-09, 3d Future task : des3, after des2, 5d Future task2 : des4, after des3, 5d
gantt dateFormat YYYY-MM-DD title Adding GANTT diagram to mermaid excludes weekdays 2014-01-10 section A section Completed task :done, des1, 2014-01-06,2014-01-08 Active task :active, des2, 2014-01-09, 3d Future task : des3, after des2, 5d Future task2 : des4, after des3, 5d
gantt dateFormat YYYY-MM-DD title Adding GANTT diagram to mermaid excludes weekdays 2014-01-10 section A section Completed task :done, des1, 2014-01-06,2014-01-08 Active task :active, des2, 2014-01-09, 3d Future task : des3, after des2, 5d Future task2 : des4, after des3, 5d
gantt dateFormat YYYY-MM-DD title Adding GANTT diagram to mermaid excludes weekdays 2014-01-10 section A section Completed task :done, des1, 2014-01-06,2014-01-08 Active task :active, des2, 2014-01-09, 3d Future task : des3, after des2, 5d Future task2 : des4, after des3, 5d
Class diagram:
| |
classDiagram Class01 <|-- AveryLongClass : Cool Class03 *-- Class04 Class05 o-- Class06 Class07 .. Class08 Class09 --> C2 : Where am i? Class09 --* C3 Class09 --|> Class07 Class07 : equals() Class07 : Object[] elementData Class01 : size() Class01 : int chimp Class01 : int gorilla Class08 <--> C2: Cool label
classDiagram Class01 <|-- AveryLongClass : Cool Class03 *-- Class04 Class05 o-- Class06 Class07 .. Class08 Class09 --> C2 : Where am i? Class09 --* C3 Class09 --|> Class07 Class07 : equals() Class07 : Object[] elementData Class01 : size() Class01 : int chimp Class01 : int gorilla Class08 <--> C2: Cool label
classDiagram Class01 <|-- AveryLongClass : Cool Class03 *-- Class04 Class05 o-- Class06 Class07 .. Class08 Class09 --> C2 : Where am i? Class09 --* C3 Class09 --|> Class07 Class07 : equals() Class07 : Object[] elementData Class01 : size() Class01 : int chimp Class01 : int gorilla Class08 <--> C2: Cool label
classDiagram Class01 <|-- AveryLongClass : Cool Class03 *-- Class04 Class05 o-- Class06 Class07 .. Class08 Class09 --> C2 : Where am i? Class09 --* C3 Class09 --|> Class07 Class07 : equals() Class07 : Object[] elementData Class01 : size() Class01 : int chimp Class01 : int gorilla Class08 <--> C2: Cool label
Git graph
| |
gitGraph
commit
branch hotfix
checkout hotfix
commit
branch develop
checkout develop
commit id:"ash" tag:"abc"
branch featureB
checkout featureB
commit type:HIGHLIGHT
checkout main
checkout hotfix
commit type:NORMAL
checkout develop
commit type:REVERSE
checkout featureB
commit
checkout main
merge hotfix
checkout featureB
commit
checkout develop
branch featureA
commit
checkout develop
merge hotfix
checkout featureA
commit
checkout featureB
commit
checkout develop
merge featureA
branch release
checkout release
commit
checkout main
commit
checkout release
merge main
checkout develop
merge releasegitGraph
commit
branch hotfix
checkout hotfix
commit
branch develop
checkout develop
commit id:"ash" tag:"abc"
branch featureB
checkout featureB
commit type:HIGHLIGHT
checkout main
checkout hotfix
commit type:NORMAL
checkout develop
commit type:REVERSE
checkout featureB
commit
checkout main
merge hotfix
checkout featureB
commit
checkout develop
branch featureA
commit
checkout develop
merge hotfix
checkout featureA
commit
checkout featureB
commit
checkout develop
merge featureA
branch release
checkout release
commit
checkout main
commit
checkout release
merge main
checkout develop
merge releasegitGraph
commit
branch hotfix
checkout hotfix
commit
branch develop
checkout develop
commit id:"ash" tag:"abc"
branch featureB
checkout featureB
commit type:HIGHLIGHT
checkout main
checkout hotfix
commit type:NORMAL
checkout develop
commit type:REVERSE
checkout featureB
commit
checkout main
merge hotfix
checkout featureB
commit
checkout develop
branch featureA
commit
checkout develop
merge hotfix
checkout featureA
commit
checkout featureB
commit
checkout develop
merge featureA
branch release
checkout release
commit
checkout main
commit
checkout release
merge main
checkout develop
merge releasegitGraph
commit
branch hotfix
checkout hotfix
commit
branch develop
checkout develop
commit id:"ash" tag:"abc"
branch featureB
checkout featureB
commit type:HIGHLIGHT
checkout main
checkout hotfix
commit type:NORMAL
checkout develop
commit type:REVERSE
checkout featureB
commit
checkout main
merge hotfix
checkout featureB
commit
checkout develop
branch featureA
commit
checkout develop
merge hotfix
checkout featureA
commit
checkout featureB
commit
checkout develop
merge featureA
branch release
checkout release
commit
checkout main
commit
checkout release
merge main
checkout develop
merge releaseEntity Relationship Diagram(❗experimental):
| |
erDiagram
CUSTOMER ||--o{ ORDER : places
ORDER ||--|{ LINE-ITEM : contains
CUSTOMER }|..|{ DELIVERY-ADDRESS : useserDiagram
CUSTOMER ||--o{ ORDER : places
ORDER ||--|{ LINE-ITEM : contains
CUSTOMER }|..|{ DELIVERY-ADDRESS : useserDiagram
CUSTOMER ||--o{ ORDER : places
ORDER ||--|{ LINE-ITEM : contains
CUSTOMER }|..|{ DELIVERY-ADDRESS : useserDiagram
CUSTOMER ||--o{ ORDER : places
ORDER ||--|{ LINE-ITEM : contains
CUSTOMER }|..|{ DELIVERY-ADDRESS : usesUser Journey Diagram
| |
journey
title My working day
section Go to work
Make tea: 5: Me
Go upstairs: 3: Me
Do work: 1: Me, Cat
section Go home
Go downstairs: 5: Me
Sit down: 5: Mejourney
title My working day
section Go to work
Make tea: 5: Me
Go upstairs: 3: Me
Do work: 1: Me, Cat
section Go home
Go downstairs: 5: Me
Sit down: 5: Mejourney
title My working day
section Go to work
Make tea: 5: Me
Go upstairs: 3: Me
Do work: 1: Me, Cat
section Go home
Go downstairs: 5: Me
Sit down: 5: Mejourney
title My working day
section Go to work
Make tea: 5: Me
Go upstairs: 3: Me
Do work: 1: Me, Cat
section Go home
Go downstairs: 5: Me
Sit down: 5: MeQuadrant Chart:
| |
quadrantChart
title Reach and engagement of campaigns
x-axis Low Reach --> High Reach
y-axis Low Engagement --> High Engagement
quadrant-1 We should expand
quadrant-2 Need to promote
quadrant-3 Re-evaluate
quadrant-4 May be improved
Campaign A: [0.3, 0.6]
Campaign B: [0.45, 0.23]
Campaign C: [0.57, 0.69]
Campaign D: [0.78, 0.34]
Campaign E: [0.40, 0.34]
Campaign F: [0.35, 0.78]quadrantChart
title Reach and engagement of campaigns
x-axis Low Reach --> High Reach
y-axis Low Engagement --> High Engagement
quadrant-1 We should expand
quadrant-2 Need to promote
quadrant-3 Re-evaluate
quadrant-4 May be improved
Campaign A: [0.3, 0.6]
Campaign B: [0.45, 0.23]
Campaign C: [0.57, 0.69]
Campaign D: [0.78, 0.34]
Campaign E: [0.40, 0.34]
Campaign F: [0.35, 0.78]quadrantChart
title Reach and engagement of campaigns
x-axis Low Reach --> High Reach
y-axis Low Engagement --> High Engagement
quadrant-1 We should expand
quadrant-2 Need to promote
quadrant-3 Re-evaluate
quadrant-4 May be improved
Campaign A: [0.3, 0.6]
Campaign B: [0.45, 0.23]
Campaign C: [0.57, 0.69]
Campaign D: [0.78, 0.34]
Campaign E: [0.40, 0.34]
Campaign F: [0.35, 0.78]quadrantChart
title Reach and engagement of campaigns
x-axis Low Reach --> High Reach
y-axis Low Engagement --> High Engagement
quadrant-1 We should expand
quadrant-2 Need to promote
quadrant-3 Re-evaluate
quadrant-4 May be improved
Campaign A: [0.3, 0.6]
Campaign B: [0.45, 0.23]
Campaign C: [0.57, 0.69]
Campaign D: [0.78, 0.34]
Campaign E: [0.40, 0.34]
Campaign F: [0.35, 0.78]XY Chart:
| |
xychart-beta
title "Sales Revenue"
x-axis [jan, feb, mar, apr, may, jun, jul, aug, sep, oct, nov, dec]
y-axis "Revenue (in $)" 4000 --> 11000
bar [5000, 6000, 7500, 8200, 9500, 10500, 11000, 10200, 9200, 8500, 7000, 6000]
line [5000, 6000, 7500, 8200, 9500, 10500, 11000, 10200, 9200, 8500, 7000, 6000]xychart-beta
title "Sales Revenue"
x-axis [jan, feb, mar, apr, may, jun, jul, aug, sep, oct, nov, dec]
y-axis "Revenue (in $)" 4000 --> 11000
bar [5000, 6000, 7500, 8200, 9500, 10500, 11000, 10200, 9200, 8500, 7000, 6000]
line [5000, 6000, 7500, 8200, 9500, 10500, 11000, 10200, 9200, 8500, 7000, 6000]xychart-beta
title "Sales Revenue"
x-axis [jan, feb, mar, apr, may, jun, jul, aug, sep, oct, nov, dec]
y-axis "Revenue (in $)" 4000 --> 11000
bar [5000, 6000, 7500, 8200, 9500, 10500, 11000, 10200, 9200, 8500, 7000, 6000]
line [5000, 6000, 7500, 8200, 9500, 10500, 11000, 10200, 9200, 8500, 7000, 6000]xychart-beta
title "Sales Revenue"
x-axis [jan, feb, mar, apr, may, jun, jul, aug, sep, oct, nov, dec]
y-axis "Revenue (in $)" 4000 --> 11000
bar [5000, 6000, 7500, 8200, 9500, 10500, 11000, 10200, 9200, 8500, 7000, 6000]
line [5000, 6000, 7500, 8200, 9500, 10500, 11000, 10200, 9200, 8500, 7000, 6000]Pie chart diagrams:
| |
pie title Pets adopted by volunteers
"Dogs" : 386
"Cats" : 85
"Rats" : 15pie title Pets adopted by volunteers
"Dogs" : 386
"Cats" : 85
"Rats" : 15pie title Pets adopted by volunteers
"Dogs" : 386
"Cats" : 85
"Rats" : 15pie title Pets adopted by volunteers
"Dogs" : 386
"Cats" : 85
"Rats" : 15Requirement Diagram:
| |
requirementDiagram
requirement test_req {
id: 1
text: the test text.
risk: high
verifymethod: test
}
element test_entity {
type: simulation
}
test_entity - satisfies -> test_req requirementDiagram
requirement test_req {
id: 1
text: the test text.
risk: high
verifymethod: test
}
element test_entity {
type: simulation
}
test_entity - satisfies -> test_req requirementDiagram
requirement test_req {
id: 1
text: the test text.
risk: high
verifymethod: test
}
element test_entity {
type: simulation
}
test_entity - satisfies -> test_req requirementDiagram
requirement test_req {
id: 1
text: the test text.
risk: high
verifymethod: test
}
element test_entity {
type: simulation
}
test_entity - satisfies -> test_reqMindmap:
| |
mindmap
root((mindmap))
Origins
Long history
::icon(fa fa-book)
Popularisation
British popular psychology author Tony Buzan
Research
On effectiveness
and features
On Automatic creation
Uses
Creative techniques
Strategic planning
Argument mapping
Tools
Pen and paper
Mermaidmindmap
root((mindmap))
Origins
Long history
::icon(fa fa-book)
Popularisation
British popular psychology author Tony Buzan
Research
On effectiveness
and features
On Automatic creation
Uses
Creative techniques
Strategic planning
Argument mapping
Tools
Pen and paper
Mermaidmindmap
root((mindmap))
Origins
Long history
::icon(fa fa-book)
Popularisation
British popular psychology author Tony Buzan
Research
On effectiveness
and features
On Automatic creation
Uses
Creative techniques
Strategic planning
Argument mapping
Tools
Pen and paper
Mermaidmindmap
root((mindmap))
Origins
Long history
::icon(fa fa-book)
Popularisation
British popular psychology author Tony Buzan
Research
On effectiveness
and features
On Automatic creation
Uses
Creative techniques
Strategic planning
Argument mapping
Tools
Pen and paper
MermaidPacket Diagram:
| |
packet-beta title UDP Packet 0-15: "Source Port" 16-31: "Destination Port" 32-47: "Length" 48-63: "Checksum" 64-95: "Data (variable length)"
packet-beta title UDP Packet 0-15: "Source Port" 16-31: "Destination Port" 32-47: "Length" 48-63: "Checksum" 64-95: "Data (variable length)"
packet-beta title UDP Packet 0-15: "Source Port" 16-31: "Destination Port" 32-47: "Length" 48-63: "Checksum" 64-95: "Data (variable length)"
packet-beta title UDP Packet 0-15: "Source Port" 16-31: "Destination Port" 32-47: "Length" 48-63: "Checksum" 64-95: "Data (variable length)"
Architecture Diagrams Documentation:
| |
architecture-beta
group api(cloud)[API]
service db(database)[Database] in api
service disk1(disk)[Storage] in api
service disk2(disk)[Storage] in api
service server(server)[Server] in api
db:L -- R:server
disk1:T -- B:server
disk2:T -- B:dbarchitecture-beta
group api(cloud)[API]
service db(database)[Database] in api
service disk1(disk)[Storage] in api
service disk2(disk)[Storage] in api
service server(server)[Server] in api
db:L -- R:server
disk1:T -- B:server
disk2:T -- B:dbarchitecture-beta
group api(cloud)[API]
service db(database)[Database] in api
service disk1(disk)[Storage] in api
service disk2(disk)[Storage] in api
service server(server)[Server] in api
db:L -- R:server
disk1:T -- B:server
disk2:T -- B:dbarchitecture-beta
group api(cloud)[API]
service db(database)[Database] in api
service disk1(disk)[Storage] in api
service disk2(disk)[Storage] in api
service server(server)[Server] in api
db:L -- R:server
disk1:T -- B:server
disk2:T -- B:db还有许多其他类型的图, 具体内容可查看 mermaid 官网.
Timeline
Timeline 可拆分成多个按照时间戳正序或倒序排列的事件, 时间戳和内容是必填项. 更多内容请查看 FixIt 官网.
| |
- 🎉 Feat: add timeline support for code blocks
- Half a year later…
- 🔖 Chore(release): 0.3.0
- ⬆️ Chore: update 0.2.11
- Developed for a long time…
Shortcodes
Hugo 内置 Shortcodes
参考 FixIt 文档.
figure
| |
建议使用 markdown 默认图片语法 或 FixIt 提供的 image shortcode.
随机图床
gist
Hugo 将不再内置 Gist shortcode4:
The gist shortcode was deprecated in version 0.143.0 and will be removed in a future release.
| |
QR
| |

或者
| |

X
| |
警告
目前无法渲染.
Vimeo
| |
Youtube
| |
FixIt 扩展 Shortcodes
参考 FixIt 文档.
link
普通链接用 markdown 语法即可, 这个 shortcode 主要是提供了卡片式链接:
| |
也可以表示可下载资源:
| |
image
| |

注意
也可以用 markdown 格式的图片引用, 大部分情况下足够满足需求. 如果有更多需求不如直接写 html.
mapbox
由于没有 accessToken 所以具体内容见 FixIt 文档.
music
详情见 FixIt 文档.
| |
警告
当前使用 music shortcode 后页面目录会卡住, 详情见 [BUG] 使用 music shortcode 后会导致目录卡死
spotify
详情见 FixIt 文档.
| |
bilibili
| |
douyin
| |
typeit
| |
这一个带有基于 TypeIt 的 打字动画 的 段落……
public class HelloWorld { public static void main(String []args) { System.out.println("Hello World"); } }
首先, 这个段落开始
然后, 这个段落开始
script
| |
details
| |
这里可以写 markdown 语法
展开内容是正常 markdown 格式.
fixit-encrypt
raw
如果需要在引用块中使用公式, 最好用 {{< raw >}} 和 {{< /raw >}} 包裹.
自定义 Shortcodes
slidev
Slidev (slide + dev, /slaɪdɪv/) 是一个为开发者设计的基于 Web 的幻灯片制作工具。它帮助您以 Markdown 的形式专注于编写幻灯片的内容,并制作出具有交互式演示功能的、高度可自定义的幻灯片。 — Slidev
| |
个人 slidev 仓库 的搭建参考了 Thomas Boerger, Anthony Fu, Haili Zhang 等人的项目.
暂时没找到比较好的演示加教程, 先用随便找的一篇占位.
常用 html 代码
缩放
| |
这是一段缩小文本 vs. 普通大小 vs. 放大文本
颜色
| |
橘色文本 vs. 水鸭色文本
空格与换行
| |
文本间的 多个空格, 通过 html代码 实现.
文本间的换行
使用<br>实现.
其他细节展示
中文“引号” vs. 英文"引号"
:smile: vs. 😄
注意
如果在配置文件里设置了 enableEmoji: true 则可以通过左边的方式输入 emoji. 但无论 true or false 都不影响直接输入 unicode 版 emoji.
References
TODO
- 完善文章结构, 把测试内容更加完善更加有逻辑的整理完成.
- 在本文基础上, 整理建站过程.
粗中有斜和斜中有粗只能外面
_, 里面*. ↩︎Reference: Math equations with the less than sign (<) can’t render correctly ↩︎
Reference: Gist shortcode. ↩︎