Loopstudios challenge completed with responsiveness. No bootstrap.
Design comparison
Solution retrospective
Any feedback on grid systems or underlining links will be highly appreciated.
Community feedback
- @pikapikamartPosted about 3 years ago
Hey, awesome work on this one. You made a different layout on this one. Desktop seems fine, but the portion from the hero-section down to the next section is too large, too much empty white space. On mobile layout, it seems fine, but you could have made the desktop layout to be visible more, maybe adjusting the breakpoint to the mobile layout, that way you will make the layout more responsive and not just instantly show mobile layout.
Some suggestions would be:
- On the
header
the website logo link should not be included in thenav
, since it is not really a primary navigation link. Separate it from thenav
and include it in it's own container. - Website logo link should be using
a
tag, since you are treating it as an interactive element, hence adding thecursor: pointer
on it. Better usea
tag. - The
alt
of the website logo should only bealt="loopstudio"
, avoid adding words that relates to "graphic" like "logo, image, icon..." as a value inalt
attribute. Assistive tech will handle those for you. - The list of links in the navbar should be wrapped inside their own
a
tag since those are supposed links. - Personally, I would separate the hero-section from the
header
tag. I would include it in themain
element. - This text
IMMERSIVE EXPERIENCES THAT DELIVER
should be inside ah1
element. Also, if you have a text that needs to be uppercase, you don't put them directly uppercase in the html, because if you did that, screen reader will pronounce it letter by letter. Just put them in lowercase, then just usetext-transform: uppercase
in your css. - Always have a
main
element on a webpage.main
element helps users to properly navigate your website. On this one, themain
element should wrap all the sections starting from the hero-section, going down to the very bottom, but not including thefooter
. A usual structure would look like:
<header /> <main /> <footer />
- When using heading tags, do not skip a level. If you have an
h3
make sure you also have anh1, h2
. OUR CREATIONS
text should be a heading tag, also it should use thetext-transform
like what I said above.- The
see all
should be ana
tag, because it is supposed to be a link that directs users to view more creations. - Each card creation in the grid should be wrapped inside
a
tag, since in real site, it would be a link of creation cards. - The text inside each card could use heading tags.
FOOTER
- Website logo should be using
a
tag. - Website logo should use
alt="loopstudio"
. - The links below the website logo should be inside a
nav
element and each should be using their owna
tag. - The social media links should be inside a
ul
element and each should be insidea
tag , because those are list of links. - The
a
tag of each social media links should havearia-label
indicating a user where this link would take them. For example, thea
tag that would wrap the facebook should havearia-label="facebook".
- Lose the word
icon
on the social media images.
MOBILE
- Hamburger menu should be using
button
element and not justdiv
withimg
, since these are not accessible at all. - The hamburger
button
should havearia-label="hamburger menu dropdown toggler"
so that users will know what thisbutton
should do. - The hamburger
button
also should havearia-expanded
attribute on it. This would be changed by javascript, this will indicate to a user that a dropdown has expanded. You can search this one up on the internet to better understand it. This is really important. - Lastly, the hamburger toggler ordering in html is wrong. The
button
should appear first before the list of links from the navbar. Because if you use this current structure, if I used thebutton
with my keyboard, open it, then usetab
key, I would not be directed in the navigation links, because those links are way passed before I even got in thebutton
. Swap the ordering.
It may be a lot, but those mentioned are important. Still, you did a good job on this one.
Marked as helpful1@abdnadeem382Posted about 3 years ago@pikamart Thank you so much for such a detailed feedback. I will surely keep these things in mind for the next time. Really appreciate the help.
0 - On the
- @ConradMcGrifterPosted about 3 years ago
here is a codepen I made to show you how I did the underline hover effect for my project
Marked as helpful0
Please log in to post a comment
Log in with GitHubJoin 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