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

Responsive Reusable JS template string Solution

P
Justin Green•2,940
@jgreen721
A solution to the Recipe page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Fun design. I ended up creating a JSON object for the recipe and added one other item to demonstrate a re-usable template added via Javascript. Put an observer onto the sections for some enhanced UX but got a little convoluted on repetitive tasking with class management to prevent re-application of the observer. Nothing crazy but could probably be cleaned up a bit. Feedback/suggestions welcomed!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • ngdangtu•120
    @ngdangtu-vn
    Posted over 1 year ago

    The appearing animation is nice but there is 1 small bug in the "Preparation time". I think you forgot to add --delay css var so the animation was failed to run.

    The pagination bullet may need a bit guard in js to prevent double click. Visitors don't need the page to re-render right?

    And I like your new cover gradient, it looks much better than the shadow 👍

    Marked as helpful
  • P
    Justin Green•2,940
    @jgreen721
    Posted over 1 year ago

    I appreciate your eye/attention on this! Umm, I think I got confused on prep-item actually being prep-header (this is more a byproduct of the seat of my pants design as I go). Seeing as I didn't assign any animations/observer events to the other sections headers I'm not entirely sure why prep area is my exception, I suppose it was initial loading experience since it'll generally be in view but I'm rambling. I think its fixed and now the prep-section(header and items) is animating accordingly (once when in view and then done). Again, appreciate the look and feedback, and if it's still buggy on your experience... From my eye, it seemed your suggestion more targeted the img/img-container but maybe I read it wrong. It kind of became a templated mess down there so again I appreciate you parsing through it! 🙂

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

Oops! 😬

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

Log in with GitHub