Posted onEdited onInTutorialViews: Symbols count in article: 2.7kReading time ≈2 mins.
A short note on the Markdown syntax used in this blog.
Translation note: This English version was translated by Codex (GPT-5) on 2026-04-20 18:01:46 CST. The source text is the corresponding Chinese post in this repository.
Summary: This is a note-style article about basic Markdown syntax.
# Level-1 Heading Step 1: You need a GitHub account and a new repository. To change the theme, modify the `theme` field in the root YAML config. To change the NexT sub-scheme, modify the `scheme` field. Use `hexo new post "xxxx"` to create a new post.
---
## Level-2 Heading: Text Styles Pitfall: - GitHub does not distinguish folder names by case in the same way as the local environment. If you only change capitalization locally, `pull` may not reflect it correctly. You may need to rename it and then rename it back.
# Level-1 Heading Step 1: You need a GitHub account and a new repository. To change the theme, modify the `theme` field in the root YAML config. To change the NexT sub-scheme, modify the `scheme` field. Use `hexo new post "xxxx"` to create a new post.
---
## Level-2 Heading: Text Styles Pitfall: - GitHub folders are case-insensitive in some workflows. If the local capitalization changes, `pull` may not recognize it correctly. You may need to rename the folder and then rename it back.