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

blog preview card using html and css

Gunal K•90
@Gunal-k
A solution to the Blog preview card 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'm proud of how the styling turned out for the preview card container. The use of Google Fonts, the color scheme, and the layout adjustments contribute to a visually appealing design.

However, if I were to approach a similar front-end challenge next time, I'd focus more on ensuring browser compatibility and responsiveness. Testing across different browsers and screen sizes is crucial to delivering a consistent user experience. Additionally, I would aim to make the CSS code more modular and organized, perhaps by utilizing CSS preprocessors like Sass or by breaking down styles into reusable components. This would enhance maintainability and scalability of the codebase.

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

One challenge I encountered was ensuring that the layout and styling were responsive across various devices and screen sizes. To overcome this challenge, I utilized media queries to adjust the styles based on the viewport width. By testing the layout on different devices and using tools like browser developer tools to simulate various screen sizes, I was able to identify areas that needed adjustments and fine-tune the CSS accordingly.

Another challenge was selecting an appropriate color scheme that not only looked visually appealing but also provided good contrast and readability. To address this, I experimented with different color combinations and tested them in the context of the preview card layout. I also considered accessibility guidelines to ensure that text and interactive elements had sufficient contrast for easy readability.

Lastly, integrating external fonts from Google Fonts posed a minor challenge in terms of correctly importing and applying the font styles. However, by following the documentation provided by Google Fonts and ensuring proper syntax in the CSS import statement, I was able to successfully integrate the desired font into the project.

Overall, by leveraging testing, experimentation, and attention to detail, I was able to overcome these challenges and create a visually appealing and functional front-end design for the eMentor challenge.

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

If I were seeking help with this project, I might ask for feedback on specific aspects such as:

  1. Visual Design: Are the colors, typography, and overall layout aesthetically pleasing and appropriate for the content?

  2. Responsiveness: Does the layout adapt well to different screen sizes and devices? Are there any specific breakpoints or adjustments that could improve the responsiveness further?

  3. Code Optimization: Is the CSS code well-organized, maintainable, and efficient? Are there any redundant styles or opportunities for optimization?

  4. Accessibility: Are the colors and contrast levels suitable for users with visual impairments? Are interactive elements accessible via keyboard navigation?

  5. Browser Compatibility: Have I tested the layout across different browsers to ensure consistent rendering and functionality?

  6. User Experience: Is the user experience intuitive and seamless? Are there any improvements that could enhance usability or interactivity?

  7. Performance: Are there any performance bottlenecks, such as large image files or excessive CSS/JavaScript? Are there optimizations that could improve page load times?

Receiving feedback on these areas can help me refine and improve the project, ensuring it meets both functional and aesthetic requirements.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • shalri•620
    @shalri
    Posted about 1 year ago

    Good job on getting the design and layout of the blog review card. However, I noticed that your design is the active preview of the design. Might be just an oversight on your part, adjusting the box-shadow to the normal state should be an easy fix.

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