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

chat app css illustration

Israel John•150
@Israeljon
A solution to the Chat app CSS illustration challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Guys, I really want you to look it over and feel free to comment. Guys, I really need help in my message send icons to appear in my work

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ebi Akangbou•170
    @Ebi-Akangbou
    Posted almost 3 years ago

    Hello John, Great work. Please how can I post my solution with vercel.

  • Elaine•11,360
    @elaineleung
    Posted almost 3 years ago

    Hi Israel John, this was not an easy challenge, but good job putting this together 🙂

    About the send icon, I see you using class names that look like ones you'd find in Font Awesome; where are you putting in your icons from? I don't see any links in the head tags and I don't see anything in your stylesheet either. You can try finding an icon on Font Awesome, and you probably need to set up an account with them (which I believe is for free). They have a lot of icons for free (they also have paid ones), and you may be able to find one there.

    One other quick comment I have:

    Your phone is looking rather large right now! Try setting a max-width: 20rem with padding: 1rem, and removing the other widths and padding you have in percentages. Whenever possible, try not to use percentages for paddings and widths unless you are certain that you can have an optimal view at all sizes. The problem with using percentages and viewport units is that what looks good at one browser width may not look good on for another browser width.

    Good luck finding that icon!

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