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

Mobile first - Chat app CSS illustration(HTML, CSS/SCSS, Extensions)

Benjo Quilario•1,790
@benjoquilario
A solution to the Chat app CSS illustration challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hey! This is my 22th frontend mentor challenge.

It's really been a while since I completed another challenge because busy in school work. This challenge is really satisfying and improve my CSS skills into another level.

Some changes in my folder because I'm not in my usual desk and I used different laptop.

  • No git that's why I used @import instead of @use my scss file.
  • I got an error when I run gulp terminal . The term 'gulp' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:1.

Feedback and Suggestion is very welcome.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Carl•1,235
    @CarlHumm
    Posted almost 4 years ago

    Wow cool solution, looks just like the design.

    I'm just a newbie but here's a couple of things I noticed.

    • No exit transitions for hover animations. When you hover over the phone, small images or menu, the animations play. But when you hover out, the animations abruptly end without any transition. You could quick fix with transition: [property] 0.35s ease-in-out or whatever timing/curve you prefer.

    • Container clips backdrop shadow. The main container has overflow: hidden which clips/hides the phones back shadow. Without this it looks cleaner and more seamless; not to mention, it doesn't seem like anything overflows anyway and if it did it would be caught be the forms overflow property.

    Regarding gulp, have you tried installing it as a global dependancy just for the command line? I see you have it as a local dev dependency.

    Try npm i -g gulp.

    Then try update / re-install gulp.

    If not, npm i gulp-cli.

    This challenge looks difficult, I look forward to doing it sometime. Great job :)

    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 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