Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

CSS Flex, Custom Properties, maintaining simplicity

Daniel•130
@tenczowy
A solution to the Social links profile challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I am trying to get a good undestanding of html and css basics and get used to writing clean and maintainable code so if there is anything to improve in this field any suggestion are welcome.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Justin Connell•720
    @justinconnell
    Posted over 1 year ago

    Hi Daniel, Your solution looks great on mobile and desktop resolutions - your code is well structured and readable - I can tell at a glance what's going on - so great job on that front.

    Something tells me you're already familiar with the general principles of clean code, you can tag me if I'm wrong - but since you asked, using a well defined methodology such as BEM will help you discover a method for naming and organising your CSS classes.

    Personally I think you're doing the right thing by honing a very strong base in HTML and CSS, this will stand you in good stead in your career going forward.

    Keep it up, I like your style.

    Marked as helpful
  • Petrit Nuredini•2,860
    @petritnuredini
    Posted over 1 year ago

    Congratulations on completing your projects! It's a significant achievement, and you should be proud of the work you've put in. Here are some best practices recommendations to help you refine your skills further:

    • Code Organization: Make sure your code is well-organized. Use comments to segment your CSS and JavaScript files, making it easier to navigate through your code. Organizing your code into sections (like header, main content, footer, etc.) can be very beneficial.

    • DRY Principle: Follow the Don't Repeat Yourself (DRY) principle. If you find yourself repeating the same code, consider creating reusable classes or functions. This approach not only saves time but also makes your code easier to maintain.

    • Semantic HTML: Continue to use semantic HTML elements as they provide better accessibility and help with SEO. Elements like <article>, <section>, <aside>, and <nav> give meaning to your content.

    • Responsive Design: Ensure your website is fully responsive. Test on various devices to guarantee a seamless user experience. Using relative units like em or rem and media queries can greatly improve responsiveness.

    • Cross-Browser Compatibility: Test your website on different browsers to ensure it works consistently across all of them. Sometimes, what works on one browser might not work the same way on another.

    • Performance Optimization: Optimize your website for performance. Compress images, minify CSS and JavaScript, and leverage browser caching to reduce load times.

    • Accessibility: Aim for greater accessibility. Use alt tags for images, ensure adequate contrast between text and background, and use ARIA labels where necessary.

    • Version Control: If you haven't already, start using a version control system like Git. It’s a great way to track changes, experiment with new features, and collaborate with others.

    • Continuous Learning: The field of front-end development is always evolving. Keep learning new technologies, frameworks, and best practices. Websites like MDN Web Docs, freeCodeCamp, and CSS-Tricks are great resources.

    Remember, every project is a learning opportunity. Keep experimenting and pushing your boundaries. The more you code, the better you become. Keep up the great work, and I'm excited to see what you create next!

    Marked as helpful

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

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