diff --git a/README.md b/README.md
index d6802c3..74a36a1 100644
--- a/README.md
+++ b/README.md
@@ -19,7 +19,7 @@
**[Live Demo →](https://chirpy.cotes.info)**
- [](https://chirpy.cotes.info)
+ [](https://chirpy.cotes.info)
@@ -159,7 +159,7 @@ Now publish your Jekyll site by:
2. Browse to your repository on GitHub. Select the tab _Settings_, then click _Pages_ in the left navigation bar, and then in the section **Source** of _GitHub Pages_, select the `/(root)` directory of branch `gh-pages` as the [publishing source][pages-src]. Remember to click Save before leaving.
- 
+ 
3. Visit your website at the address indicated by GitHub.
diff --git a/_config.yml b/_config.yml
index 94e1a32..dfabf6e 100644
--- a/_config.yml
+++ b/_config.yml
@@ -79,10 +79,10 @@ theme_mode: # [light|dark]
# will be added to all image (site avatar & posts' images) paths starting with '/'
#
# e.g. 'https://cdn.com'
-img_cdn: ''
+img_cdn: 'https://cdn.jsdelivr.net/gh/cotes2020/chirpy-images@0a003683c0c3ca549d12c309f9b3e03ea20981e5'
# the avatar on sidebar, support local or CORS resources
-avatar: https://cdn.jsdelivr.net/gh/cotes2020/chirpy-images/commons/avatar.jpg
+avatar: '/commons/avatar.jpg'
# boolean type, the global switch for ToC in posts.
toc: true
diff --git a/_posts/2019-08-08-text-and-typography.md b/_posts/2019-08-08-text-and-typography.md
index 0f2d226..65756a3 100644
--- a/_posts/2019-08-08-text-and-typography.md
+++ b/_posts/2019-08-08-text-and-typography.md
@@ -7,7 +7,7 @@ tags: [typography]
math: true
mermaid: true
image:
- src: https://cdn.jsdelivr.net/gh/cotes2020/chirpy-images/commons/devices-mockup.png
+ src: /commons/devices-mockup.png
width: 850
height: 585
---
@@ -99,34 +99,34 @@ Click the hook will locate the footnote[^footnote], and here is another footnote
- Default (with caption)
-{: width="972" height="589" }
+{: width="972" height="589" }
_Full screen width and center alignment_
- Shadow
-{: .shadow width="1548" height="864" style="max-width: 90%" }
+{: .shadow width="1548" height="864" style="max-width: 90%" }
_shadow effect (visible in light mode)_
- Left aligned
-{: width="972" height="589" style="max-width: 70%" .normal}
+{: width="972" height="589" style="max-width: 70%" .normal}
- Float to left
- {: width="972" height="589" style="max-width: 200px" .left}
+ {: width="972" height="589" style="max-width: 200px" .left}
"A repetitive and meaningless text is used to fill the space. A repetitive and meaningless text is used to fill the space. A repetitive and meaningless text is used to fill the space. A repetitive and meaningless text is used to fill the space. A repetitive and meaningless text is used to fill the space. A repetitive and meaningless text is used to fill the space. A repetitive and meaningless text is used to fill the space. A repetitive and meaningless text is used to fill the space. A repetitive and meaningless text is used to fill the space. A repetitive and meaningless text is used to fill the space. A repetitive and meaningless text is used to fill the space. A repetitive and meaningless text is used to fill the space."
- Float to right
- {: width="972" height="589" style="max-width: 200px" .right}
+ {: width="972" height="589" style="max-width: 200px" .right}
"A repetitive and meaningless text is used to fill the space. A repetitive and meaningless text is used to fill the space. A repetitive and meaningless text is used to fill the space. A repetitive and meaningless text is used to fill the space. A repetitive and meaningless text is used to fill the space. A repetitive and meaningless text is used to fill the space. A repetitive and meaningless text is used to fill the space. A repetitive and meaningless text is used to fill the space. A repetitive and meaningless text is used to fill the space. A repetitive and meaningless text is used to fill the space. A repetitive and meaningless text is used to fill the space. A repetitive and meaningless text is used to fill the space."
diff --git a/_posts/2019-08-09-getting-started.md b/_posts/2019-08-09-getting-started.md
index 639d0bf..742f1d9 100644
--- a/_posts/2019-08-09-getting-started.md
+++ b/_posts/2019-08-09-getting-started.md
@@ -124,7 +124,7 @@ Now publish your Jekyll site by:
2. Browse to your repository on GitHub. Select the tab _Settings_, then click _Pages_ in the left navigation bar, and then in the section **Source** of _GitHub Pages_, select the `/(root)` directory of branch `gh-pages` as the [publishing source][pages-src]. Remember to click Save before leaving.
- {: width="850" height="153" }
+ {: width="850" height="153" }
3. Visit your website at the address indicated by GitHub.
diff --git a/_posts/2021-01-03-enable-google-pv.md b/_posts/2021-01-03-enable-google-pv.md
index 765bdff..240b1da 100644
--- a/_posts/2021-01-03-enable-google-pv.md
+++ b/_posts/2021-01-03-enable-google-pv.md
@@ -33,7 +33,7 @@ With your property created, you now need to set up Data Stream to track your blo
It should look like this:
-{: width="1086" height="542"}
+{: width="1086" height="542"}
Now, click on the new data stream and grab the **Measurement ID**. It should look something like `G-V6XXXXXXXX`. Copy this to your `_config.yml` file
@@ -49,7 +49,7 @@ google_analytics:
When you push these changes to your blog, you should start seeing the traffic on your Google Analytics. Play around with Google Analytics dashboard to get familiar with the options available as it takes like 5 mins to pickup your changes. You should now be able to monitor your traffic in realtime.
-{: width="616" height="557"}
+{: width="616" height="557"}
## Setup Page Views
@@ -185,7 +185,7 @@ There is a detailed [tutorial](https://developers.google.com/analytics/solutions
If everything went good, you'll get this screen:
-{: width="1366" height="354"}
+{: width="1366" height="354"}
### Create Google Analytics Query
@@ -210,14 +210,14 @@ After Run Query, copy the generated contents of **API Query URI** at
After the query is saved on GAE, a **Public Endpoint** (public access address) will be generated, and we will get the query result in JSON format when accessing it. Finally, click Enable Endpoint in **Public Request Endpoint** to make the query effective, and click Start Scheduling in **Scheduling** to start the scheduled task.
-{: width="1100" height="126"}
+{: width="1100" height="126"}
## Configure Chirpy to Display Page View
Once all the hard part is done, it is very easy to enable the Page View on Chirpy theme. Your superProxy dashboard should look something like below and you can grab the required values.
-{: width="1210" height="694"}
+{: width="1210" height="694"}
Update the `_config.yml` file of [**Chirpy**][chirpy-homepage] project with the values from your dashboard, to look similar to the following:
diff --git a/docs/README.zh-CN.md b/docs/README.zh-CN.md
index ae5cb3a..5d986bc 100644
--- a/docs/README.zh-CN.md
+++ b/docs/README.zh-CN.md
@@ -19,7 +19,7 @@
**[线上体验 →](https://chirpy.cotes.info)**
- [](https://chirpy.cotes.info)
+ [](https://chirpy.cotes.info)
@@ -158,7 +158,7 @@ $ docker run -it --rm \
2. 回到 GitHub 上的仓库，选择标签 _Settings_ → 点击左侧导航栏的 _Pages_ → _GitHub Pages_ 选择分支 `gh-pages` 的 `/(root)` 作为「[发布源][pages-src]」:
- 
+ 
3. 按照 GitHub 指示的地址去访问您的网站。
diff --git a/tools/init.sh b/tools/init.sh
index f10d8b4..ab90a61 100755
--- a/tools/init.sh
+++ b/tools/init.sh
@@ -52,13 +52,14 @@ init_files() {
if $_no_gh; then
rm -rf .github
else
- # change the files of `.github`
+ ## Change the files of `.github`
+
mv .github/workflows/$ACTIONS_WORKFLOW.hook .
rm -rf .github
mkdir -p .github/workflows
mv ./${ACTIONS_WORKFLOW}.hook .github/workflows/${ACTIONS_WORKFLOW}
- # ensure the gh-actions trigger branch
+ ## Ensure the gh-actions trigger branch
_workflow=".github/workflows/${ACTIONS_WORKFLOW}"
_default_branch="$(git symbolic-ref refs/remotes/origin/HEAD | sed 's@^refs/remotes/origin/@@')"
@@ -67,6 +68,10 @@ init_files() {
sed -i.$TEMP_SUFFIX "$((_lineno + 1))s/- .*/- ${_default_branch}/" "$_workflow"
rm -f "$_workflow.$TEMP_SUFFIX"
+ ## Cleanup image settings in site config
+ sed -i.$TEMP_SUFFIX "s/^img_cdn:.*/img_cdn: ''/;s/^avatar:.*/avatar: ''/" _config.yml
+ rm -f _config.yml.$TEMP_SUFFIX
+
fi
# trace the gem lockfile on user-end