Navigable Social Links: Mouse & Keyboard

Solution retrospective
I'm especially proud of stepping out of my comfort zone by integrating Tailwind CSS and GraphQL—both of which were new additions to my toolkit. I also feel good about implementing jQuery to enable seamless keyboard navigation alongside traditional mouse interactions. Moving forward, I'll continue using Tailwind CSS since its utility-first approach made styling more efficient and enjoyable. I also plan to further refine my GraphQL integration as I gain more experience with it.
What challenges did you encounter, and how did you overcome them?The main challenge I faced was dealing with FOUC (Flash of Unstyled Content). I attempted to tackle this by setting an invisible class on the body element and then revealing it via main.js
after the CSS loaded. Unfortunately, that method didn't fully resolve the issue. Although I haven't found the perfect solution yet, and I'm eager to explore better approaches in future projects.
I welcome feedback on every aspect of the project, especially insights into fixing the FOUC issue and best practices for ensuring styles load before the page renders.(I guess I solve that:) )
Please log in to post a comment
Log in with GitHubCommunity feedback
- @Steno-95
Simply looking at your code i can only say amazing! i am sorry that with my experience i can't really give you any kind of feedback 😅
Join our Discord community
Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!
Join our Discord