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

Responsive Rock-Paper-Scissors game using CSS Grid

Abdulhamid Adeniji•160
@Alpha437
A solution to the Rock, Paper, Scissors game challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello Fellow developers,

It's been a while since I last shared my journey here. Balancing school activities and coding can be quite a task. However, as my exams drew to a close, I felt the need to challenge myself and improve my coding skills.

Have you ever been in a situation where you couldn't decide how to manage time? How did you navigate through it?, share your experience in the comment section.

I recently took this advanced challenge that required me to work with HTML, CSS, and JavaScript. It was one of the most demanding tasks I've encountered on my tech journey.

I faced UI issues that pushed me to revisit the fundamentals of CSS, particularly the display property, to get the layout just right. A piece of advice to my future self: Always break down a UI into its basic elements before diving into coding, it'll save you a lot of time.

Here's what I gained: -Proficiency with the Object-fit CSS property.

  • Mastery of the repeating-radial-gradient CSS property for captivating design effects.

Remember, growth happens when we step out of our comfort zones. Stay curious and keep coding!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Abdulhamid Adeniji's solution.

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.