Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 5 months ago

Responsive page using css and structuring using html

pure-css
Eziefule Judith•120
@a2-112
A solution to the Social links profile challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I am happy I can make an attempt in creating an exact work or project it is interesting how detailed I try to be to make it entirely exact still learning hope to perfect my coding experience

What challenges did you encounter, and how did you overcome them?

The challenge I had was the importing the font yes at first. It didn't work out but I am glad it did at last.

What specific areas of your project would you like help with?

Margin, width and padding yes it appeared smaller than expected trying to figure out if it only because I reduced the font size.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Alexwz89•480
    @Alexwz89
    Posted 5 months ago

    Hey, you’re doing a great job with the code, particularly in terms of using rem units for flexible design. The code is relatively simple and doesn't contain unnecessary styles, which helps improve maintainability! However, you could try to further improve the responsiveness of the page by referring to Figma design files to ensure accurate dimensions and by adding media queries for tablet and mobile screens to adapt to various devices. Use Media Queries to specify different dimensions and layouts for tablet and mobile devices. This will ensure your page adapts to various screen sizes, improving the user experience. it is recommended to sign up for a free Figma account and review the .fig design files. This will allow you to better understand the designer's size requirements and layout.

    Marked as helpful
  • Eziefule Judith•120
    @a2-112
    Posted 5 months ago

    Thanks sir/ma I will definitely apply the suggestions given thank you😊😊

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
Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit all CSS, SCSS and Less files in your repository.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub