Hi Tyler, This is the right place to discuss it, or in JIRA. I saw there's a similar issue opened recently: KAFKA-10883 <https://issues.apache.org/jira/browse/KAFKA-10883>, just not in English. If you have anything updated or PR opened, please associate/update in the JIRA ticket. (And help update in English would be better)
As the issue you described, I don't have any preference since it didn't bother me that much :) I think opening the first subheading links should be the good enough. Let's see if there are other opinions. Thanks. Luke On Fri, Dec 25, 2020 at 9:51 AM Tyler Knappe <tyler.kna...@colorado.edu> wrote: > There doesn't appear to be an easy way to open an issue about the > kafka.apache.org site specifically, so I figured this would be a good > place > to start. Please point me in another place, if I should open an issue > elsewhere. > > The top navigation for the kafka.apache.org site is broken. The links for > 'Get Started' and 'Community' both do not navigate to a new page or open a > menu. If the screen size is shrunk, you instead get a hamburger menu that > does show navigation (both links don't work, still), but at least there is > some clue as to what navigation is possible. I'd be happy to open up a PR > to help fix this, but I'm not entirely certain what the default action > should be. > > It feels like 'Get Started' should open to https://kafka.apache.org/intro > but the 'Community's first subheading links to https://kafka-summit.org/, > which would be a very confusing experience, and perhaps > https://kafka.apache.org/project is a better default. > > If the intention was to pop a menu, to open a dropdown for the Get Started > and Community links, I haven't been able to find it in > https://github.com/apache/kafka-site/pull/269, but it is a 27k line > change. > :) I think this is the better option, but would incur a bit more work to > fix since this would require more design work and some JS to handle the > interaction. > > Regardless, please let me know what the intention was and I'd be happy to > open a PR to fix the issue. > > Thanks, > -Tyler >
