New landing page Issues

[juzhiyuan]

Hi, @1502shivam-singh's all PRs have been merged just now, this issue is to track UI issues :)

Welcome to leave your questions here.

[juzhiyuan]

In the Events part, some links are broken. cc @guoqqqi

[juzhiyuan]

1. This Video is muted, I couldn't play it with audio;
2. How about using YouTube's playlist here? so visitors could watch and play more videos. For Chinese, we could change the Playlist to Apache APISIX's Bilibili.

cc @1502shivam-singh @moonming

[juzhiyuan]

Hi @liuxiran, I remember that you removed the Logos from Home page, may I know the action context?

[juzhiyuan]

This is a historical issue, due to the ASF's policy, new users couldn't join #apisix's Slack via fixed invitation link, see apache/apisix#4932 (comment)

We need to update website's description.

[1502shivam-singh]

1. This Video is muted, I couldn't play it with audio;

It wasn't an Yt embed so I just left it on mute, will unmute it 👍

2. How about using YouTube's playlist here? so visitors could watch and play more videos. For Chinese, we could change the Playlist to Apache APISIX's Bilibili.

I guess a nice option.

[juzhiyuan]

ya, I would suggest using a Playlist here :)

[1502shivam-singh]

In the Events part, some links are broken. cc @guoqqqi

Oh okay, surprisingly there is no events tab any more ? Where do we link the events to, blog pages ?
EDIT: We have blog posts tagged as events in blogs, maybe add them to events.json ?

[juzhiyuan]

EDIT: We have blog posts tagged as events in blogs, maybe add them to events.json ?

Ya, maybe @Serendipity96 could explain why we remove the Events page and using the events tag 🤔

[liuxiran]

Hi @liuxiran, I remember that you removed the Logos from Home page, may I know the action context?

yep @juzhiyuan , asf has a requirement that the home page of the Apache project website cannot list "powered by" companies, but we can list them on a separate page, so we move all our showcase to the https://apisix.apache.org/showcase

[juzhiyuan]

All right, need @1502shivam-singh help to update this case 😆

[Serendipity96]

EDIT: We have blog posts tagged as events in blogs, maybe add them to events.json ?

Ya, maybe @Serendipity96 could explain why we remove the Events page and using the events tag 🤔

hi @juzhiyuan @1502shivam-singh, some release notes under the Events tab, but these are duplicates of those under the Release tab. Since release notes under the Release tab are implemented with auto-generation, the release notes under the Events tab seems to be redundant. Thus, remove the release notes under Events tab maybe a good choice. After removing the redundant release notes from the Events tab, there are only a few event-related documents under the Events tab, which is not sufficient enough to support a tab. So @yzeng25 migrated the article to the blog and added the events tag.

[juzhiyuan]

get

[1502shivam-singh]

hi @juzhiyuan @1502shivam-singh, some release notes under the Events tab, but these are duplicates of those under the Release tab. Since release notes under the Release tab are implemented with auto-generation, the release notes under the Events tab seems to be redundant. Thus, remove the release notes under Events tab maybe a good choice. After removing the redundant release notes from the Events tab, there are only a few event-related documents under the Events tab, which is not sufficient enough to support a tab. So @yzeng25 migrated the article to the blog and added the events tag.

Understood. Though, I think maybe not all events are transferred to the blog section, as then replacing events with blog in the url should have linked to a specific event, isn't it ? But instead they lead to a 404 page. Maybe need to recheck on this, i guess.

[juzhiyuan]

Yes, and I'm checking and will fix this.

[Xunzhuo]

One more thing, in mobile, two buttons (dark mode and search) are too closed.

[SkyeYoung]

Is this still a problem?

[1502shivam-singh]

Is this still a problem?

Not exactly I suppose, This was put up to act as a single point to post issues related specifically to the redesigned site, just after deployment was done last year. Now that no more greater issues seem to prevail so it would be safe to close this I think.

@juzhiyuan, do you think we can close this now ?

[juzhiyuan]

Sure. 😉