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

rock-paper-scissors

sass/scss
Mahmoud•270
@Mahmoud-solaiman
A solution to the Rock, Paper, Scissors game challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


It took me LESS than a week to complete this fun challenge

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Bishal Singh Deo🎮•1,440
    @Bishalsnghd07
    Posted over 1 year ago

    Hey, I play the game and really like it. I won by 3-1☺️ You are doing great job, I would just say keep going on🏃

    Apart from the fun zone, I have one suggestion for you, I see when I click on your website url, I amazed that you had been used GitHub url that means you deployed your project in GitHub. I will recommend you to use GitHub only for tracking and saving local repository into it. By any chance if your local repo get deleted in your pc, then from GitHub you can clone that remote url and reuse in your local, for that case GitHub should have been made not for deployment purpose only.

    I would say, use netlify or vercel for deployment of your project free, it only made for run your website. So, by doing that you are maintaining professionalism in your work.

    Hope, this tips will help you in your future projects too!

    Happy Coding💓

    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