Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 4 years ago

Made in HTML and using SASS for the first time

Eddy Cerpa•145
@edycerpa
A solution to the Chat app CSS illustration challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello, i used SASS for the first time because I read it's easier but i think it's sooo much harder than simple CSS, i had big troubles to make responsive this challenge, at the end I think it's all good.

All feedback is welcome. Thanks

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Dave•5,295
    @dwhenson
    Posted about 4 years ago

    hey @edycerpa great work on this one - it looks lovely! 🙌 I have also only just started SASS, and I have to say after a couple of challenges I'm really starting to love it. But I also found it really tricky to change over from regular CSS.

    I would really suggest trying a couple more challenges and see if you get comfortable with it. That said, I really made sure I was OK with the CSS basics, and how I structure my code before trying it - so I wouldn't rush into it.

    Some small suggestions on this challenge:

    1: It looks great at large viewports, but at smaller screens the margin on the bottom of the phone pushes the text quite a way off screen - you might want to reduce this?

    2: I would consider using background-image for the background images rather than the body-bg divs you have at the moment. This will just make your code cleaner.

    3: Semantically this one is tricky, and up for debate for sure, but I would consider putting all the messages in a ol and have them as li items?

    4: Lastly, and I think I'm on stronger ground here, I would suggest the msg area at the bottom should be an input with the submit element as a button.

    Really nice job though 👍 Keep up the great work!! Cheers 👋

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