Guidance to Post a Blog


  1. Refer to to register Gitee account.

  2. Set your primary mail box in gitee settings

  3. Sign your CLA in

  4. Prepare your git environment refering to

Understand blog format

The openEuler blog is written in markdown format. You can read to get understand how the blog is designed.

The head includes the following information:

title: Sample Post
date: '2020-03-03'
category: blog
    - Sample
    - ABC
    - cccc
sig: sig-xxx
archives: '2020-03'
  - openEuler Blog Maintainer
summary: Just about everything you'll need to style in the theme:headings, paragraphs, blockquotes, tables, code blocks, and more.

Here you can edit your blog.

Tips: you can copy to your folder and edit it.

Post your blog

The blog posting follows the pull request of Gitee.

  1. Fork openEuler blog project to your own gitee. Refer to for detailed guidance.

  2. Clone the code to your local environment.

git clone<your-gitee-id>/openEuler-portal
  1. Create a branch
git checkout -b <branch-name>
  1. Create a folder in the website floder If you are going to post a blog in English, the app/en/blog is your work path.

And if you are going to post a blog in Chinese, the app/zh/blog is your work path.

Assume that you are preparing an English blog.

cd app/en/blog
mkdir <your-gitee-id>
cd <your-gitee-id>

And You can put the resources in the same folder as your text file's, and name the resources as


Where the YEAR, MONTH, DAY, and title are the same as your blog file, and NN is the serial number of the pictures, like 01, 02 and so on. The MARKUP is the file extension, and for pictures it is recommended to use png. The following are one example.
  1. Commit your post
git add <file-path>
git commit -m "<message>"
git push origin <branch-name>:<branch-name>
  1. Refer to to submit your Pull Request

  2. Wait for reviewing and merging.

[Disclaimer] This article only represents the author's opinions, and is irrelevant to this website. This website is neutral in terms of the statements and opinions in this article, and does not provide any express or implied warranty of accuracy, reliability, or completeness of the contents contained therein. This article is for readers' reference only, and all legal responsibilities arising therefrom are borne by the reader himself.