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

responsive card i should only use css external only but i rush lol

react
IRON Michael•180
@Iron-Michael
A solution to the Recipe page 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?

this is remind me a lot of html basic technic i can write again without nervous i can enjoy to write more

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

the hard part is font adapt to make it similar to the matrix because i use front end mentor free version i don't know the real resolution i use my eyes and my sense analysis and write down the code

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

should i use external css only in responsive design??

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Dilara Ajaj•60
    @dilaraj
    Posted about 2 months ago

    Hey!

    Your solution looks great. Just some tips based on your final solution:

    • Look over grammatical and spelling errors. As they can affect the overall professional look of your websites/solutions
    • Ensure there is a high contrast between your text and their background for those that are visually impaired. This improves the usability of your website for a variety of people.

    As for your question, yes external css is best as you move on to be a professional developer. Not only does it allow for code to be reusable with the use of classes in your html tags. It also increases the readability of your code as it separates html and css code. This makes everything look much neater and gives your code a clean and professional look.

    Good luck!

    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