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

Social links profile made using SCSS and partial 7-1 pattern

sass/scss, semantic-ui
Łukasz Lubaszewski•140
@luckyszakul0
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?

The speed at which I'm doing these small projects is slightly faster each time, while more or less keeping the quality of my work.

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

I don't think there is anything mentioning here.

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

I would really appreciate some feedback on the use of my 7-1 pattern in SCSS files, as I sometimes don't know where to put a specific file. I know this doesn't make sense to use the pattern for such a small project, but I wanted to give it a go. Also, I tried using the BEM naming combined with kebab case for SCSS class names, but I don't think I did a good job with that.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Christian Camilo Beltran Fonseca•170
    @CamiloBeltran24
    Posted 9 months ago

    Hi @luckyszakul0 ! Great job on this project!

    I think reorganizing your folders a bit could make your structure even cleaner. Try moving your design, scss, and css folders into the assets folder. This way, all your static resources—like styles, images, and designs—are in one place, which makes everything easier to find and manage as your project grows.

    Also, it looks like there are quite a few files here for a project this size. Simplifying a bit could make it easier to navigate and keep tidy, especially if you're working with others.

    Awesome work overall—keep it up!

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