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

Blog Preview

vite
P
Aaron Deimund•70
@Aaron-Deimund
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 used Vite for the first time on this one. I also feel like I did a good job with the semantic layout. I tried some visually hidden headers to maintain the hierarchy, and I'd be interested to know how other people would structure the data.

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

Getting Vite to deploy to a folder Github pages could see. I ended up putting it into a docs folder, which is the other place Github allows you to serve from by default. I saw there was some documentation on using .htaccess to change the root folder, but I couldn't get it to work. I also saw documentation on Vite for Github specific builds after I already set up this repo.

I also had problems getting the blog preview image to display in the flex-box card without a container div. I feel like the container div on the image is unnecessary, but I couldn't get it to maintain its width without it.

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

How others handle the hierarchy of headers. the blog title was clearly not an H1, but that's where you have to start. I ended up just setting some headers and organizing things with hidden elements.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Clark Tolosa•550
    @clakr
    Posted 5 months ago

    Hi! 🙋‍♂️ Congrats on completing the challenge.

    I did not know about the Vite and GitHub Pages issue so thank you for sharing what you have experienced to the community, your experience sheds a light and potentially be helpful to someone.

    Your approach with the semantic layouts and hiding them visually is what most would do, even I. But if you really want to set the blog title as an <H1 />, you can use the order CSS Property. It is a tradeoff though, as you will sacrifice code readability for semantic layout.

    If you have questions, concerns, feel free to bump me through this thread! 😁

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

Oops! 😬

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

Log in with GitHub