Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 11 months ago

Chat-App-Css-Illustration

Neel Mishra•240
@Neel-07
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?

I am most proud of successfully implementing the visually appealing chat app illustration using HTML and CSS. The project allowed me to focus on front-end techniques such as positioning, media queries, and animations to create a polished and interactive design that closely resembled the provided design specifications . Next time, I would enhance my project by paying more attention to detail in terms of responsiveness and interactivity, ensuring that the chat interface animates seamlessly on the initial load as an additional feature, providing a more engaging user experience .

What challenges did you encounter, and how did you overcome them?

I encountered challenges in aligning certain elements of the chat interface properly across different screen sizes. To overcome this, I leveraged flexbox and grid layout techniques to ensure consistent alignment and responsiveness. Additionally, troubleshooting through browser developer tools helped me identify and resolve layout inconsistencies efficiently .

What specific areas of your project would you like help with?

I would appreciate feedback on optimizing the CSS code structure for better maintainability and scalability. Specifically, advice on organizing stylesheets, improving naming conventions, and minimizing redundancy in the codebase would be valuable for enhancing the project's overall maintainability and future development .

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 Neel Mishra'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.