Create website

main
Emil Dabrowski 4 months ago
parent 0e606be040
commit b536977c22
  1. 5
      Containerfile
  2. 1
      README.md
  3. 6
      archetypes/default.md
  4. 10
      assets/css/_custom.scss
  5. 3
      assets/css/_override.scss
  6. BIN
      assets/images/avatar.png
  7. BIN
      assets/images/logo.png
  8. BIN
      assets/images/screenshot.png
  9. 305
      config.yaml
  10. 25
      container-build.sh
  11. 64
      content/about/index.en.md
  12. 67
      content/about/index.sv.md
  13. BIN
      content/about/wp2535788-1280px.jpg
  14. BIN
      content/posts/first-post/featured-image.png
  15. 31
      content/posts/first-post/index.en.md
  16. 771
      content/posts/first-post/index.zh-cn.md
  17. BIN
      static/android-chrome-192x192.png
  18. BIN
      static/android-chrome-512x512.png
  19. BIN
      static/apple-touch-icon.png
  20. BIN
      static/favicon-16x16.png
  21. BIN
      static/favicon-32x32.png
  22. BIN
      static/favicon.ico
  23. 747
      static/favicon.svg
  24. 1
      static/site.webmanifest
  25. 10
      themes/LoveIt/.babelrc
  26. 17
      themes/LoveIt/.circleci/config.yml
  27. 1
      themes/LoveIt/.github/FUNDING.yml
  28. 41
      themes/LoveIt/.github/ISSUE_TEMPLATE/bug-report.md
  29. 5
      themes/LoveIt/.github/ISSUE_TEMPLATE/config.yml
  30. 22
      themes/LoveIt/.github/ISSUE_TEMPLATE/feature-request.md
  31. 20
      themes/LoveIt/.gitignore
  32. 4
      themes/LoveIt/.husky/pre-commit
  33. 21
      themes/LoveIt/LICENSE
  34. 203
      themes/LoveIt/README.md
  35. 198
      themes/LoveIt/README.zh-cn.md
  36. 62
      themes/LoveIt/archetypes/default.md
  37. 61
      themes/LoveIt/assets/css/_core/_base.scss
  38. 15
      themes/LoveIt/assets/css/_core/_layout.scss
  39. 80
      themes/LoveIt/assets/css/_core/_media.scss
  40. 4
      themes/LoveIt/assets/css/_custom.scss
  41. 5
      themes/LoveIt/assets/css/_mixin/_blur.scss
  42. 110
      themes/LoveIt/assets/css/_mixin/_compatibility.scss
  43. 7
      themes/LoveIt/assets/css/_mixin/_details.scss
  44. 4
      themes/LoveIt/assets/css/_mixin/_index.scss
  45. 20
      themes/LoveIt/assets/css/_mixin/_link.scss
  46. 4
      themes/LoveIt/assets/css/_override.scss
  47. 6
      themes/LoveIt/assets/css/_page/_404.scss
  48. 13
      themes/LoveIt/assets/css/_page/_archive.scss
  49. 182
      themes/LoveIt/assets/css/_page/_home.scss
  50. 22
      themes/LoveIt/assets/css/_page/_index.scss
  51. 347
      themes/LoveIt/assets/css/_page/_single.scss
  52. 5
      themes/LoveIt/assets/css/_page/_special.scss
  53. 27
      themes/LoveIt/assets/css/_partial/_archive/_tags.scss
  54. 82
      themes/LoveIt/assets/css/_partial/_archive/_terms.scss
  55. 17
      themes/LoveIt/assets/css/_partial/_cookieconsent.scss
  56. 33
      themes/LoveIt/assets/css/_partial/_details.scss
  57. 46
      themes/LoveIt/assets/css/_partial/_fixed-button.scss
  58. 21
      themes/LoveIt/assets/css/_partial/_footer.scss
  59. 468
      themes/LoveIt/assets/css/_partial/_header.scss
  60. 17
      themes/LoveIt/assets/css/_partial/_icon.scss
  61. 16
      themes/LoveIt/assets/css/_partial/_mask.scss
  62. 91
      themes/LoveIt/assets/css/_partial/_pagination.scss
  63. 67
      themes/LoveIt/assets/css/_partial/_single/_admonition.scss
  64. 16
      themes/LoveIt/assets/css/_partial/_single/_bilibili.scss
  65. 399
      themes/LoveIt/assets/css/_partial/_single/_code.scss
  66. 3
      themes/LoveIt/assets/css/_partial/_single/_comment.scss
  67. 4
      themes/LoveIt/assets/css/_partial/_single/_echarts.scss
  68. 98
      themes/LoveIt/assets/css/_partial/_single/_footer.scss
  69. 5
      themes/LoveIt/assets/css/_partial/_single/_instagram.scss
  70. 4
      themes/LoveIt/assets/css/_partial/_single/_mapbox.scss
  71. 3
      themes/LoveIt/assets/css/_partial/_single/_music.scss
  72. 157
      themes/LoveIt/assets/css/_partial/_single/_toc.scss
  73. 369
      themes/LoveIt/assets/css/_variables.scss
  74. 19
      themes/LoveIt/assets/css/style.scss
  75. 61
      themes/LoveIt/assets/data/cdn/jsdelivr.yml
  76. 150
      themes/LoveIt/assets/data/emoji/apple.yml
  77. 150
      themes/LoveIt/assets/data/emoji/facebook.yml
  78. 150
      themes/LoveIt/assets/data/emoji/google.yml
  79. 150
      themes/LoveIt/assets/data/emoji/twitter.yml
  80. 18
      themes/LoveIt/assets/data/polyfill.yml
  81. 511
      themes/LoveIt/assets/data/social.yml
  82. 1058
      themes/LoveIt/assets/js/theme.js
  83. 24
      themes/LoveIt/assets/lib/VERSION
  84. 8
      themes/LoveIt/assets/lib/algoliasearch/algoliasearch-lite.umd.min.js
  85. 7
      themes/LoveIt/assets/lib/animate/animate.min.css
  86. 3
      themes/LoveIt/assets/lib/aplayer/APlayer.min.css
  87. 2
      themes/LoveIt/assets/lib/aplayer/APlayer.min.js
  88. 112
      themes/LoveIt/assets/lib/aplayer/dark.scss
  89. 7
      themes/LoveIt/assets/lib/autocomplete/autocomplete.min.js
  90. 7
      themes/LoveIt/assets/lib/clipboard/clipboard.min.js
  91. 6
      themes/LoveIt/assets/lib/cookieconsent/cookieconsent.min.css
  92. 1
      themes/LoveIt/assets/lib/cookieconsent/cookieconsent.min.js
  93. 45
      themes/LoveIt/assets/lib/echarts/echarts.min.js
  94. 273
      themes/LoveIt/assets/lib/echarts/theme/dark.yml
  95. 297
      themes/LoveIt/assets/lib/echarts/theme/light.yml
  96. 6
      themes/LoveIt/assets/lib/fontawesome-free/all.min.css
  97. 1251
      themes/LoveIt/assets/lib/gitalk/gitalk.css
  98. 35
      themes/LoveIt/assets/lib/gitalk/gitalk.min.js
  99. 1
      themes/LoveIt/assets/lib/katex/auto-render.min.js
  100. 1
      themes/LoveIt/assets/lib/katex/copy-tex.min.css
  101. Some files were not shown because too many files have changed in this diff Show More

@ -0,0 +1,5 @@
FROM alpine
RUN apk add git hugo
WORKDIR /app
COPY . /app
CMD hugo server --bind 0.0.0.0

@ -1,2 +1 @@
# website

@ -0,0 +1,6 @@
---
title: "{{ replace .Name "-" " " | title }}"
date: {{ .Date }}
draft: true
---

@ -0,0 +1,10 @@
// ==============================
// Custom style
// ==============================
.home .home-profile,
.home[data-home="posts"] {
.home-avatar img {
width: 12rem;
}
}

@ -0,0 +1,3 @@
// ==============================
// Override Variables
// ==============================

Binary file not shown.

After

Width:  |  Height:  |  Size: 875 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 3.8 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 84 KiB

@ -0,0 +1,305 @@
baseurl: "http://localhost:1313"
title: JILITS
languageCode: en-us
theme: LoveIt
defaultContentLanguage: en
languageCode: en
languageName: English
hasCJKLanguage: false
paginate: 12
googleAnalytics: ''
copyright: ''
enableRobotsTXT: true
enableGitInfo: true
enableEmoji: true
author:
name: Emil Dabrowski
link: 'https://www.linkedin.com/in/dbrski/'
menu:
main:
- weight: 1
identifier: posts
pre: ''
post: ''
name: Posts
url: /posts/
title: ''
- weight: 2
identifier: about
pre: ''
post: ''
name: About
url: /about/
title: ''
- weight: 3
identifier: gitea
pre: <i class='fab fa-git-alt fa-fw' aria-hidden='true'></i>
post: ''
name: ''
url: 'https://git.jilits.se/JILITS/website'
title: Gitea
params:
title: JILITS
description: Cloud Agnostic Computing
defaultTheme: auto
dateFormat: '2006-01-02'
gitRepo: 'https://git.jilits.se/JILITS/website'
# website images for Open Graph and Twitter Cards
images:
- /images/screenshot.png
header:
desktopMode: fixed
mobileMode: auto
title:
logo: '/images/logo.png'
name: ''
post: ''
typeit: false
home:
rss: 10
profile:
enable: true
avatarURL: /images/avatar.png
title: 'Emil Dabrowski // JILITS'
subtitle: 'Cloud Agnostic DevOps Consulting'
typeit: true
social: true
disclaimer: ''
posts:
enable: false
social:
Gitea: https://git.jilits.se/explore/repos
Telegram: dbrski
Linkedin: dbrski
footer:
enable: true
custom: ''
hugo: false
copyright: true
author: true
since: 2022
license: >-
<a rel="license external nofollow noopener noreffer"
href="https://creativecommons.org/licenses/by-nc/4.0/" target="_blank">CC
BY-NC 4.0</a>
section:
paginate: 20
dateFormat: 01-02
rss: 10
list:
paginate: 20
dateFormat: 01-02
rss: 10
app:
title: JILITS
noFavicon: false
svgFavicon: 'favicon.svg'
themeColor: '#ffffff'
iconColor: '#ffffff'
tileColor: '#ffffff'
search:
enable: false
page:
hiddenFromHomePage: false
hiddenFromSearch: false
twemoji: false
lightgallery: false
ruby: true
fraction: true
fontawesome: true
linkToMarkdown: true
rssFullText: false
toc:
enable: true
keepStatic: false
auto: true
code:
copy: true
maxShownLines: 50
math:
enable: false
inlineLeftDelimiter: ''
inlineRightDelimiter: ''
blockLeftDelimiter: ''
blockRightDelimiter: ''
copyTex: true
mhchem: true
comment:
enable: false
share:
enable: true
Twitter: true
Facebook: true
Linkedin: true
Whatsapp: false
Pinterest: false
Tumblr: false
HackerNews: false
Reddit: false
VK: false
Buffer: false
Xing: false
Line: false
Instapaper: false
Pocket: false
Flipboard: false
Weibo: false
Blogger: false
Baidu: false
Odnoklassniki: false
Evernote: false
Skype: false
Trello: false
Mix: false
# # FIXME
# seo:
# images: []
# publisher:
# name: xxxx
# logoUrl: /images/avatar.png
typeit:
speed: 75
cursorSpeed: 1000
cursorChar: '|'
duration: -1
# # FIXME
# verification:
# google: ''
# bing: ''
# yandex: ''
# pinterest: ''
# baidu: ''
seo:
thumbnailUrl: /images/screenshot.png
analytics:
enable: false
cdn:
data: jsdelivr.yml
compatibility:
polyfill: false
objectFit: false
markup:
highlight:
codeFences: true
guessSyntax: true
lineNos: true
lineNumbersInTable: true
noClasses: false
goldmark:
extensions:
definitionList: true
footnote: true
linkify: true
strikethrough: true
table: true
taskList: true
typographer: true
renderer:
unsafe: true
tableOfContents:
startLevel: 2
endLevel: 6
sitemap:
changefreq: weekly
filename: sitemap.xml
priority: 0.5
Permalinks:
posts: ':filename'
privacy:
googleAnalytics: {}
twitter:
enableDNT: true
youtube:
privacyEnhanced: true
mediaTypes:
text/plain:
suffixes:
- md
outputFormats:
MarkDown:
mediaType: text/plain
isPlainText: true
isHTML: false
outputs:
home:
- HTML
- RSS
- JSON
page:
- HTML
- MarkDown
section:
- HTML
- RSS
taxonomy:
- HTML
- RSS
taxonomyTerm:
- HTML
languages:
en:
weight: 1
languageCode: en
languageName: English
hasCJKLanguage: false
copyright: >-
This work is licensed under a Creative Commons Attribution-NonCommercial
4.0 International License.
sv:
weight: 1
languageCode: sv
languageName: Svenska
hasCJKLanguage: false
copyright: >-
Detta arbete är licensierat under en Creative Commons Attribution-NonCommercial
4.0 Internationell licens.
params:
home:
profile:
enable: true
avatarURL: /images/avatar.png
title: 'Emil Dabrowski // JILITS'
subtitle: 'Molnagnostisk DevOps-konsultation'
typeit: true
social: true
disclaimer: ''

@ -0,0 +1,25 @@
#!/bin/bash
version="0.1.0"
script_dir=$( cd -- "$( dirname -- "${BASH_SOURCE[0]}" )" &> /dev/null && pwd )
tmp_dir="$(mktemp -d --suffix=-web)"
cleanup () { rm -Rfv "$tmp_dir"; }
trap cleanup EXIT
theme_dir="$script_dir/themes/LoveIt"
release_json="$theme_dir/release.json"
latest_theme_release_metadata="$(curl -s https://api.github.com/repos/dillonzq/LoveIt/releases/latest)" || exit 1
latest_theme_tag_name="$(jq -r .tag_name <<<"${latest_theme_release_metadata:?}")" || exit 2
previous_theme_tag_name="$(jq -r .tag_name "$release_json" 2>/dev/null)" || exit 3
if [[ "$latest_theme_tag_name" != "$previous_theme_tag_name" ]]; then
echo "Updating theme: '$latest_theme_tag_name' != '$previous_theme_tag_name'"
curl -L "https://github.com/dillonzq/LoveIt/archive/refs/tags/${latest_theme_tag_name:?}.tar.gz" -o "$tmp_dir/theme.tgz" || exit 11
tar -xvf "$tmp_dir/theme.tgz" -C "$tmp_dir" || exit 12
[ -d "$theme_dir" ] && { rm -Rv "$theme_dir"* || exit 13; }
mv "$tmp_dir/LoveIt"* "$theme_dir" || exit 14
rm -Rv "$theme_dir/exampleSite"
echo "$latest_theme_release_metadata" >"$release_json"
fi
docker build "$script_dir" -f Containerfile -t jilits/website:latest -t jilits/website:$version

@ -0,0 +1,64 @@
---
title: "About us"
date: 2022-12-01T18:04:49+01:00
draft: false
description: "About JILITS"
images: ["wp2535788-1280px.jpg"]
lightgallery: true
---
![Hoggar Mountains](wp2535788-1280px.jpg)
## Background
JILITS is a christian consulting company with a focus on server application hosting with a cloud agnostic approach. Cloud agnostic refers to a cloud design strategy in which applications, tools, and services are designed to migrate seamlessly between multiple cloud platforms or between on-premises and cloud in a hybrid model without disruption of service. Some of the tenets of a cloud-agnostic approach are to support seamless portability independent of the underlying operating system, to ensure limited disruption of the workloads in migration, and to limit the risk of application downtime while enhancing cost efficiencies. The company is run by [Emil Dabrowski](https://www.linkedin.com/in/dbrski/) and was founded in April 2021.
## Expertise
Cloud Native:
- [FluxCD](https://fluxcd.io)
- [Grafana](https://grafana.com)
- [Helm](https://helm.sh)
- [Kubernetes](https://kubernetes.io)
- [Prometheus](https://prometheus.io)
- [Thanos](https://thanos.io)
- [Tekton](https://tekton.dev)
Cloud providers:
- Amazon Web Services (AWS)
- Azure
Database engines:
- MariaDB
- PostgreSQL
Programming languages:
- Bash
- Terraform
- Python
- Ansible
Networking:
- DNS
- Routing
- Firewalls
- VPNs
Operating systems:
- Debian
- Ubuntu
- Manjaro
- Amazon Linux
Platforms:
- Docker
- Proxmox
- vSphere

@ -0,0 +1,67 @@
---
title: "Om oss"
date: 2022-12-01T18:04:49+01:00
draft: false
description: "Om JILITS"
# images: ["/Apple-Devices-Preview.png"]
lightgallery: true
math:
enable: true
---
![Hoggar Mountains](/img/wp2535788-1280px.jpg)
## Bakgrund
JILITS är ett kristet konsultbolag med fokus på serverapplikationsdrift med ett molnagnostisk tillvägagångssätt. Molnagnostisism hänvisar till en molndesignstrategi där applikationer, verktyg och tjänster är utformade för att migrera sömlöst mellan flera molnplattformar eller mellan on-prem och moln i en hybridmodell utan avbrott i tjänsten. Några av grundsatserna för ett moln-agnostiskt tillvägagångssätt är att stödja sömlös portabilitet oberoende av det underliggande operativsystemet, för att säkerställa begränsade avbrott i arbetsbelastningen vid migrering, och att begränsa risken för programavbrott samtidigt som kostnadseffektiviteten förbättras. Företaget drivs av [Emil Dabrowski](https://www.linkedin.com/in/dbrski/) och grundades i april 2021.
## Expertis
Cloud Native:
- [FluxCD](https://fluxcd.io)
- [Grafana](https://grafana.com)
- [Helm](https://helm.sh)
- [Kubernetes](https://kubernetes.io)
- [Prometheus](https://prometheus.io)
- [Thanos](https://thanos.io)
- [Tekton](https://tekton.dev)
Molnleverantörer:
- Amazon Web Services (AWS)
- Azure
Databasmotorer:
- MariaDB
- PostgreSQL
Programmeringsspråk:
- Bash
- Terraform
- Python
- Ansible
Nätverk:
- DNS
- Routing
- Brandväggar
- VPNs
Operativsystem:
- Debian
- Ubuntu
- Manjaro
- Amazon Linux
Plattformar:
- Docker
- Proxmox
- vSphere

Binary file not shown.

After

Width:  |  Height:  |  Size: 72 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 74 KiB

@ -0,0 +1,31 @@
---
weight: 1
title: "First post"
date: 2022-12-01T18:04:49+01:00
draft: false
description: "Just a greeting!"
images: []
resources:
- name: "featured-image"
src: "featured-image.png"
toc:
enable: false
---
Dear visitor,
I'm happy that you've found your way to my website. Surely there's not much here, but perhaps you might find some of the tech on the list below useful on your journey through the internet galaxy 😎
- [Kubernetes](https://kubernetes.io)
- [Helm](https://helm.sh)
- [FluxCD](https://fluxcd.io)
- [Tekton](https://tekton.dev)
- [Grafana](https://grafana.com)
- [Prometheus](https://prometheus.io)
- [Thanos](https://thanos.io)
Greetings,
Emil

@ -0,0 +1,771 @@
---
weight: 4
title: "Markdown 基本语法"
date: 2019-12-01T21:57:40+08:00
lastmod: 2020-01-01T16:45:40+08:00
draft: false
author: "Dillon"
authorLink: "https://dillonzq.com"
description: "这篇文章展示了基本的 Markdown 语法和格式."
images: []
resources:
- name: "featured-image"
src: "featured-image.png"
tags: ["Markdown", "HTML"]
categories: ["Markdown"]
lightgallery: true
---
这篇文章提供了可以在 Hugo 的文章中使用的基本 Markdown 语法示例.
<!--more-->
{{< admonition >}}
这篇文章借鉴了一篇很棒的[来自 Grav 的文章](http://learn.getgrav.org/content/markdown).
如果你想了解 **Loveit** 主题的扩展 Markdown 语法, 请阅读[扩展 Markdown 语法页面](../theme-documentation-content#extended-markdown-syntax).
{{< /admonition >}}
事实上, 编写 Web 内容很麻烦. [WYSIWYG]^(所见即所得) 编辑器帮助减轻了这一任务. 但通常会导致代码太糟, 或更糟糕的是, 网页也会很丑.
没有通常伴随的所有复杂和丑陋的问题, **Markdown** 是一种更好的生成 **HTML** 内容的方式.
一些主要好处是:
1. Markdown 简单易学, 几乎没有多余的字符, 因此编写内容也更快.
2. 用 Markdown 书写时出错的机会更少.
3. 可以产生有效的 XHTML 输出.
4. 将内容和视觉显示保持分开, 这样就不会打乱网站的外观.
5. 可以在你喜欢的任何文本编辑器或 Markdown 应用程序中编写内容.
6. Markdown 使用起来很有趣!
John Gruber, Markdown 的作者如是说:
> Markdown 格式的首要设计目标是更具可读性.
> 最初的想法是 Markdown 格式的文档应当以纯文本形式发布,
> 而不会看起来像被标签或格式说明所标记.
> 虽然 Markdown 的语法受到几种现有的文本到 HTML 转换工具的影响,
> 但 Markdown 语法的最大灵感来源是纯文本电子邮件的格式.
>
> {{< style "text-align: right;" >}}-- _John Gruber_{{< /style >}}
话不多说, 我们来回顾一下 Markdown 的主要语法以及生成的 HTML 样式!
{{< admonition tip >}}
:(far fa-bookmark fa-fw): 将此页保存为书签,以备将来参考!
{{< /admonition >}}
## 1 标题
`h2``h6` 的标题在每个级别上都加上一个 `#`:
```markdown
## h2 标题
### h3 标题
#### h4 标题
##### h5 标题
###### h6 标题
```
输出的 HTML 看起来像这样:
```html
<h2>h2 标题</h2>
<h3>h3 标题</h3>
<h4>h4 标题</h4>
<h5>h5 标题</h5>
<h6>h6 标题</h6>
```
{{< admonition note "标题 ID" >}}
要添加自定义标题 ID, 请在与标题相同的行中将自定义 ID 放在花括号中:
```markdown
### 一个很棒的标题 {#custom-id}
```
输出的 HTML 看起来像这样:
```html
<h3 id="custom-id">一个很棒的标题</h3>
```
{{< /admonition >}}
## 2 注释
注释是和 HTML 兼容的:
```html
<!--
这是一段注释
-->
```
**不能**看到以下的注释:
<!--
这是一段注释
-->
## 3 水平线
HTML 中的 `<hr>` 标签是用来在段落元素之间创建一个 "专题间隔" 的.
使用 Markdown, 你可以用以下方式创建一个 `<hr>` 标签:
* `___`: 三个连续的下划线
* `---`: 三个连续的破折号
* `***`: 三个连续的星号
呈现的输出效果如下:
___
---
***
## 4 段落
按照纯文本的方式书写段落, 纯文本在呈现的 HTML 中将用 `<p>`/`</p>` 标签包裹.
如下段落:
```markdown
Lorem ipsum dolor sit amet, graecis denique ei vel, at duo primis mandamus. Et legere ocurreret pri,
animal tacimates complectitur ad cum. Cu eum inermis inimicus efficiendi. Labore officiis his ex,
soluta officiis concludaturque ei qui, vide sensibus vim ad.
```
输出的 HTML 看起来像这样:
```html
<p>Lorem ipsum dolor sit amet, graecis denique ei vel, at duo primis mandamus. Et legere ocurreret pri, animal tacimates complectitur ad cum. Cu eum inermis inimicus efficiendi. Labore officiis his ex, soluta officiis concludaturque ei qui, vide sensibus vim ad.</p>
```
可以使用一个空白行进行**换行**.
## 5 内联 HTML 元素
如果你需要某个 HTML 标签 (带有一个类), 则可以简单地像这样使用:
```html
Markdown 格式的段落.
<div class="class">
这是 <b>HTML</b>
</div>
Markdown 格式的段落.
```
## 6 强调
### 加粗
用于强调带有较粗字体的文本片段.
以下文本片段会被 **渲染为粗体**.
```markdown
**渲染为粗体**
__渲染为粗体__
```
输出的 HTML 看起来像这样:
```html
<strong>渲染为粗体</strong>
```
### 斜体
用于强调带有斜体的文本片段.
以下文本片段被 _渲染为斜体_.
```markdown
*渲染为斜体*
_渲染为斜体_
```
输出的 HTML 看起来像这样:
```html
<em>渲染为斜体</em>
```
### 删除线
按照 [[GFM]^(GitHub flavored Markdown)](https://github.github.com/gfm/) 你可以使用删除线.
```markdown
~~这段文本带有删除线.~~
```
呈现的输出效果如下:
~~这段文本带有删除线.~~
输出的 HTML 看起来像这样:
```html
<del>这段文本带有删除线.</del>
```
### 组合
加粗, 斜体, 和删除线可以 组合使用.
```markdown
***加粗和斜体***
~~**删除线和加粗**~~
~~*删除线和斜体*~~
~~***加粗, 斜体和删除线***~~
```
呈现的输出效果如下:
***加粗和斜体***
~~**删除线和加粗**~~
~~*删除线和斜体*~~
~~***加粗, 斜体和删除线***~~
输出的 HTML 看起来像这样:
```html
<em><strong>加粗和斜体</strong></em>
<del><strong>删除线和加粗</strong></del>
<del><em>删除线和斜体</em></del>
<del><em><strong>加粗, 斜体和删除线</strong></em></del>
```
## 7 引用
用于在文档中引用其他来源的内容块.
在要引用的任何文本之前添加 `>`:
```markdown
> **Fusion Drive** combines a hard drive with a flash storage (solid-state drive) and presents it as a single logical volume with the space of both drives combined.
```
呈现的输出效果如下:
> **Fusion Drive** combines a hard drive with a flash storage (solid-state drive) and presents it as a single logical volume with the space of both drives combined.
输出的 HTML 看起来像这样:
```html
<blockquote>
<p>
<strong>Fusion Drive</strong> combines a hard drive with a flash storage (solid-state drive) and presents it as a single logical volume with the space of both drives combined.
</p>
</blockquote>
```
引用也可以嵌套:
```markdown
> Donec massa lacus, ultricies a ullamcorper in, fermentum sed augue.
Nunc augue augue, aliquam non hendrerit ac, commodo vel nisi.
>> Sed adipiscing elit vitae augue consectetur a gravida nunc vehicula. Donec auctor
odio non est accumsan facilisis. Aliquam id turpis in dolor tincidunt mollis ac eu diam.
```
呈现的输出效果如下:
> Donec massa lacus, ultricies a ullamcorper in, fermentum sed augue.
Nunc augue augue, aliquam non hendrerit ac, commodo vel nisi.
>> Sed adipiscing elit vitae augue consectetur a gravida nunc vehicula. Donec auctor
odio non est accumsan facilisis. Aliquam id turpis in dolor tincidunt mollis ac eu diam.
## 8 列表
### 无序列表
一系列项的列表, 其中项的顺序没有明显关系.
你可以使用以下任何符号来表示无序列表中的项:
```markdown
* 一项内容
- 一项内容
+ 一项内容
```
例如:
```markdown
* Lorem ipsum dolor sit amet
* Consectetur adipiscing elit
* Integer molestie lorem at massa
* Facilisis in pretium nisl aliquet
* Nulla volutpat aliquam velit
* Phasellus iaculis neque
* Purus sodales ultricies
* Vestibulum laoreet porttitor sem
* Ac tristique libero volutpat at
* Faucibus porta lacus fringilla vel
* Aenean sit amet erat nunc
* Eget porttitor lorem
```
呈现的输出效果如下:
* Lorem ipsum dolor sit amet
* Consectetur adipiscing elit
* Integer molestie lorem at massa
* Facilisis in pretium nisl aliquet
* Nulla volutpat aliquam velit
* Phasellus iaculis neque
* Purus sodales ultricies
* Vestibulum laoreet porttitor sem
* Ac tristique libero volutpat at
* Faucibus porta lacus fringilla vel
* Aenean sit amet erat nunc
* Eget porttitor lorem
输出的 HTML 看起来像这样:
```html
<ul>
<li>Lorem ipsum dolor sit amet</li>
<li>Consectetur adipiscing elit</li>
<li>Integer molestie lorem at massa</li>
<li>Facilisis in pretium nisl aliquet</li>
<li>Nulla volutpat aliquam velit
<ul>
<li>Phasellus iaculis neque</li>
<li>Purus sodales ultricies</li>
<li>Vestibulum laoreet porttitor sem</li>
<li>Ac tristique libero volutpat at</li>
</ul>
</li>
<li>Faucibus porta lacus fringilla vel</li>
<li>Aenean sit amet erat nunc</li>
<li>Eget porttitor lorem</li>
</ul>
```
### 有序列表
一系列项的列表, 其中项的顺序确实很重要.
```markdown
1. Lorem ipsum dolor sit amet
2. Consectetur adipiscing elit
3. Integer molestie lorem at massa
4. Facilisis in pretium nisl aliquet
5. Nulla volutpat aliquam velit
6. Faucibus porta lacus fringilla vel
7. Aenean sit amet erat nunc
8. Eget porttitor lorem
```
呈现的输出效果如下:
1. Lorem ipsum dolor sit amet
2. Consectetur adipiscing elit
3. Integer molestie lorem at massa
4. Facilisis in pretium nisl aliquet
5. Nulla volutpat aliquam velit
6. Faucibus porta lacus fringilla vel
7. Aenean sit amet erat nunc
8. Eget porttitor lorem
输出的 HTML 看起来像这样:
```html
<ol>
<li>Lorem ipsum dolor sit amet</li>
<li>Consectetur adipiscing elit</li>
<li>Integer molestie lorem at massa</li>
<li>Facilisis in pretium nisl aliquet</li>
<li>Nulla volutpat aliquam velit</li>
<li>Faucibus porta lacus fringilla vel</li>
<li>Aenean sit amet erat nunc</li>
<li>Eget porttitor lorem</li>
</ol>
```
{{< admonition tip >}}
如果你对每一项使用 `1.`, Markdown 将自动为每一项编号. 例如:
```markdown
1. Lorem ipsum dolor sit amet
1. Consectetur adipiscing elit
1. Integer molestie lorem at massa
1. Facilisis in pretium nisl aliquet
1. Nulla volutpat aliquam velit
1. Faucibus porta lacus fringilla vel
1. Aenean sit amet erat nunc
1. Eget porttitor lorem
```
呈现的输出效果如下:
1. Lorem ipsum dolor sit amet
1. Consectetur adipiscing elit
1. Integer molestie lorem at massa
1. Facilisis in pretium nisl aliquet
1. Nulla volutpat aliquam velit
1. Faucibus porta lacus fringilla vel
1. Aenean sit amet erat nunc
1. Eget porttitor lorem
{{< /admonition >}}
### 任务列表
任务列表使你可以创建带有复选框的列表.
要创建任务列表, 请在任务列表项之前添加破折号 (`-`) 和带有空格的方括号 (`[ ]`). 要选择一个复选框,请在方括号之间添加 x (`[x]`).
```markdown
- [x] Write the press release
- [ ] Update the website
- [ ] Contact the media
```
呈现的输出效果如下:
- [x] Write the press release
- [ ] Update the website
- [ ] Contact the media
## 9 代码
### 行内代码
<code>`</code> 包装行内代码段.
```markdown
在这个例子中, `<section></section>` 会被包裹成 **代码**.
```
呈现的输出效果如下:
在这个例子中, `<section></section>` 会被包裹成 **代码**.
输出的 HTML 看起来像这样:
```html
<p>
在这个例子中, <code>&lt;section&gt;&lt;/section&gt;</code> 会被包裹成 <strong>代码</strong>.
</p>
```
### 缩进代码
将几行代码缩进至少四个空格,例如:
```markdown
// Some comments
line 1 of code
line 2 of code
line 3 of code
```
呈现的输出效果如下:
// Some comments
line 1 of code
line 2 of code
line 3 of code
输出的 HTML 看起来像这样:
```html
<pre>
<code>
// Some comments
line 1 of code
line 2 of code
line 3 of code
</code>
</pre>
```
### 围栏代码块
使用 "围栏" <code>```</code> 来生成一段带有语言属性的代码块.
{{< highlight markdown >}}
```markdown
Sample text here...
```
{{< / highlight >}}
输出的 HTML 看起来像这样:
```html
<pre language-html>
<code>Sample text here...</code>
</pre>
```
### 语法高亮
[GFM]^(GitHub Flavored Markdown) 也支持语法高亮.
要激活它,只需在第一个代码 "围栏" 之后直接添加你要使用的语言的文件扩展名,
<code>```js</code>, 语法高亮显示将自动应用于渲染的 HTML 中.
例如, 在以下 JavaScript 代码中应用语法高亮:
{{< highlight markdown >}}
```js
grunt.initConfig({
assemble: {
options: {
assets: 'docs/assets',
data: 'src/data/*.{json,yml}',
helpers: 'src/custom-helpers.js',
partials: ['src/partials/**/*.{hbs,md}']
},
pages: {
options: {
layout: 'default.hbs'
},
files: {
'./': ['src/templates/pages/index.hbs']
}
}
}
};
```
{{< / highlight >}}
呈现的输出效果如下:
```js
grunt.initConfig({
assemble: {
options: {
assets: 'docs/assets',
data: 'src/data/*.{json,yml}',
helpers: 'src/custom-helpers.js',
partials: ['src/partials/**/*.{hbs,md}']
},
pages: {
options: {
layout: 'default.hbs'
},
files: {
'./': ['src/templates/pages/index.hbs']
}
}
}
};
```
{{< admonition >}}
**Hugo** 文档中的 [语法高亮页面](https://gohugo.io/content-management/syntax-highlighting/) 介绍了有关语法高亮的更多信息,
包括语法高亮的 shortcode.
{{< /admonition >}}
## 10 表格
通过在每个单元格之间添加竖线作为分隔线, 并在标题下添加一行破折号 (也由竖线分隔) 来创建表格. 注意, 竖线不需要垂直对齐.
```markdown
| Option | Description |
| ------ | ----------- |
| data | path to data files to supply the data that will be passed into templates. |
| engine | engine to be used for processing templates. Handlebars is the default. |
| ext | extension to be used for dest files. |
```
呈现的输出效果如下:
| Option | Description |
| ------ | ----------- |
| data | path to data files to supply the data that will be passed into templates. |
| engine | engine to be used for processing templates. Handlebars is the default. |
| ext | extension to be used for dest files. |
输出的 HTML 看起来像这样:
```html
<table>
<thead>
<tr>
<th>Option</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr>
<td>data</td>
<td>path to data files to supply the data that will be passed into templates.</td>
</tr>
<tr>
<td>engine</td>
<td>engine to be used for processing templates. Handlebars is the default.</td>
</tr>
<tr>
<td>ext</td>
<td>extension to be used for dest files.</td>
</tr>
</tbody>
</table>
```
{{< admonition note "文本右对齐或居中对齐" >}}
在任何标题下方的破折号右侧添加冒号将使该列的文本右对齐.
在任何标题下方的破折号两边添加冒号将使该列的对齐文本居中.
```markdown
| Option | Description |
|:------:| -----------:|
| data | path to data files to supply the data that will be passed into templates. |
| engine | engine to be used for processing templates. Handlebars is the default. |
| ext | extension to be used for dest files. |
```
呈现的输出效果如下:
| Option | Description |
|:------:| -----------:|
| data | path to data files to supply the data that will be passed into templates. |
| engine | engine to be used for processing templates. Handlebars is the default. |
| ext | extension to be used for dest files. |
{{< /admonition >}}
## 11 链接 {#links}
### 基本链接
```markdown
<https://assemble.io>
<contact@revolunet.com>
[Assemble](https://assemble.io)
```
呈现的输出效果如下 (将鼠标悬停在链接上,没有提示):
<https://assemble.io>
<contact@revolunet.com>
[Assemble](https://assemble.io)
输出的 HTML 看起来像这样:
```html
<a href="https://assemble.io">https://assemble.io</a>
<a href="mailto:contact@revolunet.com">contact@revolunet.com</a>
<a href="https://assemble.io">Assemble</a>
```
### 添加一个标题
```markdown
[Upstage](https://github.com/upstage/ "Visit Upstage!")
```
呈现的输出效果如下 (将鼠标悬停在链接上,会有一行提示):
[Upstage](https://github.com/upstage/ "Visit Upstage!")
输出的 HTML 看起来像这样:
```html
<a href="https://github.com/upstage/" title="Visit Upstage!">Upstage</a>
```
### 定位标记
定位标记使你可以跳至同一页面上的指定锚点. 例如, 每个章节:
```markdown
## Table of Contents
* [Chapter 1](#chapter-1)
* [Chapter 2](#chapter-2)
* [Chapter 3](#chapter-3)
```
将跳转到这些部分:
```markdown
## Chapter 1 <a id="chapter-1"></a>
Content for chapter one.
## Chapter 2 <a id="chapter-2"></a>
Content for chapter one.
## Chapter 3 <a id="chapter-3"></a>
Content for chapter one.
```
{{< admonition >}}
定位标记的位置几乎是任意的. 因为它们并不引人注目, 所以它们通常被放在同一行了.
{{< /admonition >}}
## 12 脚注
脚注使你可以添加注释和参考, 而不会使文档正文混乱.
当你创建脚注时, 会在添加脚注引用的位置出现带有链接的上标编号.
读者可以单击链接以跳至页面底部的脚注内容.
要创建脚注引用, 请在方括号中添加插入符号和标识符 (`[^1]`).
标识符可以是数字或单词, 但不能包含空格或制表符.
标识符仅将脚注引用与脚注本身相关联 - 在脚注输出中, 脚注按顺序编号.
在中括号内使用插入符号和数字以及用冒号和文本来添加脚注内容 (`[^1]:这是一段脚注`).
你不一定要在文档末尾添加脚注. 可以将它们放在除列表, 引用和表格等元素之外的任何位置.
```markdown
这是一个数字脚注[^1].
这是一个带标签的脚注[^label]
[^1]: 这是一个数字脚注
[^label]: 这是一个带标签的脚注
```
这是一个数字脚注[^1].
这是一个带标签的脚注[^label]
[^1]: 这是一个数字脚注
[^label]: 这是一个带标签的脚注
## 13 图片
图片的语法与链接相似, 但包含一个在前面的感叹号.
```markdown
![Minion](https://octodex.github.com/images/minion.png)
```
![Minion](https://octodex.github.com/images/minion.png)
或者:
```markdown
![Alt text](https://octodex.github.com/images/stormtroopocat.jpg "The Stormtroopocat")
```
![Alt text](https://octodex.github.com/images/stormtroopocat.jpg "The Stormtroopocat")
像链接一样, 图片也具有脚注样式的语法:
```markdown
![Alt text][id]
```
![Alt text][id]
稍后在文档中提供参考内容, 用来定义 URL 的位置:
```markdown
[id]: https://octodex.github.com/images/dojocat.jpg "The Dojocat"
```
[id]: https://octodex.github.com/images/dojocat.jpg "The Dojocat"
{{< admonition tip >}}
**LoveIt** 主题提供了一个包含更多功能的 [图片的 shortcode](../theme-documentation-extended-shortcodes#image).
{{< /admonition >}}

Binary file not shown.

After

Width:  |  Height:  |  Size: 6.7 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 21 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 6.0 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 557 B

Binary file not shown.

After

Width:  |  Height:  |  Size: 1.0 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 15 KiB

@ -0,0 +1,747 @@
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<svg
width="94mm"
height="94mm"
viewBox="0 0 94 94"
version="1.1"
id="svg8"
sodipodi:docname="jilits-favicon-20211116-1-stroke.svg"
inkscape:version="1.2.1 (9c6d41e410, 2022-07-14, custom)"
inkscape:export-filename="/home/walter/Syncthing/private-misc/jilits/logo/jilits-20210515-1-lr.png"
inkscape:export-xdpi="150"
inkscape:export-ydpi="150"
xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape"
xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd"
xmlns:xlink="http://www.w3.org/1999/xlink"
xmlns="http://www.w3.org/2000/svg"
xmlns:svg="http://www.w3.org/2000/svg"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:cc="http://creativecommons.org/ns#"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:osb="http://www.openswatchbook.org/uri/2009/osb">
<defs
id="defs2">
<linearGradient
inkscape:collect="always"
id="linearGradient2049">
<stop
style="stop-color:#37dbd0;stop-opacity:1"
offset="0"
id="stop2045" />
<stop
style="stop-color:#22a7f0;stop-opacity:1"
offset="1"
id="stop2047" />
</linearGradient>
<linearGradient
inkscape:collect="always"
id="linearGradient1549">
<stop
style="stop-color:#22a7f0;stop-opacity:1"
offset="0"
id="stop1545" />
<stop
style="stop-color:#37dbd0;stop-opacity:1"
offset="1"
id="stop1547" />
</linearGradient>
<linearGradient
id="linearGradient3185"
osb:paint="solid">
<stop
style="stop-color:#007ff0;stop-opacity:1;"
offset="0"
id="stop3183" />
</linearGradient>
<marker
inkscape:stockid="DistanceStart"
orient="auto"
refY="0"
refX="0"
id="marker4529"
style="overflow:visible"
inkscape:isstock="true">
<g
id="g4527"
style="fill:#37dbd0;fill-opacity:1;stroke:#106b60;stroke-opacity:1">
<path
id="path4521"
d="M 0,0 H 2"
style="fill:#37dbd0;fill-opacity:1;stroke:#106b60;stroke-width:1.15;stroke-linecap:square;stroke-opacity:1" />
<path
id="path4523"
d="M 0,0 13,4 9,0 13,-4 Z"
style="fill:#37dbd0;fill-opacity:1;fill-rule:evenodd;stroke:#106b60;stroke-opacity:1" />
<path
id="path4525"
d="M 0,-4 V 40"
style="fill:#37dbd0;fill-opacity:1;stroke:#106b60;stroke-width:1;stroke-linecap:square;stroke-opacity:1" />
</g>
</marker>
<marker
inkscape:stockid="DistanceStart"
orient="auto"
refY="0"
refX="0"
id="marker4489"
style="overflow:visible"
inkscape:isstock="true">
<g
id="g4487"
style="fill:#37dbd0;fill-opacity:1;stroke:#106b60;stroke-opacity:1">
<path
id="path4481"
d="M 0,0 H 2"
style="fill:#37dbd0;fill-opacity:1;stroke:#106b60;stroke-width:1.15;stroke-linecap:square;stroke-opacity:1" />
<path
id="path4483"
d="M 0,0 13,4 9,0 13,-4 Z"
style="fill:#37dbd0;fill-opacity:1;fill-rule:evenodd;stroke:#106b60;stroke-opacity:1" />
<path
id="path4485"
d="M 0,-4 V 40"
style="fill:#37dbd0;fill-opacity:1;stroke:#106b60;stroke-width:1;stroke-linecap:square;stroke-opacity:1" />
</g>
</marker>
<marker
inkscape:stockid="DistanceStart"
orient="auto"
refY="0"
refX="0"
id="marker3802"
style="overflow:visible"
inkscape:isstock="true">
<g
id="g3800"
style="fill:#37dbd0;fill-opacity:1;stroke:#106b60;stroke-opacity:1">
<path
id="path3794"
d="M 0,0 H 2"
style="fill:#37dbd0;fill-opacity:1;stroke:#106b60;stroke-width:1.15;stroke-linecap:square;stroke-opacity:1" />
<path
id="path3796"
d="M 0,0 13,4 9,0 13,-4 Z"
style="fill:#37dbd0;fill-opacity:1;fill-rule:evenodd;stroke:#106b60;stroke-opacity:1" />
<path
id="path3798"
d="M 0,-4 V 40"
style="fill:#37dbd0;fill-opacity:1;stroke:#106b60;stroke-width:1;stroke-linecap:square;stroke-opacity:1" />
</g>
</marker>
<marker
inkscape:stockid="DistanceStart"
orient="auto"
refY="0"
refX="0"
id="marker3576"
style="overflow:visible"
inkscape:isstock="true">
<g
id="g3574"
style="fill:#37dbd0;fill-opacity:1;stroke:#106b60;stroke-opacity:1">
<path
id="path3568"
d="M 0,0 H 2"
style="fill:#37dbd0;fill-opacity:1;stroke:#106b60;stroke-width:1.15;stroke-linecap:square;stroke-opacity:1" />
<path
id="path3570"