community
community copied to clipboard
Contribute to KubeSphere Blogs
As we mentioned last week, we expect every one of the community to contribute an English blog to us. These blogs will be published on the official website and some other media channels. You can write them based on your skilled part.
We suggest you to start with a couple of pain points regarding the current technical state, then elaborate on the solutions or capabilities provided by KubeSphere. Why
and How to
should be included in your blog.
BTW, we are pretty flexible about the type of content, length and style. A contributed blog doesn’t have to be 5,000 words of heavy teaching. It can be around 1000 words outlining a KubeSphere-related technical story, an introduction or a tutorial. Code snippets are fine.
The content should be writing in markdown, and the images should be stored in QingStor object storage, just paste the image URL into the content. This is an example blog you can reference the content framework.
You can draft a topic or your thought in this issue firstly, thus we can avoid the duplicated content. Others can also evaluate your topic or give you some inspiration. You can submit a PR to this repository when you finish the blog. We hope you can finish it before Apr, 13.
- [ ] @zryfish
- [ ] @zheng1
- [ ] @leoendless
- [ ] @benjaminhuo
- [ ] @pixiake
- [ ] @huanggze
- [ ] @pengcong06
- [ ] @hlwanghl
- [ ] @wnxn
- [ ] @liuyp2018
- [ ] @mayuhope
- [ ] @shaowenchen
- [ ] @wansir
- [ ] @Forest-L
- [ ] @justahole
- [ ] @min-zh
- [ ] @wanjunlei
- [ ] @junotx
- [ ] @FeynmanZhou
- [ ] @yunkunrao
- [ ] @runzexia (Optional)
- [ ] @rayzhou2017 (Optional)
- [ ] @calvinyv (Optional)
I will write a blog regarding the architecture of 4.0 after 3.0 released.
Considering this issue is outdated I guess we can close it. Right? @FeynmanZhou