Hi community, I have designed a plan for the blog issue raised above. Let me briefly describe my plan: I have divided apisix related material into two categories, one is blog and the other is video. Blogs and videos will be added tags, so that everyone can easily find the information according to his or her needs. Because there are some diagrams in the plan, I wrote the full content on github: https://github.com/apache/apisix-website/issues/607, please take a look. Looking forward to your feedback, thanks. Best Reagrds! @Serendipity96< https://github.com/Serendipity96>
Zhiyuan Ju <[email protected]> 于2021年10月5日周二 上午8:45写道： > Hi, > > Shivam Singh's PRs have been merged, and Apache APISIX's website gets > updated. Welcome to have a look and give some feedbacks, you could reply to > https://github.com/apache/apisix-website/issues/640 and we will resolve > them. > > see https://apisix.apache.org/ > > Best Regards! > @ Zhiyuan Ju <https://github.com/juzhiyuan> > > > Zhiyuan Ju <[email protected]> 于2021年9月27日周一 上午11:23写道： > > > Hi, Serendipity, > > > > I just found this site[1], it includes some tutorials from the community! > > Please take a look :) > > > > Also, we could learn more from https://docusaurus.io/showcase?tags=large > > > > [1] https://questdb.io/tutorial/ > > > > Best Regards! > > @ Zhiyuan Ju <https://github.com/juzhiyuan> > > > > > > Serendipity 96 <[email protected]> 于2021年9月24日周五 下午3:40写道： > > > >> hi, Yilin, Zhiyuan, > >> > >> I read all content in PR#625, it was a big and great job! Yilin, thanks > >> for your hard work. I am really grateful that my idea was supported so > >> quickly. > >> > >> Zhiyuan Ju <[email protected]> 于2021年9月23日周四 下午10:12写道： > >> > >> > I noticed that Yilin has submitted the PR to migrate Events :) > >> > > >> > https://github.com/apache/apisix-website/pull/625 > >> > > >> > Best Regards! > >> > @ Zhiyuan Ju <https://github.com/juzhiyuan> > >> > > >> > > >> > Yilin Zeng <[email protected]> 于2021年9月23日周四 下午4:26写道： > >> > > >> > > Hi Serendipity96, > >> > > > >> > > > a.i means 'Those that overlap with the contents of Release under > >> > > Resources'? > >> > > > >> > > > a.ii means 'Move Events content to Blog, and add Events tag in > >> Blog.'? > >> > > > >> > > Yes. > >> > > > >> > > Regards, > >> > > Yilin(https://github.com/yzeng25) > >> > > ________________________________ > >> > > From: [email protected] <[email protected]> > >> > > Sent: Thursday, September 23, 2021 1:19 AM > >> > > To: [email protected] <[email protected]> > >> > > Subject: Re: [DISCUSS] a new structure of Apache APISIX website > >> > > > >> > > Hi Yilin, > >> > > > >> > > I need to confirm two items: > >> > > > >> > > a.i means 'Those that overlap with the contents of Release under > >> > > Resources'? > >> > > > >> > > a.ii means 'Move Events content to Blog, and add Events tag in > Blog.'? > >> > > > >> > > I read all articles on the events page, some are blogs, some are > event > >> > > descriptions, and some are release blogs. In your plan, release > blogs > >> > will > >> > > be added the 'release' tag on the blog page, event descriptions will > >> be > >> > > added the 'events' tag on the blog page. > >> > > > >> > > If so, it will be clearer to migrate the articles of events to the > >> blog > >> > > page. Good job. > >> > > > >> > > Best Regards! > >> > > > >> > > Serendipity96(https://github.com/Serendipity96) > >> > > > >> > > Yilin Zeng <[email protected]> 于2021年9月22日周三 下午6:17写道： > >> > > > >> > > > Hi Serendipity96, > >> > > > > >> > > > Here is my initial plan of modifing the events and the blog pages: > >> > > > > >> > > > > >> > > > 1. Events-related transformation > >> > > > * Divide Events under Resources into 2 categories. > >> > > > * Those that overlap with the contents of Release under > >> > > Resources > >> > > > * Events content > >> > > > * Delete a.i > >> > > > * Move a.ii to Blog, and add Events tag in Blog. > >> > > > 2. Blog-related modifications > >> > > > * refine tags > >> > > > * only one tag for each article, if an article matches more > >> than > >> > > > one tag, choose the tag that best fits. > >> > > > 3. Modify homepage's link to events tag inside the blog. > >> > > > > >> > > > What do you think? > >> > > > > >> > > > Regards, > >> > > > Yilin(https://github.com/yzeng25) > >> > > > [https://avatars.githubusercontent.com/u/36651058?v=4?s=400]< > >> > > > https://github.com/yzeng25> > >> > > > yzeng25 (yilinzeng) · GitHub<https://github.com/yzeng25> > >> > > > Add a bio. yzeng25 has 28 repositories available. Follow their > code > >> on > >> > > > GitHub. > >> > > > github.com > >> > > > > >> > > > ________________________________ > >> > > > From: [email protected] <[email protected]> > >> > > > Sent: Saturday, September 18, 2021 2:21 AM > >> > > > To: [email protected] <[email protected]> > >> > > > Subject: Re: [DISCUSS] a new structure of Apache APISIX website > >> > > > > >> > > > Hi Yilin, > >> > > > > >> > > > I'm glad to have a new proposal so soon, thanks for your > attention. > >> > > > > >> > > > > >> > > > I agree with expanding the tags under the blog. Redefining tags > will > >> > help > >> > > > others who want to learn Apache APISIX. > >> > > > > >> > > > > >> > > > As you suggested, the events page will be a blank page. The events > >> will > >> > > be > >> > > > removed directly from the navigation. Maybe it is a good way. At > the > >> > same > >> > > > time, it is a big change and I'm not sure if we should do that. > >> > > > > >> > > > Best Regards! > >> > > > > >> > > > Serendipity96(https://github.com/Serendipity96) > >> > > > > >> > > > > >> > > > > >> > > > Yilin Zeng <[email protected]> 于2021年9月17日周五 下午12:03写道： > >> > > > > >> > > > > Hi Serendipity96, > >> > > > > > >> > > > > I can help on this part. > >> > > > > > * Events: Events module does not have a dedicated tab on > the > >> > nav. > >> > > > > There > >> > > > > > are only 4 infomation introductions are displayed on the > >> homepage, > >> > > > which > >> > > > > is > >> > > > > > hard to be noticed. The content on the events page is not > >> > > categorized. > >> > > > > > > >> > > > > > * Blog: Blog show too much little information, and the > >> style is > >> > > > > simple. > >> > > > > > >> > > > > Here are a couple of problems on the Events part: > >> > > > > > >> > > > > > >> > > > > 1. Release notes under Events tab are redundant. For the > >> release > >> > > > notes > >> > > > > under Events tab, these are duplicates of those under Release > tab. > >> > > Since > >> > > > > release notes under Release tab are implemented with > >> auto-generation, > >> > > the > >> > > > > release notes under Events tab seems to be redundant. Thus, I > >> > recommend > >> > > > > remove the release notes under Events tab. > >> > > > > > >> > > > > 1. After removing the redundant release notes from Events > tab, > >> > there > >> > > > > are only a few event-related documents under Events tab, which > is > >> not > >> > > > > sufficient enough to support a tab. > >> > > > > 2. > >> > > > > > >> > > > > Here are some problems on the Blog part: > >> > > > > > >> > > > > > >> > > > > 1. Using tags to catergorize the blogs is good, but it can be > >> > better > >> > > > if > >> > > > > tags were more specifiied. > >> > > > > 2. The current tags are in lower case, but there is a 'All' > >> tag, > >> > > > > started with capitalized letter, they are not unfied. > >> > > > > > >> > > > > I came up with a proposal to solve the problems above: > >> > > > > > >> > > > > > >> > > > > 1. Remove redundant release notes under Events tab, keep > >> release > >> > > notes > >> > > > > under Release tab. > >> > > > > 2. Move event-related documents under Events tab to Blog tab, > >> add > >> > a > >> > > > new > >> > > > > tag 'Events' in Blog tab, and tag these event-related document > >> with > >> > > > > 'Events' tag. > >> > > > > 3. Update tags in Blog tab > >> > > > > * Specifiy tags: such as 'Events', 'Weekly Report', and > >> 'News' > >> > > > > * First letter capitalized: such as: 'Practical Case', > >> 'News', > >> > > and > >> > > > > 'Security'. > >> > > > > 4. Change the link to Events tab on home page, to link to > >> > 'Events' > >> > > > tag > >> > > > > on Blog tab. > >> > > > > 5. Add new tags 'User Case', 'Interview' under 'Blog' tab to > be > >> > more > >> > > > > specifiied. > >> > > > > > >> > > > > What do you think? > >> > > > > > >> > > > > Regards, > >> > > > > Yilin > >> > > > > <https://github.com/yzeng25> > >> > > > > [https://avatars.githubusercontent.com/u/36651058?v=4?s=400]< > >> > > > > https://github.com/yzeng25> > >> > > > > yzeng25 - Overview<https://github.com/yzeng25> > >> > > > > Add a bio. yzeng25 has 28 repositories available. Follow their > >> code > >> > on > >> > > > > GitHub. > >> > > > > github.com > >> > > > > > >> > > > > > >> > > > > ________________________________ > >> > > > > From: [email protected] <[email protected]> > >> > > > > Sent: Thursday, September 16, 2021 1:30 AM > >> > > > > To: [email protected] <[email protected]> > >> > > > > Subject: [DISCUSS] a new structure of Apache APISIX website > >> > > > > > >> > > > > hi, community, > >> > > > > > >> > > > > > >> > > > > I found that Apache APISIX website is not very convenient, I > often > >> > > can't > >> > > > > find the content that I want. But after browsing many times, I > >> found > >> > > > Apache > >> > > > > APISIX website is very informative. > >> > > > > > >> > > > > > >> > > > > I've also followed Apache APISIX other media and found a lot of > >> > really > >> > > > > great content that isn't posted on the website. > >> > > > > > >> > > > > > >> > > > > I have listed some of the problems on the website： > >> > > > > > >> > > > > - Apache APISIX website modules are not clear, e.g. > >> > > > > > >> > > > > * Homepage: The introduction of Apache APISIX on the > homepage > >> is > >> > > not > >> > > > > complete. The full features are on the github readme ( > >> > > > > https://github.com/apache/apisix). > >> > > > > > >> > > > > * Events: Events module does not have a dedicated tab on the > >> nav. > >> > > > There > >> > > > > are only 4 infomation introductions are displayed on the > homepage, > >> > > which > >> > > > is > >> > > > > hard to be noticed. The content on the events page is not > >> > categorized. > >> > > > > > >> > > > > * Blog: Blog show too much little information, and the style > >> is > >> > > > simple. > >> > > > > > >> > > > > * Docs: The document structure is deep and hard to find. > >> > > > > > >> > > > > * Language: There are two languages on the website, but the > >> > English > >> > > > and > >> > > > > Chinese contents are mixed together. > >> > > > > > >> > > > > * There is no content under the existing modules, such as: > >> news > >> > > > > > >> > > > > - Lack of linking channels to contributors: > >> > > > > > >> > > > > * Except for good first issues ，for potential and new > >> > contributors > >> > > > > (like me), I don't know what can I contribute. > >> > > > > > >> > > > > * Contact information is hidden too deep, it is in the > second > >> > level > >> > > > > under the tab. Or I change to Apache APISIX Github to find > contact > >> > > > > information. > >> > > > > > >> > > > > - Apache APISIX has a lot of learning materials and information, > >> but > >> > > the > >> > > > > website is not the most comprehensive. > >> > > > > > >> > > > > > >> > > > > I think a useful contributor site is the first step to attract > >> > > > > contributors. What do you think？ > >> > > > > > >> > > > > > >> > > > > Based on the above problems, I came up with a solution to make > >> Apache > >> > > > > APISIX website better and easier to find learning materials, > and I > >> > hope > >> > > > > more and more people will participate in contributing to Apache > >> > > APISIX. I > >> > > > > have drawn a prototype of the website, please take a look: > >> > > > > https://github.com/apache/apisix-website/issues/607. > >> > > > > > >> > > > > > >> > > > > Best Regards! > >> > > > > > >> > > > > Serendipity96(https://github.com/Serendipity96) > >> > > > > > >> > > > > >> > > > >> > > >> > > >
