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

Chat App CSS Experimental_Grady

Andrew Grady•175
@agr227
A solution to the Chat app CSS illustration challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Second challenge since my break and I felt like I was right back in it! I was able to spend most of the day studying and going over some of the formatting, sizing, and design basics.

This challenge was a lot of fun because it has a certain simplicity to the web layout, but the challenge of designing a phone's messaging layout.

I remember when I first started I kept hearing all of the YouTube coders saying they spend most of their time googling how to do something or trying to find sources to base their code off of and I finally realized how helpful that could be. I utilized the resources I had and I believe I was learning better by doing that because I wasn't just making endless mistakes and getting frustrated that I couldn't figure things out on my own.

This is not going to be an exact copy of the example. I took creative liberties to improve as I saw fit.

If anybody sees anything funky in my code or spots something visually that just doesn't look right please please please let me know. At this point I'm getting comfortable making these challenges my own and would like to take the step into Java before long, so if there are glaring deficiencies now is definitely the time to catch them!

As always, thanks for the help and feedback!

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Andrew Grady's solution.

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.