remove placeholder posts

2024-11-15 20:44:10 +03:00 · 2024-11-15 20:44:10 +03:00 · dd99a9b433
commit dd99a9b433
parent bce4c71cce
4 changed files with 0 additions and 893 deletions
--- a/_posts/2019-08-08-text-and-typography.md
+++ b/_posts/2019-08-08-text-and-typography.md
@ -1,200 +0,0 @@
 ---
 title: Text and Typography
 description: Examples of text, typography, math equations, diagrams, flowcharts, pictures, videos, and more.
 author: cotes
 date: 2019-08-08 11:33:00 +0800
 categories: [Blogging, Demo]
 tags: [typography]
 pin: true
 math: true
 mermaid: true
 image:
  path: /commons/devices-mockup.png
  lqip: data:image/webp;base64,UklGRpoAAABXRUJQVlA4WAoAAAAQAAAADwAABwAAQUxQSDIAAAARL0AmbZurmr57yyIiqE8oiG0bejIYEQTgqiDA9vqnsUSI6H+oAERp2HZ65qP/VIAWAFZQOCBCAAAA8AEAnQEqEAAIAAVAfCWkAALp8sF8rgRgAP7o9FDvMCkMde9PK7euH5M1m6VWoDXf2FkP3BqV0ZYbO6NA/VFIAAAA
  alt: Responsive rendering of Chirpy theme on multiple devices.
 ---
 ## Headings
 <!-- markdownlint-capture -->
 <!-- markdownlint-disable -->
 # H1 — heading
 {: .mt-4 .mb-0 }
 ## H2 — heading
 {: data-toc-skip='' .mt-4 .mb-0 }
 ### H3 — heading
 {: data-toc-skip='' .mt-4 .mb-0 }
 #### H4 — heading
 {: data-toc-skip='' .mt-4 }
 <!-- markdownlint-restore -->
 ## Paragraph
 Quisque egestas convallis ipsum, ut sollicitudin risus tincidunt a. Maecenas interdum malesuada egestas. Duis consectetur porta risus, sit amet vulputate urna facilisis ac. Phasellus semper dui non purus ultrices sodales. Aliquam ante lorem, ornare a feugiat ac, finibus nec mauris. Vivamus ut tristique nisi. Sed vel leo vulputate, efficitur risus non, posuere mi. Nullam tincidunt bibendum rutrum. Proin commodo ornare sapien. Vivamus interdum diam sed sapien blandit, sit amet aliquam risus mattis. Nullam arcu turpis, mollis quis laoreet at, placerat id nibh. Suspendisse venenatis eros eros.
 ## Lists
 ### Ordered list
 1. Firstly
 2. Secondly
 3. Thirdly
 ### Unordered list
 - Chapter
  - Section
    - Paragraph
 ### ToDo list
 - [ ] Job
  - [x] Step 1
  - [x] Step 2
  - [ ] Step 3
 ### Description list
 Sun
 : the star around which the earth orbits
 Moon
 : the natural satellite of the earth, visible by reflected light from the sun
 ## Block Quote
 > This line shows the _block quote_.
 ## Prompts
 <!-- markdownlint-capture -->
 <!-- markdownlint-disable -->
 > An example showing the `tip` type prompt.
 {: .prompt-tip }
 > An example showing the `info` type prompt.
 {: .prompt-info }
 > An example showing the `warning` type prompt.
 {: .prompt-warning }
 > An example showing the `danger` type prompt.
 {: .prompt-danger }
 <!-- markdownlint-restore -->
 ## Tables
 | Company                      | Contact          | Country |
 | :--------------------------- | :--------------- | ------: |
 | Alfreds Futterkiste          | Maria Anders     | Germany |
 | Island Trading               | Helen Bennett    |      UK |
 | Magazzini Alimentari Riuniti | Giovanni Rovelli |   Italy |
 ## Links
 <http://127.0.0.1:4000>
 ## Footnote
 Click the hook will locate the footnote[^footnote], and here is another footnote[^fn-nth-2].
 ## Inline code
 This is an example of `Inline Code`.
 ## Filepath
 Here is the `/path/to/the/file.extend`{: .filepath}.
 ## Code blocks
 ### Common
 ```text
 This is a common code snippet, without syntax highlight and line number.
 ```
 ### Specific Language
 ```bash
 if [ $? -ne 0 ]; then
  echo "The command was not successful.";
  #do the needful / exit
 fi;
 ```
 ### Specific filename
 ```sass
@import
  "colors/light-typography",
  "colors/dark-typography";
 ```
 {: file='_sass/jekyll-theme-chirpy.scss'}
 ## Mathematics
 The mathematics powered by [**MathJax**](https://www.mathjax.org/):
 $$
 \begin{equation}
  \sum_{n=1}^\infty 1/n^2 = \frac{\pi^2}{6}
  \label{eq:series}
 \end{equation}
 $$
 We can reference the equation as \eqref{eq:series}.
 When $a \ne 0$, there are two solutions to $ax^2 + bx + c = 0$ and they are
 $$ x = {-b \pm \sqrt{b^2-4ac} \over 2a} $$
 ## Mermaid SVG
 ```mermaid
 gantt
  title  Adding GANTT diagram functionality to mermaid
  apple :a, 2017-07-20, 1w
  banana :crit, b, 2017-07-23, 1d
  cherry :active, c, after b a, 1d
 ```
 ## Images
 ### Default (with caption)
 ![Desktop View](/posts/20190808/mockup.png){: width="972" height="589" }
 _Full screen width and center alignment_
 ### Left aligned
 ![Desktop View](/posts/20190808/mockup.png){: width="972" height="589" .w-75 .normal}
 ### Float to left
 ![Desktop View](/posts/20190808/mockup.png){: width="972" height="589" .w-50 .left}
 Praesent maximus aliquam sapien. Sed vel neque in dolor pulvinar auctor. Maecenas pharetra, sem sit amet interdum posuere, tellus lacus eleifend magna, ac lobortis felis ipsum id sapien. Proin ornare rutrum metus, ac convallis diam volutpat sit amet. Phasellus volutpat, elit sit amet tincidunt mollis, felis mi scelerisque mauris, ut facilisis leo magna accumsan sapien. In rutrum vehicula nisl eget tempor. Nullam maximus ullamcorper libero non maximus. Integer ultricies velit id convallis varius. Praesent eu nisl eu urna finibus ultrices id nec ex. Mauris ac mattis quam. Fusce aliquam est nec sapien bibendum, vitae malesuada ligula condimentum.
 ### Float to right
 ![Desktop View](/posts/20190808/mockup.png){: width="972" height="589" .w-50 .right}
 Praesent maximus aliquam sapien. Sed vel neque in dolor pulvinar auctor. Maecenas pharetra, sem sit amet interdum posuere, tellus lacus eleifend magna, ac lobortis felis ipsum id sapien. Proin ornare rutrum metus, ac convallis diam volutpat sit amet. Phasellus volutpat, elit sit amet tincidunt mollis, felis mi scelerisque mauris, ut facilisis leo magna accumsan sapien. In rutrum vehicula nisl eget tempor. Nullam maximus ullamcorper libero non maximus. Integer ultricies velit id convallis varius. Praesent eu nisl eu urna finibus ultrices id nec ex. Mauris ac mattis quam. Fusce aliquam est nec sapien bibendum, vitae malesuada ligula condimentum.
 ### Dark/Light mode & Shadow
 The image below will toggle dark/light mode based on theme preference, notice it has shadows.
 ![light mode only](/posts/20190808/devtools-light.png){: .light .w-75 .shadow .rounded-10 w='1212' h='668' }
 ![dark mode only](/posts/20190808/devtools-dark.png){: .dark .w-75 .shadow .rounded-10 w='1212' h='668' }
 ## Video
 {% include embed/youtube.html id='Balreaj8Yqs' %}
 ## Reverse Footnote
 [^footnote]: The footnote source
 [^fn-nth-2]: The 2nd footnote source
--- a/_posts/2019-08-08-write-a-new-post.md
+++ b/_posts/2019-08-08-write-a-new-post.md
@ -1,505 +0,0 @@
 ---
 title: Writing a New Post
 author: cotes
 date: 2019-08-08 14:10:00 +0800
 categories: [Blogging, Tutorial]
 tags: [writing]
 render_with_liquid: false
 ---
 This tutorial will guide you how to write a post in the _Chirpy_ template, and it's worth reading even if you've used Jekyll before, as many features require specific variables to be set.
 ## Naming and Path
 Create a new file named `YYYY-MM-DD-TITLE.EXTENSION`{: .filepath} and put it in the `_posts`{: .filepath} of the root directory. Please note that the `EXTENSION`{: .filepath} must be one of `md`{: .filepath} and `markdown`{: .filepath}. If you want to save time of creating files, please consider using the plugin [`Jekyll-Compose`](https://github.com/jekyll/jekyll-compose) to accomplish this.
 ## Front Matter
 Basically, you need to fill the [Front Matter](https://jekyllrb.com/docs/front-matter/) as below at the top of the post:
 ```yaml
 ---
 title: TITLE
 date: YYYY-MM-DD HH:MM:SS +/-TTTT
 categories: [TOP_CATEGORIE, SUB_CATEGORIE]
 tags: [TAG]     # TAG names should always be lowercase
 ---
 ```
 > The posts' _layout_ has been set to `post` by default, so there is no need to add the variable _layout_ in the Front Matter block.
 {: .prompt-tip }
 ### Timezone of Date
 To accurately record the release date of a post, you should not only set up the `timezone` of `_config.yml`{: .filepath} but also provide the post's timezone in variable `date` of its Front Matter block. Format: `+/-TTTT`, e.g. `+0800`.
 ### Categories and Tags
 The `categories` of each post are designed to contain up to two elements, and the number of elements in `tags` can be zero to infinity. For instance:
 ```yaml
 ---
 categories: [Animal, Insect]
 tags: [bee]
 ---
 ```
 ### Author Information
 The author information of the post usually does not need to be filled in the _Front Matter_ , they will be obtained from variables `social.name` and the first entry of `social.links` of the configuration file by default. But you can also override it as follows:
 Adding author information in `_data/authors.yml` (If your website doesn't have this file, don't hesitate to create one).
 ```yaml
 <author_id>:
  name: <full name>
  twitter: <twitter_of_author>
  url: <homepage_of_author>
 ```
 {: file="_data/authors.yml" }
 And then use `author` to specify a single entry or `authors` to specify multiple entries:
 ```yaml
 ---
 author: <author_id>                     # for single entry
 # or
 authors: [<author1_id>, <author2_id>]   # for multiple entries
 ---
 ```
 Having said that, the key `author` can also identify multiple entries.
 > The benefit of reading the author information from the file `_data/authors.yml`{: .filepath } is that the page will have the meta tag `twitter:creator`, which enriches the [Twitter Cards](https://developer.twitter.com/en/docs/twitter-for-websites/cards/guides/getting-started#card-and-content-attribution) and is good for SEO.
 {: .prompt-info }
 ### Post Description
 By default, the first words of the post are used to display on the home page for a list of posts, in the _Further Reading_ section, and in the XML of the RSS feed. If you don't want to display the auto-generated description for the post, you can customize it using the `description` field in the _Front Matter_ as follows:
 ```yaml
 ---
 description: Short summary of the post.
 ---
 ```
 Additionally, the `description` text will also be displayed under the post title on the post's page.
 ## Table of Contents
 By default, the **T**able **o**f **C**ontents (TOC) is displayed on the right panel of the post. If you want to turn it off globally, go to `_config.yml`{: .filepath} and set the value of variable `toc` to `false`. If you want to turn off TOC for a specific post, add the following to the post's [Front Matter](https://jekyllrb.com/docs/front-matter/):
 ```yaml
 ---
 toc: false
 ---
 ```
 ## Comments
 The global switch of comments is defined by variable `comments.active` in the file `_config.yml`{: .filepath}. After selecting a comment system for this variable, comments will be turned on for all posts.
 If you want to close the comment for a specific post, add the following to the **Front Matter** of the post:
 ```yaml
 ---
 comments: false
 ---
 ```
 ## Media
 We refer to images, audio and video as media resources in _Chirpy_.
 ### URL Prefix
 From time to time we have to define duplicate URL prefixes for multiple resources in a post, which is a boring task that you can avoid by setting two parameters.
 - If you are using a CDN to host media files, you can specify the `cdn` in `_config.yml`{: .filepath }. The URLs of media resources for site avatar and posts are then prefixed with the CDN domain name.
  ```yaml
  cdn: https://cdn.com
  ```
  {: file='_config.yml' .nolineno }
 - To specify the resource path prefix for the current post/page range, set `media_subpath` in the _front matter_ of the post:
  ```yaml
  ---
  media_subpath: /path/to/media/
  ---
  ```
  {: .nolineno }
 The option `site.cdn` and `page.media_subpath` can be used individually or in combination to flexibly compose the final resource URL: `[site.cdn/][page.media_subpath/]file.ext`
 ### Images
 #### Caption
 Add italics to the next line of an image, then it will become the caption and appear at the bottom of the image:
 ```markdown
 ![img-description](/path/to/image)
 _Image Caption_
 ```
 {: .nolineno}
 #### Size
 To prevent the page content layout from shifting when the image is loaded, we should set the width and height for each image.
 ```markdown
 ![Desktop View](/assets/img/sample/mockup.png){: width="700" height="400" }
 ```
 {: .nolineno}
 > For an SVG, you have to at least specify its _width_, otherwise it won't be rendered.
 {: .prompt-info }
 Starting from _Chirpy v5.0.0_, `height` and `width` support abbreviations (`height` → `h`, `width` → `w`). The following example has the same effect as the above:
 ```markdown
 ![Desktop View](/assets/img/sample/mockup.png){: w="700" h="400" }
 ```
 {: .nolineno}
 #### Position
 By default, the image is centered, but you can specify the position by using one of the classes `normal`, `left`, and `right`.
 > Once the position is specified, the image caption should not be added.
 {: .prompt-warning }
 - **Normal position**
  Image will be left aligned in below sample:
  ```markdown
  ![Desktop View](/assets/img/sample/mockup.png){: .normal }
  ```
  {: .nolineno}
 - **Float to the left**
  ```markdown
  ![Desktop View](/assets/img/sample/mockup.png){: .left }
  ```
  {: .nolineno}
 - **Float to the right**
  ```markdown
  ![Desktop View](/assets/img/sample/mockup.png){: .right }
  ```
  {: .nolineno}
 #### Dark/Light mode
 You can make images follow theme preferences in dark/light mode. This requires you to prepare two images, one for dark mode and one for light mode, and then assign them a specific class (`dark` or `light`):
 ```markdown
 ![Light mode only](/path/to/light-mode.png){: .light }
 ![Dark mode only](/path/to/dark-mode.png){: .dark }
 ```
 #### Shadow
 The screenshots of the program window can be considered to show the shadow effect:
 ```markdown
 ![Desktop View](/assets/img/sample/mockup.png){: .shadow }
 ```
 {: .nolineno}
 #### Preview Image
 If you want to add an image at the top of the post, please provide an image with a resolution of `1200 x 630`. Please note that if the image aspect ratio does not meet `1.91 : 1`, the image will be scaled and cropped.
 Knowing these prerequisites, you can start setting the image's attribute:
 ```yaml
 ---
 image:
  path: /path/to/image
  alt: image alternative text
 ---
 ```
 Note that the [`media_subpath`](#url-prefix) can also be passed to the preview image, that is, when it has been set, the attribute `path` only needs the image file name.
 For simple use, you can also just use `image` to define the path.
 ```yml
 ---
 image: /path/to/image
 ---
 ```
 #### LQIP
 For preview images:
 ```yaml
 ---
 image:
  lqip: /path/to/lqip-file # or base64 URI
 ---
 ```
 > You can observe LQIP in the preview image of post \"[Text and Typography](../text-and-typography/)\".
 For normal images:
 ```markdown
 ![Image description](/path/to/image){: lqip="/path/to/lqip-file" }
 ```
 {: .nolineno }
 ### Video
 #### Social Media Platform
 You can embed videos from social media platforms with the following syntax:
 ```liquid
 {% include embed/{Platform}.html id='{ID}' %}
 ```
 Where `Platform` is the lowercase of the platform name, and `ID` is the video ID.
 The following table shows how to get the two parameters we need in a given video URL, and you can also know the currently supported video platforms.
 | Video URL                                                                                          | Platform   | ID             |
 | -------------------------------------------------------------------------------------------------- | ---------- | :------------- |
 | [https://www.**youtube**.com/watch?v=**H-B46URT4mg**](https://www.youtube.com/watch?v=H-B46URT4mg) | `youtube`  | `H-B46URT4mg`  |
 | [https://www.**twitch**.tv/videos/**1634779211**](https://www.twitch.tv/videos/1634779211)         | `twitch`   | `1634779211`   |
 | [https://www.**bilibili**.com/video/**BV1Q44y1B7Wf**](https://www.bilibili.com/video/BV1Q44y1B7Wf) | `bilibili` | `BV1Q44y1B7Wf` |
 #### Video Files
 If you want to embed a video file directly, use the following syntax:
 ```liquid
 {% include embed/video.html src='{URL}' %}
 ```
 Where `URL` is a URL to a video file e.g. `/path/to/sample/video.mp4`.
 You can also specify additional attributes for the embedded video file. Here is a full list of attributes allowed.
 - `poster='/path/to/poster.png'` — poster image for a video that is shown while video is downloading
 - `title='Text'` — title for a video that appears below the video and looks same as for images
 - `autoplay=true` — video automatically begins to play back as soon as it can
 - `loop=true` — automatically seek back to the start upon reaching the end of the video
 - `muted=true` — audio will be initially silenced
 - `types` — specify the extensions of additional video formats separated by `|`. Ensure these files exist in the same directory as your primary video file.
 Consider an example using all of the above:
 ```liquid
 {%
  include embed/video.html
  src='/path/to/video.mp4'
  types='ogg|mov'
  poster='poster.png'
  title='Demo video'
  autoplay=true
  loop=true
  muted=true
 %}
 ```
 ### Audios
 If you want to embed an audio file directly, use the following syntax:
 ```liquid
 {% include embed/audio.html src='{URL}' %}
 ```
 Where `URL` is a URL to an audio file e.g. `/path/to/audio.mp3`.
 You can also specify additional attributes for the embedded audio file. Here is a full list of attributes allowed.
 - `title='Text'` — title for an audio that appears below the audio and looks same as for images
 - `types` — specify the extensions of additional audio formats separated by `|`. Ensure these files exist in the same directory as your primary audio file.
 Consider an example using all of the above:
 ```liquid
 {%
  include embed/audio.html
  src='/path/to/audio.mp3'
  types='ogg|wav|aac'
  title='Demo audio'
 %}
 ```
 ## Pinned Posts
 You can pin one or more posts to the top of the home page, and the fixed posts are sorted in reverse order according to their release date. Enable by:
 ```yaml
 ---
 pin: true
 ---
 ```
 ## Prompts
 There are several types of prompts: `tip`, `info`, `warning`, and `danger`. They can be generated by adding the class `prompt-{type}` to the blockquote. For example, define a prompt of type `info` as follows:
 ```md
 > Example line for prompt.
 {: .prompt-info }
 ```
 {: .nolineno }
 ## Syntax
 ### Inline Code
 ```md
 `inline code part`
 ```
 {: .nolineno }
 ### Filepath Highlight
 ```md
 `/path/to/a/file.extend`{: .filepath}
 ```
 {: .nolineno }
 ### Code Block
 Markdown symbols ```` ``` ```` can easily create a code block as follows:
 ````md
 ```
 This is a plaintext code snippet.
 ```
 ````
 #### Specifying Language
 Using ```` ```{language} ```` you will get a code block with syntax highlight:
 ````markdown
 ```yaml
 key: value
 ```
 ````
 > The Jekyll tag `{% highlight %}` is not compatible with this theme.
 {: .prompt-danger }
 #### Line Number
 By default, all languages except `plaintext`, `console`, and `terminal` will display line numbers. When you want to hide the line number of a code block, add the class `nolineno` to it:
 ````markdown
 ```shell
 echo 'No more line numbers!'
 ```
 {: .nolineno }
 ````
 #### Specifying the Filename
 You may have noticed that the code language will be displayed at the top of the code block. If you want to replace it with the file name, you can add the attribute `file` to achieve this:
 ````markdown
 ```shell
 # content
 ```
 {: file="path/to/file" }
 ````
 #### Liquid Codes
 If you want to display the **Liquid** snippet, surround the liquid code with `{% raw %}` and `{% endraw %}`:
 ````markdown
 {% raw %}
 ```liquid
 {% if product.title contains 'Pack' %}
  This product's title contains the word Pack.
 {% endif %}
 ```
 {% endraw %}
 ````
 Or adding `render_with_liquid: false` (Requires Jekyll 4.0 or higher) to the post's YAML block.
 ## Mathematics
 We use [**MathJax**][mathjax] to generate mathematics. For website performance reasons, the mathematical feature won't be loaded by default. But it can be enabled by:
 [mathjax]: https://www.mathjax.org/
 ```yaml
 ---
 math: true
 ---
 ```
 After enabling the mathematical feature, you can add math equations with the following syntax:
 - **Block math** should be added with `$$ math $$` with **mandatory** blank lines before and after `$$`
  - **Inserting equation numbering** should be added with `$$\begin{equation} math \end{equation}$$`
  - **Referencing equation numbering** should be done with `\label{eq:label_name}` in the equation block and `\eqref{eq:label_name}` inline with text (see example below)
 - **Inline math** (in lines) should be added with `$$ math $$` without any blank line before or after `$$`
 - **Inline math** (in lists) should be added with `\$$ math $$`
 ```markdown
 <!-- Block math, keep all blank lines -->
 $$
 LaTeX_math_expression
 $$
 <!-- Equation numbering, keep all blank lines  -->
 $$
 \begin{equation}
  LaTeX_math_expression
  \label{eq:label_name}
 \end{equation}
 $$
 Can be referenced as \eqref{eq:label_name}.
 <!-- Inline math in lines, NO blank lines -->
 "Lorem ipsum dolor sit amet, $$ LaTeX_math_expression $$ consectetur adipiscing elit."
 <!-- Inline math in lists, escape the first `$` -->
 1. \$$ LaTeX_math_expression $$
 2. \$$ LaTeX_math_expression $$
 3. \$$ LaTeX_math_expression $$
 ```
 > Starting with `v7.0.0`, configuration options for **MathJax** have been moved to file `assets/js/data/mathjax.js`{: .filepath }, and you can change the options as needed, such as adding [extensions][mathjax-exts].  
 > If you are building the site via `chirpy-starter`, copy that file from the gem installation directory (check with command `bundle info --path jekyll-theme-chirpy`) to the same directory in your repository.
 {: .prompt-tip }
 [mathjax-exts]: https://docs.mathjax.org/en/latest/input/tex/extensions/index.html
 ## Mermaid
 [**Mermaid**](https://github.com/mermaid-js/mermaid) is a great diagram generation tool. To enable it on your post, add the following to the YAML block:
 ```yaml
 ---
 mermaid: true
 ---
 ```
 Then you can use it like other markdown languages: surround the graph code with ```` ```mermaid ```` and ```` ``` ````.
 ## Learn More
 For more knowledge about Jekyll posts, visit the [Jekyll Docs: Posts](https://jekyllrb.com/docs/posts/).
--- a/_posts/2019-08-09-getting-started.md
+++ b/_posts/2019-08-09-getting-started.md
@ -1,151 +0,0 @@
 ---
 title: Getting Started
 description: >-
  Get started with Chirpy basics in this comprehensive overview.
  You will learn how to install, configure, and use your first Chirpy-based website, as well as deploy it to a web server.
 author: cotes
 date: 2019-08-09 20:55:00 +0800
 categories: [Blogging, Tutorial]
 tags: [getting started]
 pin: true
 media_subpath: '/posts/20180809'
 ---
 ## Creating a Site Repository
 When creating your site repository, you have two options depending on your needs:
 ### Option 1. Using the Starter (Recommended)
 This approach simplifies upgrades, isolates unnecessary files, and is perfect for users who want to focus on writing with minimal configuration.
 1. Sign in to GitHub and navigate to the [**starter**][starter].
 2. Click the <kbd>Use this template</kbd> button and then select <kbd>Create a new repository</kbd>.
 3. Name the new repository `<username>.github.io`, replacing `username` with your lowercase GitHub username.
 ### Option 2. Forking the Theme
 This approach is convenient for modifying features or UI design, but presents challenges during upgrades. So don't try this unless you are familiar with Jekyll and plan to heavily modify this theme.
 1. Sign in to GitHub.
 2. [Fork the theme repository](https://github.com/cotes2020/jekyll-theme-chirpy/fork).
 3. Name the new repository `<username>.github.io`, replacing `username` with your lowercase GitHub username.
 ## Setting up the Environment
 Once your repository is created, it's time to set up your development environment. There are two primary methods:
 ### Using Dev Containers (Recommended for Windows)
 Dev Containers offer an isolated environment using Docker, which prevents conflicts with your system and ensures all dependencies are managed within the container.
 **Steps**:
 1. Install Docker:
   - On Windows/macOS, install [Docker Desktop][docker-desktop].
   - On Linux, install [Docker Engine][docker-engine].
 2. Install [VS Code][vscode] and the [Dev Containers extension][dev-containers].
 3. Clone your repository:
   - For Docker Desktop: Start VS Code and [clone your repo in a container volume][dc-clone-in-vol].
   - For Docker Engine: Clone your repo locally, then [open it in a container][dc-open-in-container] via VS Code.
 4. Wait for the Dev Containers setup to complete.
 ### Setting up Natively (Recommended for Unix-like OS)
 For Unix-like systems, you can set up the environment natively for optimal performance, though you can also use Dev Containers as an alternative.
 **Steps**:
 1. Follow the [Jekyll installation guide](https://jekyllrb.com/docs/installation/) to install Jekyll and ensure [Git](https://git-scm.com/) is installed.
 2. Clone your repository to your local machine.
 3. If you forked the theme, install [Node.js][nodejs] and run `bash tools/init.sh` in the root directory to initialize the repository.
 4. Run command `bundle` in the root of your repository to install the dependencies.
 ## Usage
 ### Start the Jekyll Server
 To run the site locally, use the following command:
 ```terminal
 $ bundle exec jekyll s
 ```
 > If you are using Dev Containers, you must run that command in the **VS Code** Terminal.
 {: .prompt-info }
 After a few seconds, the local server will be available at <http://127.0.0.1:4000>.
 ### Configuration
 Update the variables in `_config.yml`{: .filepath} as needed. Some typical options include:
 - `url`
 - `avatar`
 - `timezone`
 - `lang`
 ### Social Contact Options
 Social contact options are displayed at the bottom of the sidebar. You can enable or disable specific contacts in the `_data/contact.yml`{: .filepath} file.
 ### Customizing the Stylesheet
 To customize the stylesheet, copy the theme's `assets/css/jekyll-theme-chirpy.scss`{: .filepath} file to the same path in your Jekyll site, and add your custom styles at the end of the file.
 Starting with version `6.2.0`, if you want to overwrite the SASS variables defined in `_sass/addon/variables.scss`{: .filepath}, copy the main SASS file `_sass/main.scss`{: .filepath} to the `_sass`{: .filepath} directory in your site's source, then create a new file `_sass/variables-hook.scss`{: .filepath} and assign your new values there.
 ### Customizing Static Assets
 Static assets configuration was introduced in version `5.1.0`. The CDN of the static assets is defined in `_data/origin/cors.yml`{: .filepath }. You can replace some of them based on the network conditions in the region where your website is published.
 If you prefer to self-host the static assets, refer to the [_chirpy-static-assets_](https://github.com/cotes2020/chirpy-static-assets#readme) repository.
 ## Deployment
 Before deploying, check the `_config.yml`{: .filepath} file and ensure the `url` is configured correctly. If you prefer a [**project site**](https://help.github.com/en/github/working-with-github-pages/about-github-pages#types-of-github-pages-sites) and don't use a custom domain, or if you want to visit your website with a base URL on a web server other than **GitHub Pages**, remember to set the `baseurl` to your project name, starting with a slash, e.g., `/project-name`.
 Now you can choose _ONE_ of the following methods to deploy your Jekyll site.
 ### Deploy Using Github Actions
 Prepare the following:
 - If you're on the GitHub Free plan, keep your site repository public.
 - If you have committed `Gemfile.lock`{: .filepath} to the repository, and your local machine is not running Linux, update the platform list of the lock file:
  ```console
  $ bundle lock --add-platform x86_64-linux
  ```
 Next, configure the _Pages_ service:
 1. Go to your repository on GitHub. Select the _Settings_ tab, then click _Pages_ in the left navigation bar. In the **Source** section (under _Build and deployment_), select [**GitHub Actions**][pages-workflow-src] from the dropdown menu.  
   ![Build source](pages-source-light.png){: .light .border .normal w='375' h='140' }
   ![Build source](pages-source-dark.png){: .dark .normal w='375' h='140' }
 2. Push any commits to GitHub to trigger the _Actions_ workflow. In the _Actions_ tab of your repository, you should see the workflow _Build and Deploy_ running. Once the build is complete and successful, the site will be deployed automatically.
 You can now visit the URL provided by GitHub to access your site.
 ### Manual Build and Deployment
 For self-hosted servers, you will need to build the site on your local machine and then upload the site files to the server.
 Navigate to the root of the source project, and build your site with the following command:
 ```console
 $ JEKYLL_ENV=production bundle exec jekyll b
 ```
 Unless you specified the output path, the generated site files will be placed in the `_site`{: .filepath} folder of the project's root directory. Upload these files to your target server.
 [nodejs]: https://nodejs.org/
 [starter]: https://github.com/cotes2020/chirpy-starter
 [pages-workflow-src]: https://docs.github.com/en/pages/getting-started-with-github-pages/configuring-a-publishing-source-for-your-github-pages-site#publishing-with-a-custom-github-actions-workflow
 [docker-desktop]: https://www.docker.com/products/docker-desktop/
 [docker-engine]: https://docs.docker.com/engine/install/
 [vscode]: https://code.visualstudio.com/
 [dev-containers]: https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers
 [dc-clone-in-vol]: https://code.visualstudio.com/docs/devcontainers/containers#_quick-start-open-a-git-repository-or-github-pr-in-an-isolated-container-volume
 [dc-open-in-container]: https://code.visualstudio.com/docs/devcontainers/containers#_quick-start-open-an-existing-folder-in-a-container
--- a/_posts/2019-08-11-customize-the-favicon.md
+++ b/_posts/2019-08-11-customize-the-favicon.md
@ -1,37 +0,0 @@
 ---
 title: Customize the Favicon
 author: cotes
 date: 2019-08-11 00:34:00 +0800
 categories: [Blogging, Tutorial]
 tags: [favicon]
 ---
 The [favicons](https://www.favicon-generator.org/about/) of [**Chirpy**](https://github.com/cotes2020/jekyll-theme-chirpy/) are placed in the directory `assets/img/favicons/`{: .filepath}. You may want to replace them with your own. The following sections will guide you to create and replace the default favicons.
 ## Generate the favicon
 Prepare a square image (PNG, JPG, or SVG) with a size of 512x512 or more, and then go to the online tool [**Real Favicon Generator**](https://realfavicongenerator.net/) and click the button <kbd>Select your Favicon image</kbd> to upload your image file.
 In the next step, the webpage will show all usage scenarios. You can keep the default options, scroll to the bottom of the page, and click the button <kbd>Generate your Favicons and HTML code</kbd> to generate the favicon.
 ## Download & Replace
 Download the generated package, unzip and delete the following two from the extracted files:
 - `browserconfig.xml`{: .filepath}
 - `site.webmanifest`{: .filepath}
 And then copy the remaining image files (`.PNG`{: .filepath} and `.ICO`{: .filepath}) to cover the original files in the directory `assets/img/favicons/`{: .filepath} of your Jekyll site. If your Jekyll site doesn't have this directory yet, just create one.
 The following table will help you understand the changes to the favicon files:
 | File(s)             | From Online Tool                  | From Chirpy |
 |---------------------|:---------------------------------:|:-----------:|
 | `*.PNG`             | ✓                                 | ✗           |
 | `*.ICO`             | ✓                                 | ✗           |
 <!-- markdownlint-disable-next-line -->
 >  ✓ means keep, ✗ means delete.
 {: .prompt-info }
 The next time you build the site, the favicon will be replaced with a customized edition.