Hi, Ralph.
Don't be disappointed in this solution. I think you did a great job. My first try at this took a very long time.
I am not seeing any horizontal scrollbars. Did you fix the problem?
I struggled to get the images to overflow the page. I will have to check out this solution.
Hope this helps.
David
Nice job.
A couple of suggestions. You want your main content to be in a Main tag for accessibility. You should also use the blockquote tag for the testimonial quotes. There are several contrast issues with the design. It isn't required to fix them in the challenge, but it will help fix accessibility issues.
Get AXE dev tools:
AXE dev tools
What are you most proud of, and what would you do differently next time?
I'm more comfortable using grid and flexbox layouts. I've also adopted the BEM (Block, Element, Modifier) naming convention for SCSS. While I prioritize using modern fonts, I ensure compatibility with older browsers. Matching exact spacing and fonts from design files can be challenging. For future projects, I'll focus on creating adaptive solutions with visually appealing elements. I won't strive for pixel-perfect font replication, as it can be time-consuming.
What challenges did you encounter, and how did you overcome them?
The challenge was finding the exact padding and fonts used in the design files. I figured it out through experimentation.
What specific areas of your project would you like help with?
At this point i am more comfortable with working in css and html. Do you use the same font sizes and spacings as in the design photos? Do you try to match the exact elements in design files, like font sizes and spacing, or do you use your best judgment to achieve the most accurate representation? Also if you find any mistakes or have suggestions for improvement, please let me know. I will be very grateful.
Nice job, Darek.
I have started using BEM more and more now. It makes it easier to name classes, and they are more relevant.
I try to match the layout as much as possible, but some of the older challenges have spacing that isn't totally accurate. Sometimes I change things and go with what looks good to the eye.
Hope this helps.
David
Just looking at this quickly, the image is set to display: none at 1024px. If you use the Devtools to inspect the page you can turn off that property and the image will show up. You will have to position it as it is not in the right place.
Hope this helps.
David
I want to know if this is the best practice for writing the code for this project? Or is it a clean code I wrote?
The logo picture is not showing on the live demo but is showing on my localhost. Does anyone know why?
Making Global components was a lot of fun, if there is a better way to write or think about them, please inform me.
I want to know if this is the best practice for writing the code for this project? Or is it a clean code I wrote?
The logo picture is not showing on the live demo but is showing on my localhost. Does anyone know why?
Making Global components was a lot of fun, if there is a better way to write or think about them, please inform me.
Nice job with this.
Your logo isn't showing because you forgot to add the dot in front of the path to the images folder. Your other images have it, which is why they are showing up.
To clear the accessibility issues, wrap all of your main content in a main tag and change the ALL YOUR FILES text to an H1. Every page should have an H1. You can style it however you want it to look. Don't use Headings according to their size. You can always re-style them. You also want to avoid skipping Heading sizes as well.
Change your div class of footer to an actual Footer tag since this is a footer. You can leave Headers and Footers out of the Main tag since they have semantic meaning already.
Add the code aria-label="Facebook link" or whatever describes it to links that only show icons for screen readers.
That should clear all of the accessibility warnings.
Any feedback welcome, Made it within 1 hour. I am great learner and I will be happy to hear anything regarding design and code in order to enhance my skills. Feel free to share your thoughts.
Do you think the code needs any changes? Please let me know so I can keep improving.
And if you liked it, you know, give me a lot of love by pressing the like button.
You did a pretty good job on this. The submit button can use some work, they are a little small at some resolutions. The phone and mail Icons are distorted at some resolutions as well. You also want to research form validation as you will need to use it later on.
Add Fylo to the ALT text on your logo images, and add aria-label="Facebook" etc.. to the A tags surrounding your social media icons. That will clear the accessibility warnings.
Download AXE DevTools and you can clear accessibility warnings while you code.
https://www.deque.com/axe/devtools/