Design comparison
Solution retrospective
Lots of lessons here. I really dont even know where to begin. SASS made this project much easier. Used custom properties, used nesting and even took advantage of BEM. Feeling like I took bog steps forward with everything.
Community feedback
- @correlucasPosted about 2 years ago
๐พHello @ColinMcArthur85, Congratulations on completing this challenge!
๐จโ๐ป Here are some tips to improve your solution code:
1.The easiest way to build this component and make sure that each column will have 50% of the container size is by using
GRID
. All you need to do is to usedisplay: grid
to activate the Grid and then make the two columns withgrid-template-column: 1fr 1fr
and its done, now youโve two columns. For theMOBILE VERSION
you can switch toflex
creating a media query usingdisplay: flex
andflex-direction: column-reverse
to make the image appear before the text content.2.To make the image have a better fit inside of it, make the component image responsive with
display: block
andmax-width: 100%
(this makes the image fit the column/div size) and respect the component size while it scales down. To make it crop while scaling useobject-fit: cover
.img { display: block; object-fit: cover; max-width: 100%; }
3.Instead of using a long code for the IMAGE OVERLAY. You can do it using a shortcut with a few lines of code
mix-blend-mode
, that in my opinion is a better way and makes the color tone really close to the challenge design. All you need is thediv
under theimage
with thisbackground-color: hsl(277, 64%, 61%);
and applymix-blend-mode: multiply
andopacity: 80%
on theimg
orpicture
selector to activate the overlay blending the image with the color of the div. See the code bellow:img { mix-blend-mode: multiply; opacity: 80%; }
โ๏ธ I hope this helps you and happy coding!
0 - @AdrianoEscarabotePosted about 2 years ago
Hi Colin McArthur, how are you?
I really liked the result of your project, but I have some tips that I think you will like:
1- Every page should have one main landmark
<main>
. So replace the div that wraps the whole content with<main>
to improve the accessibility. click here2- All page content should be contained by landmarks, you can understand better by clicking here: click here
We have to make sure that all content is contained in a reference region, designated with HTML5 reference elements or ARIA reference regions.
Example:
native HTML5 reference elements:
<body> <header>This is the header</header> <nav>This is the nav</nav> <main>This is the main</main> <footer>This is the footer</footer> </body>
ARIA best practices call for using native HTML5 reference elements instead of ARIA functions whenever possible, but the markup in the following example works:
<body> <div role="banner">This is the header</div> <div role="navigation">This is the nav</div> <div role="main">This is the main</div> <div role="contentinfo">This is the footer</div> </body>
It is a best practice to contain all content, except skip links, in distinct regions such as header, navigation, main, and footer.
Link to read more about: click here
2- Why it Matters
Navigating the web page is far simpler for screen reader users if all of the content splits between one or more high-level sections. Content outside of these sections is difficult to find, and its purpose may be unclear.
HTML has historically lacked some key semantic markers, such as the ability to designate sections of the page as the header, navigation, main content, and footer. Using both HTML5 elements and ARIA landmarks in the same element is considered a best practice, but the future will favor HTML regions as browser support increases.
Rule Description
It is a best practice to ensure that there is only one main landmark to navigate to the primary content of the page and that if the page contains iframe elements, each should either contain no landmarks, or just a single landmark.
Link to read more about: click here
The rest is great!!
Hope it helps...๐
0
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