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

Solution to Chat App Illustration

Gian Ramelb•160
@rame0033
A solution to the Chat app CSS illustration 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 use of pseudo-code ::before and ::after helped me to add content like accent designs and radio button for the choices in the message container.

The snippet below will show how I did the styling for the mockup radio button

.time:before {
  content: '';
  display: inline-block;
  height: 1rem;
  width: 1rem;
  border: 0.1rem solid var(--radio-btn);
  border-radius: 50%;
  margin-right: 0.5rem;
}
What challenges did you encounter, and how did you overcome them?

I was hesitant to do the phone app but I discovered to make a container that will have respective divs for every element and class to style each individual properly.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Raphael Holzer•850
    @DigitaleWeltLibrary
    Posted about 1 year ago

    Hey, good soluten.

    I have two points for improvement:

    • Give the main element a height. Then you can't see the footer on the screen.
    • The violet banner on the left side is on the mobile version smaller. Then you can read the text easier.
    main{
          min-height: 100dvh;
    }
    

    I hope i could help you to improve your skills. 😉

    Happy coding 😊

    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
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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub