Yes, I have discussed with @hf200012 yesterday about this issue.
There are 3 ways we can do:
1. Move the entire `docs/` dir to the other code repo[1]
This can solve the problem of the main repo being too large. But the
trouble is that when we update other functional documents, we need to submit
PRs to the code repo on both sides, which is more cumbersome.
2. Try to limit the number and format of pictures
We tried to use `svg` format. But in some cases, the size of svg turned out
to be larger than the compressed `png` format.
3. Use external links
Use external links of images in blogs. So that the contributor need first
post its blog to some other blog website. And than refer to that.
But I am not sure it is ok to use external links in Apache project's
website.
So my suggestion is to use the compressed png format in the early stage, and
try to limit the size and number of pictures.
If this does become a problem, we can consider other options
[1] https://github.com/apache/incubator-doris-website
--
此致！Best Regards
陈明雨 Mingyu Chen
Email:
chenmin...@apache.org
At 2021-11-19 10:58:56, "ling miao" <lingm...@apache.org> wrote:
>First of all, I am looking forward to the blog feature very much.
>But when I was reviewing blog posts, I found that general blog posts will
>carry a lot of resources, such as pictures.
>In the future, we will definitely add a lot of blog posts. Will this lead
>to a larger and larger code base?
>If the answer is yes, is it a correct operation for us to put the resouces
>of these blog articles in the code base?
>Or how do other projects manage these blogs?
>
>Ling Miao
