Build With ACSS: Zendesk.com Home Page Part 4 (Header Menus)
Вставка
- Опубліковано 29 вер 2024
- In Part 4, Kevin tackles the top navigation and main navigation in the header.
Interested in using Automatic.css on your sites and accessing the private ACSS support and strategy community? Get a license here: automaticcss.com
Interested in using Frames on your sites and accessing the private Frames support and strategy community? Get a license here: getframes.io
Want more helpful dev tutorials and agency-related trainings? Check out Kevin's channel: / @gearyco
This bulding live videos are much better then talking about other sites and picking mistakes. Keep it going
Everything offers something different. If you don’t know what makes a website successful, knowing how to build one is useless.
This series is great! I've learned a lot again. It's also nice to see that you're not a machine, but have to think sometimes.
Next time, please create a darker website. Then I can watch it in the evening while my girlfriend is trying to sleep. Our TV is a bit too big and too bright. But I explained the importance of the videos to her and she understood. (Just kidding, but with a bit of truth)
Question: I revisited your video after a few days, and I'm trying to recall the section where you discussed using conditions to display or hide elements using data attributes on mobile devices. If I want to make certain content disappear on the Mobile version and implement a sticky mobile menu at the bottom, could you please guide me on achieving this? Or could specify the video where this topic is covered and provide the corresponding timestamp.
Not sure of where I've done that specifically with data attributes :/
Once again - TY SO MUCH Kevin for this! While I could achieve this in a half "chump" way myself - there are just so many tiny nuggets here and there which level up my game. Truly appreciated! Cheers mate! Osu! 🤙
Like you mentioned in the video that DOM elements are not proper made available in nav menus by pagebuilders like Bricks.
Can you target all the DOM elements of a nav menu that is build with Frames?
Another brilliant tutorial - helped me solve a problem with the crazy Bricks menu structure just this morning.
PURE GOLD . please make some E-commerce website . it will be amazing.
Another really informative video! thank you.
Zendesk site designer at start of first video "Hey everyone, Kevin Geary picked my site design to do a demo build - come see!"
Zendesk site designer about now: "Really wish I'd never told anyone..."
It’s pretty good, just not sure what they are doing with these stock photos lol
Awesome, can't wait for the mobile version!
Loved this video - so many nuggets
Some golden nugggets (as usual), thank you Kevin 😃
Hey Kevin, thank you so much for this series and your incredible work. For me this series is an absolute masterpiece. ❤
The Zendesk UI/UX designer listening to the layout issues for the menu 😰
Another example of a great learning experience..
I learn so much on building menus with this video! Thx Kevin.
I got mentally stuck on the nth-last-child(-n + 3) selector for the buttons. Since you did +3 it should have grabbed three items on the end, not just two. Two items would have been nth-last-child(-n + 2).
Obviously I missed something or it was a fluke that it worked.
Hmm, not sure without going back and watching again.
Thank you Kevin, much appreciated
seems a dumb question but why not use buttons on the header instead of doing a nth-last-child
Because semantically you want those options to be part of the navigation. They will also show up in the mobile menu automatically this way.
Thank you Kevin, I get so inspired and learn so much from your videos 😊
You are so welcome
Is there a rough timeframe for the nav builder being released for Frames?
Not yet.