Responsive Fylo landing page with two column layout
Design comparison
Solution retrospective
This challenge was really fun, I had a 30 minute problem trying to position the bg curve above the second section...
At that moment I had no internet (Venezuela struggles lol) so I wasnยดt able to look up for a solution, I donยดt know if what I did was one of the methods to do so.
After all everything was comfortable to do hehe :-)
Also I forgot something that I am used to do with my sections (that is nesting a container in my sections with a fixed width in a percentage unit) so I had to use that padding, is it okay?
Also thanks to everyone for taking the time to read and see my solution, and to those who provide feedback! It is greatly apreciated
So if you have any advices on how I can improve my choices and the way I write my code, I would greatly appreciate it!
Thanks in advance :D!
Community feedback
- @vanzasetiaPosted over 2 years ago
Greetings, Luis! ๐
It's good to see you completing another challenge! ๐
Regarding your question about the container element, if you see the site on a wide screen like 1800px, you will notice that the site starts becoming too large. So, I recommend having a
max-width
to prevent the elements from becoming too large.Also, I recommend only limiting the page content instead of the background too, this way the site looks more natural and has no empty space while the footer has full width.
More feedback.
- Put the
header
element outside of themain
element. It's not going to have meaning if you put it inside themain
element. - I suggest removing all the visually hidden headings and making the
h2
ash1
instead.sr-only
is used only if the site has no visible text like an icon button or in Frontend Mentor challenges circumstances, no visibleh1
on the component challenges (assuming that theh1
exist somewhere else on the page). So, my point is that don't use visually hidden element as long as there's visible text. input
withtype="submit"
was used before thebutton
element exist. It's best to avoid using legacy elements. So, I recommend usingbutton
element instead.- The secondary navigation on the
footer
should be wrapped bynav
element. Add anaria-label
to bothnav
elements so that screen reader users can distinguish the two navigation elements. So, thenav
on theheader
would be the primary navigation, so the value for thearia-label
would beprimary
and for the other one wouldsecondary
. - Good job on labeling the social media links! ๐
That's it! Happy coding!
Marked as helpful1@PazispeacePosted over 2 years ago@vanzasetia Thank you!!, I have done what you told me. I will try to not forget about those details next time.
Thank you so much for taking the time to help the community!!
have a nice day! happy codding to you too
Edit:
I forgot to change the input to button for submit. Already done.
And yeah! I was aware of the button, somehow I forgot about it when making the form, thank you so much!
0@vanzasetiaPosted over 2 years ago@Pazispeace You're welcome! ๐
Amazing! Great job with the updates! ๐
Keep up the great work!
1 - Put the
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