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

CSS Chat App. Built with: Tailwind | SASS | CSS @keyframes.

Bonrey•1,130
@Bonrey
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 there, everyone! 👋 Here's another CSS challenge I decided to tackle.

At first, I wanted to practice another CSS framework — Tailwind. However, I didn't find it very entertaining: looking up specific tailwind classes when I can just write my own styles, ugh. 😒

Don't get me wrong, I still learned a lot about Tailwind! In fact, it's the best CSS framework I tried. (As some of you know, I also tried Bootstrap and Bulma in the last couple of challenges.) It is very comprehensive: you get way more classes than in Bulma and can style your page with virtually no CSS! However, sometimes, there's still a need to apply a very specific value to width or use pseudo-classes (or -elements), for instance. Well, you see, no matter how extensive a certain framework is, plain CSS will always be more flexible. 😏

So, I believe that from now onwards, I'll write my own styles, using SASS, and use CSS frameworks only for super-small projects.

Well, thanks for reading this long text till the end. 😅 And happy coding to all of you! 💻

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • ApplePieGiraffe•30,525
    @ApplePieGiraffe
    Posted about 4 years ago

    Hello there, Bonrey! 👋

    Just came to say great job on this challenge! 👏 Your solution looks really good and the animations that you added are very fun! 😀

    And thank you for trying out all of those CSS frameworks and coming to a conclusion for me! 😂 Seeing your small CSS framework journey and hearing your thoughts has been interesting. I think I'll follow your lead and keep at it with good ol' CSS for now! 👍

    Keep coding (and happy coding, too)! 😁

  • tediko•6,700
    @tediko
    Posted about 4 years ago

    Hello, Bonrey! 👋

    It's very good that you trying different things. Good job on this challenge. I've nothing much to say this time. The one thing you can add is to push your own messages when you use input for messages.

    Good luck with that, have fun coding! 💪

  • MuhammadSamir•510
    @Muhammad-samir
    Posted about 4 years ago

    Clean work

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.

Frontend Mentor for Teams

Frontend Mentor for Teams helps companies and schools onboard and train developers through project-based learning. Our industry-standard projects give developers hands-on experience tackling real coding problems, helping them master their craft.

If you work in a company or are a student in a coding school, feel free to share Frontend Mentor for Teams with your manager or instructor, as they may use it to help with your coding education.

Learn more

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

Oops! 😬

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

Log in with GitHub