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

Responsive Chat App ilustration with animations

Jakub•210
@flexer89
A solution to the Chat app CSS illustration challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi, please share your feedback and let me ask some questions.

  • I didn't get any background images so i made it from scratch using HTML/CSS. Was it good?
  • Sometimes i still have difficulties with css properties order. Is there any system or pattern how to arrange them, or there is just a freedom?
  • Is it a good practice to comment the code like me? I mean CSS code
Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Vanza Setia•27,715
    @vanzasetia
    Posted almost 4 years ago

    👋Hi Jakub!

    Regarding to your questions:

    • In this challenge you have to create the background and the illustration from complete scratch, that's why this is an intermediate challenge. If all the images has been prepared this might be a junior challenge 😁. In my opinion the two background needs to be bigger.
    • The property order is matter. For instance if you do this, then the body background would be blue.
    body {
      background-color: red;
      background-color: blue;
    }
    
    • OR, the property order that you mean is maybe like sorting the property based on alphabetical order? Well, I would recommend the CSS Concentric property order.
    /* Alphabetical Order */
    body {
      background-color: red;
      color: white;
      display: flex;
      justify-content: center;
    }
    
    • Based on CSS Guidelines, it's good to "title" your CSS for every section. But, it's not always a must to have comment.

    Feedback:

    • Use rem or sometimes em unit instead of px. It's a good practice to never use px most of the time, like in this case.
    • For any decorative images, like in all the images, you should leave the alt="" empty and add aria-hidden="true" to make sure all screen readers ignore those images.

    That's it! Hopefully this is helpful!

    Marked as helpful
  • Dušan Lukić•1,660
    @dusanlukic404
    Posted almost 4 years ago

    Hi Jakub, I did this challenge a few days ago so I think it can be helpful for you to hear my suggestions.

    First, I will answer on your questions.

    • Every challenge on Frontend Mentor should be from scratch but in this case you did not have any images so you have to use only CSS. I think you did good job
    • You shouldn't have problems with properties order. They are only specificity. I recommend you to have a look on w3schools about it or on Mozilla Dev Network
    • You should always have comments on your code, so it is awesome

    Also, I have a few suggestions for your solution:

    • Make heading and paragraph text smaller on mobile devices
    • Chat text shouldn't be bold
    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