-
+
- Markdown Syntax +
- Heading 1 + + +
- HTML Syntax +
- Heading 1 + + +
How to post posts
@@ -92,7 +125,7 @@How to post posts
First, let’s talk about the basic requirements for a valid post file:
+Welcome to the 2nd-Minima Jekyll theme! This guide will walk you through creating and managing your posts effectively. Whether you’re a beginner or an experienced Jekyll user, these instructions will help you make the most out of this theme.
-
@@ -100,13 +133,13 @@
How to post posts
-
-
Naming: You need to name your post file with the naming format of “Year-Month-Date-Title.md”, for example: “2022-11-28-My-first-post.md”. (Attention: The file naming does not allow any “space” character, so please make sure to use “-“ to replace them.)
+Naming: Posts should be named following the “Year-Month-Date-Title.md” format, for example: “2022-11-28-My-first-post.md”. (Attention: Spaces (
-) to separate words) -
-
Location: You need to place your post file under the “/_posts/” folder.
+Location: Place your post files in the “/_posts/” directory
-
-
tag-page: (You could temporarily skip this part until you have gotten up to the tags part under Internal requirements below) Please remember, if you add tags to a post, let’s assume one of the tags name is “the-tag-you-add”, then you should create a “the-tag-you-add.md” file under the “/tag/” folder in order to generate a tag-page for the “the-tag-you-add” and with just these contents in that “the-tag-you-add.md”:
+tag-page: (This section can be deferred until you’ve read about tags in the Internal Requirements.) Please remember, if you add tags to a post, let’s assume one of the tags name is “the-tag-you-add”, then you should create a “the-tag-you-add.md” file under the “/tag/” folder in order to generate a tag-page for the “the-tag-you-add” tag and the “the-tag-you-add.md” file should contain the following:
---- layout: tagpage @@ -115,7 +148,9 @@How to post posts
---And that tag-page would collect and display all your posts with that tag. In fact, there is a more efficient way to repeat this repetitive procedure, which is to create a python script to help you do that, for more detailed information please click on the solutions link below.
+(Attention: Ensure the title is enclosed in double quotes (
+ +") if it contains a colon (:) for successful tag page creation.)The tag page will aggregate and display all posts with the specified tag. Considering a more efficient implementation, which is to create a python script to automate this process, more details can be found in the solutions link right below.
The tags and tag-page display solutions are here provided by Long Qian, great thanks to him!
@@ -128,13 +163,15 @@ -
Predeclaration:
-Every “post.md” file you posted need to have a Predeclaration in the form of this at the file’s head (beginning) part (including this file: You can see the Predeclaration part at the beginning):
+Each “post.md” file you posted must have a Predeclaration block in the form of this at the file’s head (beginning) part (including this file: You can see the Predeclaration part at the beginning):
@@ -142,22 +179,38 @@--- layout: post title: How to post posts tags: this-is-a-tag WoW let's go +toc: true description: You could write a brief description here to catch your readers' interests, like this is a post about how to post posts :) +thumbnail: https://deep0thinking.com/wp-content/uploads/2024/01/my-first-post.jpg ---How to post posts
-
-
layout: post
+layout: Apply the “???” layout from “_layouts/???.html” to the post.
-Please just write 1 word “post”. This means your post that you want to post would use the post layout of “_layouts/page.html” file.
+Please just write 1 word “post” here for every post file. This means to apply the post layout from “_layouts/post.html” on your post.
-
-
title: Please write your post title here.
+title: The title of your post.
In fact, the file name in the Naming part of the External requirements can be different from the title name here, but it is always a good habit to keep them the same to disambiguate and improve convenience (just like writing the annotation when coding), especially when you want to read or modify these posts files in the future. But if you find a more efficient and effective naming method, you could definitely follow your way.
-
-
tags: Please write your post tag(s) here.
+tags: List the tags associated with your post, separated by spaces (
--) to avoid breaking multi-word tags.If you want to put 2 or more tags here, you need to use “space” to separate them, and what can you do if you don’t want the tag to be separated, you could use “-“ to replace the “space” to combine the words and prevent the breakage in 1 tag. For example:
+this-is-a-tagis 1 tag,WoWis 1 tag,let's gois 2 tags, they actually break into 2 tags oflet'sandgodue to the “space” between them.If you want to put 2 or more tags here, you need to use “space” (
-to replace the “space” to combine the words and prevent the breakage in 1 tag. For example:this-is-a-tagis 1 tag,WoWis 1 tag, butlet's gois 2 tags, since it actually breaks into the 2 tagslet'sandgodue to the “space” between them. -
-
description: You could write a brief description in the description part to catch your readers’ interests (Attention: Please don’t leave “space” between “:” and following the word or punctuation in the description part, or your post and description will not be able to display.) , like this is a post about how to post posts (Me: It sounds super attractive right? Me again: Hahahahaha, no.) . Or, if you don’t like the description part, you could always turn it off in the “/_config.yml” file by replacing the
+trueinshow_description: truewithfalseor just simply delete that whole line.toc: Set to
+ +trueto include a Table of Contents,falseotherwise.The table of contents is a block contains a list of links to the different sections in your post. It is generated automatically based on the headings in your post. If you want to turn it off, just replace the
+ +trueintoc: truewithfalseor just simply delete that whole line.When
+ +true, the toc appears on the left side of your post. It automatically generates clickable links to different sections based on Markdown headings (e.g.,# Heading,## Subheading). Clicking on these links allows readers to quickly navigate to specific sections of your post. (Attention: While HTML headings like<h1>Heading</h1>will be included in the toc, they are not interactive and cannot be clicked to navigate to the respective sections. This feature is exclusively available for Markdown headings.)Conversely, setting
+toctofalseor removing the line entirely disables the toc. This means no interactive list of sections will appear on the left of your post, and there will be no clickable links for navigation within the post.
+ -
+
thumbnail: Put your post thumbnail link (URL or local path) here.
+ +The thumbnail link is the link of the image you want to display on the post page, it can be an URL like this:
+https://deep0thinking.com/wp-content/uploads/2024/01/my-first-post.jpgor a local file path like this:/assets/img/my-first-post.jpg. (Attention: Please make sure to use the correct link format, or the thumbnail would not be able to display.)
+ -
+
description: A short description to engage readers. Avoid spaces after colons in
+ +???insidedescription: ???likedescription: Hi, : );description: Hi, :)is permitted.You could write a brief description in the description part to catch your readers’ interests (Attention: Please don’t leave “space” (
:and following the word or punctuation in the description part, or your post and description will not be able to display.) , like this is a post about how to post posts (Me: It sounds super attractive right? Me again: Hahahahaha, no.) . If you don’t want the description part in all posts (the post layout), you could disable it permanently in the “/_config.yml” file by replacing thetrueinshow_description: truewithfalseor just simply delete that whole line.
@@ -183,7 +236,7 @@ -
-
How to post posts
How to post posts
-
-
Don’t worry, you don’t need to master these 4 languages to write a post, in fact, using only the Markdown language is basically enough (look at this post file name, its suffix is “.md” and md represents the Markdown language), because Markdown language can support the basic post arrangements and it is super easy and convenient to learn and use. BTW I bet you could master its basic syntax within 5 minutes, then you could be able to write the following Mardown contents too:
+Don’t worry, mastery of these languages is not required to write a post… In fact, using only the Markdown language is sufficient for most posts (look at this post file name, its suffix is “.md” and md represents the Markdown language), because Markdown language can support the basic post arrangements and it is super easy and convenient to learn and use. BTW I bet you could master its basic syntax within 5 minutes, then you could be able to write the following Markdown contents too:
@@ -193,7 +246,11 @@How to post posts
-
Markdown Syntax
+ +# Heading 1
## Heading 2
@@ -267,9 +324,9 @@ Heading 6
Here is a table:
|title 1|title 2|title 3|
-|:-|:-:|-:|
-|left|middle|right|
-|text|text|text|
+|:- | :-: | -:|
+|left |middle |right |
+|text |text |text |
Here is a table:
@@ -384,20 +441,24 @@ Heading 6
-<h1> Heading </h1>
-<h2> Heading </h2>
-<h3> Heading </h3>
-<h4> Heading </h4>
-<h5> Heading </h5>
-<h6> Heading </h6>
+HTML Syntax
+
+
+
+<h1> Heading 1 </h1>
+<h2> Heading 2 </h2>
+<h3> Heading 3 </h3>
+<h4> Heading 4 </h4>
+<h5> Heading 5 </h5>
+<h6> Heading 6 </h6>
- Heading
- Heading
- Heading
- Heading
- Heading
- Heading
+ Heading 1
+ Heading 2
+ Heading 3
+ Heading 4
+ Heading 5
+ Heading 6
@@ -601,7 +662,7 @@ Heading
-Maybe you have already noticed the fake comments section below, wanna put it somewhere else or delete it? Click it for more information ~
+Maybe you have already noticed the fake comments section below, wanna activate it? Click it for more information ~
@@ -611,11 +672,11 @@ Heading
fake comments section
-
-
+ -
+
My first post
+ + [ + + +WoW go +
+ +
+ Haha! This is my first post. +
+ + ++ +
###
+ ++ +
fake comments section
+ +0.1 About the 2nd-Minima repository
-This Github repository is designed for the people who want to build a personal website handily (based on [Jekyll-theme-Minima](https://github.com/jekyll/minima)) but are not familiar with front-end programming languages. +The **2nd-Minima** Github repository is designed for individuals seeking to handily create a blog. It's a user-friendly, advanced **template** based on the popular [Jekyll-theme-Minima](https://github.com/jekyll/minima), perfect for those unfamiliar with front-end programming. -To be more specific, it is an advanced modified-version **template** of personal websites based on [Jekyll-theme-Minima](https://github.com/jekyll/minima). +Experience a live demo of a [2nd-Minima](https://github.com/Deep0Thinking/2nd-Minima) based website here: [Deep0Thinking.github.io](https://deep0thinking.github.io) -And here is a [**2nd-Minima**](https://github.com/Deep0Thinking/2nd-Minima) based website sample: [Deep0Thinking.github.io](https://deep0thinking.github.io) - - +0.2 About the "/README.md"
-This "[**/README.md**](https://github.com/Deep0Thinking/2nd-Minima/blob/master/README.md)" file is considered to be a manual or handbook for the [**2nd-Minima**](https://github.com/Deep0Thinking/2nd-Minima) repository. I would try to explain everything as I can to help you to understand it and modify it according to your preference. +This "[**/README.md**](https://github.com/Deep0Thinking/2nd-Minima/blob/master/README.md)" file serves as a comprehensive manual for the [**2nd-Minima**](https://github.com/Deep0Thinking/2nd-Minima) repository. It aims to provide clear explanations and guidance for customization and use. If you're new to this repository, I recommend reading this "**/README.md**" file in its entirety. It will help you get started quickly and easily.0.3 About the usage
-Briefly, you could do almost any modification based on this template as you want according to the [MIT License](https://github.com/Deep0Thinking/2nd-Minima/blob/main/LICENSE) in both [**2nd-Minima**](https://github.com/Deep0Thinking/2nd-Minima) and [Jekyll-theme-Minima](https://github.com/jekyll/minima). +With the [MIT License](https://github.com/Deep0Thinking/2nd-Minima/blob/main/LICENSE), you have extensive freedom to modify and adapt the [**2nd-Minima**](https://github.com/Deep0Thinking/2nd-Minima) template to suit your personal needs. You may also use it for commercial purposes.0.4 About the acknowledgement
@@ -64,9 +62,9 @@ And specifically, great thanks to [Long Qian](http://longqian.me/aboutme/), [Mat Thanks should also go to Github, because this platform provide many people (including me) a chance to learn, cooperate and improve in coding. -Finally, special thanks to my family and friends, without their support in every aspect, I would never accomplish this. +Lastly, heartfelt appreciation to my family and friends for their unwavering support. -Oh, and a big thank to you too, I really appreciate that you trust me and use it :) +Oh, and a big thank you to you, the user, for trusting and using this template :) --- @@ -74,17 +72,19 @@ Oh, and a big thank to you too, I really appreciate that you trust me and use it1.1 Use this template
-Please enter the [**2nd-Minima**](https://github.com/Deep0Thinking/2nd-Minima) repository page first and click on `Use this template` (the green button) -> `Create a new repository` , then please enter the "Repository name", if this is your first time creating a repository, I recommend you to type in the form of "Your-Github-name.github.io" like "Louis.github.io", for more detailed explanation please check here: https://pages.github.com . But if you want to use other repository names like "Cookie-0111", it's totally acceptable and will not cause any difference or problem on the future use. +Please direct to the [**2nd-Minima**](https://github.com/Deep0Thinking/2nd-Minima) repository (repo) page first and click on `Use this template` (the green button) -> `Create a new repository` , then please enter the "Repository name", if you're a first-timer, I suggest using the format "your-Github-username.github.io", like "louis.github.io". This naming convention is important for GitHub Pages, and you can learn more about it at https://pages.github.com. However, feel free to choose a different name, such as "Cookie-0111", if you prefer. This won't impact the future functionality of your site. + +As for the other repo settings, you can stick with the default options or adjust them according to your preferences. Keep in mind, even if you initially set your repository to private, others can still access your personal website once it's deployed and they have the link. (Note: even if you initially set your repository to `private`, others can still access your personal website once it's deployed and they have the link) -And for other setting selections you could just leave them as default, or you could make your own choices based on your preference. (BTW, others could still access to your personal website as long as you've deployed this repository's webpage and they also got its link address, even though you choose `private` when creating the repository at first) +1.2 Webpage pre-set-up and deployment
-1.2 Webpage deployment
+Please direct to the page of the repo which you've just created using the [**2nd-Minima**](https://github.com/Deep0Thinking/2nd-Minima) template, click on `< > Code` (the green button right under the "Fork" button) -> `HTTPS` -> "Copy url to clipboard", and then open your terminal (or command line) and type in `git clone ` and paste the url you've just copied from the repo page, then press `Enter` to clone the repo to your local computer. (Note: you need to have "git" installed on your computer first, if you don't have git installed, please check here: https://git-scm.com/downloads) -Please enter the page of the repository which you've just created using the [**2nd-Minima**](https://github.com/Deep0Thinking/2nd-Minima) template, then please click on `Settings` (above the green button) -> `Pages` (on the left column list) -> `None` -> `master` -> `Save`. And after about 1 minute, your personal website will be generated successfully, BTW you can always check its deployment state through access your repository Github main page to see whether that little yellow point (next to the green button `< > Code`) has turned into the ✅ (and please keep refreshing the page) . +Once the cloning process is complete, please direct to the folder of the repo you've just cloned, and open the "**/.github/workflows/jekyll.yml**" file, then please replace the `/2nd-Minima` in `jekyll_baseurl: '/2nd-Minima'` with your repo name: If your repo is named "Cookie-0111", then set it to `jekyll_baseurl: '/Cookie-0111'`; If your repo name is in the form of "your-Github-username.github.io" like "louis.github.io", set it to `jekyll_baseurl: ''`. Don't forget to save the changes. (Note: the repo name is case-sensitive, so please type in the repo name exactly as it is) -And you can visit your site at `Settings` -> `Pages` -> `Visit site` , and don't forget to remember your website address :) +Return to the page of the repo you created, then navigate to `Settings` (located just beneath the search bar) -> `Pages` (on the left column list) -> `Deploy from a branch` -> `Github Actions`. And after about 2 minute, your personal website will be generated successfully. To monitor its deployment state, revisit your repository's main page, keep an eye on the small yellow dot (next to the green button `< > Code`). Upon successful deployment, this dot will change to a green check mark ✅ (Remember to refresh the page to update the status indicator). (Note: if you see a red cross ❌ instead of the check mark ✅, please check the "**/.github/workflows/jekyll.yml**" file and make sure you've replaced the `/2nd-Minima` in `jekyll_baseurl: '/2nd-Minima'` as previously instructed) -In fact, you could save the address on your browser, or put that address into your repository's `About` block which is next to the green button `< > Code` on your repository Github main page by clicking the option button (the gear icon) in that `About` block, or create a clickable link combines with the heading in your "**/README.md**" file under the repository, like `# [please-paste-your-webpage-link-here](https://please-paste-your-webpage-link-here)` , and next time you can conveniently click on that heading on your repository Github main page to access your webpage since Github has set the "**README.md**" file of every repository to display automatically on their corresponding repository's Github main page. +To visit your site, navigate to `Settings` -> `Pages` -> `Visit site` , it's a good idea to bookmark your site's url for easy access. Alternatively, you can add your site's url into your repo's `About` section, which is located next to the green button `< > Code` on your repo Github main page. Click on the option button (the gear icon) in that `About` block to add your link. You can also create a direct link combines with the heading style in your "**/README.md**" file under the repo root folder, like `# [please-paste-your-webpage-link-here](https://please-paste-your-webpage-link-here)`. This creates a clickable heading on your repository's main page, as GitHub automatically displays the "README.md" file there for every repo. --- @@ -92,42 +92,40 @@ In fact, you could save the address on your browser, or put that address into yo2.1 "/_config.yml"
-First, please open the "**/_config.yml**" and replace the `Please-type-your-Github-name-here` with your Github name in the title part. +Start by opening the "**/_config.yml**" file. In the title section, replace `Please-type-your-Github-name-here` with your actual Github username. -Next, for line with `the show_description` , I recommend you to leave its value with `true` , and don't worry, we will help you to figure that out later. +Moving on to the line labeled `show_description`, I recommend setting its value to `true`. Don't worry about the details for now; we'll guide you through this part later. -And for the `header_pages` , this part controls the display order of the pages on the navigation bar of `archive` , `about` and `all-tags` pages, you can change their sequence to affect their real display sequence on the webpage: the order of top to bottom in the `header_pages` corresponds to order of left to right on the webpage navigation bar. +Lastly, let's focus on `header_pages`. This section determines the order of pages like `archive`, `about`, and `all-tags` on your website's navigation bar. To rearrange their display order on the webpage, simply change their sequence in `header_pages`. The order from top to bottom in this section directly corresponds to the left-to-right order on your website's navigation bar.2.2 Posts
-Want to write a post including texts, a picture, a youtube video, links to other website, Maths equations (latex), a downloadable document link, others comments, interactive animations, and etc? +Are you ready to craft a captivating post featuring a mix of elements like text, images, YouTube videos, external links, LaTeX-formatted math equations, downloadable documents, interactive animations, and more? -Now please go to check the [How-to-post-posts](https://deep0thinking.github.io/2nd-Minima/2022/11/28/How-to-post-posts.html) post :), it is under the "**/_posts/**" folder. +If so, your next step is simple. Dive into our comprehensive guide post titled [How-to-post-posts](https://deep0thinking.github.io/2nd-Minima/2022/11/28/How-to-post-posts.html). You'll find this valuable resource in the "**/_posts/**" folder. This guide is your key to effortlessly integrating these diverse content types into your posts. Let's get started!2.3 giscus.app
-I think you've noticed the **fake comments section** on the bottom part of the post of "**How to post posts**", this is actually the area that you would need to establish your **real comments section**. - -In fact, the real comments section is supported by [giscus.app](https://giscus.app). Please check that out, the [giscus.app](https://giscus.app) page have already written detailed information and instructions to enable the comments section (giscus). +You might have noticed the **fake comments section** at the bottom of the "**How to post posts**" post and "**Archive**" page and "**About**" page. This is where you'll set up your **real comments section**. -When you finish reading the [giscus.app](https://giscus.app) instructions and have copied the embed code for the comments section (giscus), you can now paste it and replace the **fake comments section** code (which is located at bottom of the file: `fake comments section
` ) in your "**/_layouts/post.html**" file. And you also need to apply the same process to the your "**/about.md**" and "**/archive.md**" file, yeah I also put the **fake comments section** there respectively. +The actual comments functionality is powered by [giscus.app](https://giscus.app), a robust platform for enabling comments on your site. To get started, visit [giscus.app](https://giscus.app) and follow the detailed instructions provided there to enable the giscus comment section. -Maybe you would wonder why can't I just put the giscus embed code in the "**/_layouts/page.html**" (since the [**about**](https://deep0thinking.github.io/2nd-Minima/about.html) and [**archive**](https://deep0thinking.github.io/2nd-Minima/archive.html) pages all have `layout: page` in the Predeclaration part) ? +Once you've read through the giscus instructions and obtained the necessary embed code, it's time to integrate it into your site. Replace the **fake comments section** code at the bottom of your "**/_layouts/post.html**" file with the new giscus embed code. The placeholder code you'll be replacing looks like this: `fake comments section
`. Remember to repeat this step for your "**/about.md**" and "**/archive.md**" files, as they also contain placeholders for the **fake comments section**. -In fact, it is valid for you to do that, but I don't recommend this action because it would also cause the and [**all-tags**](https://deep0thinking.github.io/2nd-Minima/all-tags.html) and every single **tag** page to have the comments section at the bottom and that is not necessary and would somehow decrease the webpage aesthetics from my perspective. +You might wonder why not simply insert the giscus embed code into the "**/_layouts/page.html**" file, as both the [**about**](https://deep0thinking.github.io/2nd-Minima/about.html) and [**archive**](https://deep0thinking.github.io/2nd-Minima/archive.html) pages use `layout: page` in their predeclarations. The reason is that doing so would also add a comments section to the [**all-tags**](https://deep0thinking.github.io/2nd-Minima/all-tags.html) page and every single **tag** page, which isn't ideal. In my view, this could clutter these pages and detract from the site's aesthetic appeal. But you can surely do that based on you preference. -After completing the procedure above, you can now see the comments sections (giscus) appear at the bottom part in the corresponding pages. +After you've completed these steps, the giscus comments sections should now be visible at the bottom of the relevant pages.2.4 "/about.md"
-The instruction of modifying [**about**](https://deep0thinking.github.io/2nd-Minima/about.html) page are provided inside the "**/about.md**" file, so you can now visit your "**/about.md**" file and do some personalized modification. +You'll find detailed guidance on customizing the [**about**](https://deep0thinking.github.io/2nd-Minima/about.html) page within the "**/about.md**" file itself. So, take a moment to visit your "**/about.md**" file, where you can apply your own personal touches and modifications to make it truly yours.2.5 "/archive.md"
-The instruction of modifying [**archive**](https://deep0thinking.github.io/2nd-Minima/archive.html) page are provided inside the "**/archive.md**" file, so you can now visit your "**/archive.md**" file and do some personalized modification. +Tailoring the [**archive**](https://deep0thinking.github.io/2nd-Minima/archive.html) page to your preferences is straightforward. You'll find all the necessary instructions within the "**/archive.md** file. Go ahead and open your "**/archive.md** file to start making personalized modifications that reflect your style and needs.2.6 favicon
-Favicon is the icon that represents your webpage (did you notice the black icon located next to your webpage title? Yeah, that is the favicon I set as default for this repository, and I'll tell you how to change it) and you can design your own favicon for your webpage, here I recommend [favicon.io](https://favicon.io), it is a website that allows you to design and generate your favicon freely and conveniently. +The favicon is a small, iconic image that represents your webpage. Have you noticed the black icon next to your webpage title? That's the default favicon I've set for this repository. But you can personalize it by creating your own. For this, I recommend using [favicon.io](https://favicon.io). It's a user-friendly website that lets you design and generate your own favicon for free. -After you've done creating your favicon, all you need to do is to place the generated "**favicon.ico**" file under the "**/favicon/**" folder to **replace** the old one (the old "**favicon.ico**" file) I've put there before ***(Attention: The file name of the favicon file you put under the "/favicon/" folder must be "favicon.ico" exactly, or it won't work)***, then your webpage would be able to show the favicon you designed. +Once you've crafted your favicon, the next step is simple. Just place your newly created "**favicon.ico**" file into the "**/favicon/**" folder, replacing the existing one (the old "**favicon.ico**" file I placed there). ***(Attention: the new file you replaced with under the "/favicon/" must be named exactly "favicon.ico" for it to function correctly )*** With this change, your webpage will display the favicon you've designed, adding a unique touch to your site. \ No newline at end of file diff --git a/_site/about.html b/_site/about.html index 6a2f8b4..d0e2290 100644 --- a/_site/about.html +++ b/_site/about.html @@ -1,5 +1,5 @@ - + @@ -27,19 +27,7 @@ - - -About
@@ -77,9 +65,11 @@Welcome to the “About” page of your site! This is where you can introduce yourself or your project. Below, you’ll find a template structure along with instructions to personalize your page. If you need help, feel free to contact me through email: Deep0Thinking@outlook.com
+Instruction part 1 begins
-To find your github avatar HTML source code, you need to first view the source code of your Github profile page (please go google “how to view the source code of a webpage”, and it is very easy to apply), then you need to use the built-in pointer tool of your browser to locate and click on your Github avatar area, then you will be lead to a HTML source code section in a form like :
+To find your github avatar HTML source code, you need to first view the source code of your Github profile page (please google “how to view the source code of a webpage”, trust me, it is very easy to apply), then you should use the built-in pointer tool of your browser to locate and click on your Github avatar area, this will lead you to the HTML source code section in the form like:
<img style="height:auto;" alt="" width="260" height="260" class="avatar avatar-user width-full border color-bg-default" src="https://avatars.githubusercontent.com/u/103571424?v=4">
Instruction part 1 begins
Instruction part 1 ends
Try to write something here:
-Try to write something here
+Here, you can talk about yourself, your interests, or the purpose of your site.
Maybe your hobbies:
-…
+Share your hobbies or things you’re passionate about.
Maybe your Contact Information:
@@ -112,9 +102,9 @@Maybe your Information On Oth
Instruction part 2 begins
-
If you want to add more platforms information, you can go to remixicon.com to find icons you want and copy the corresponding embed code, for exam: <i class="ri-github-line"></i> . Then paste it and edit in the form of the above, and it’ll work properly.
If you want to add more platforms information, you can visit remixicon.com to choose the desired icons and copy the corresponding embed code, for example: <i class="ri-github-line"></i> . Then insert it in the form of the above.
Finally, after getting familiar with these procedure, you can delete this instruction part (from <h3 style="color: red">Instruction part 2 begins</h3> to <h3 style="color: red">Instruction part 2 ends</h3>) safely.
After you’re comfortable with the setup, you can remove these instructions safely (from <h3 style="color: red">Instruction part 2 begins</h3> to <h3 style="color: red">Instruction part 2 ends</h3>).
+