jon-xo/cascade

A classic arcade single-page web application built using React.js, RESTful APIs, and Material-UI.

🎉 Nice to meet you, I'm Jon—

I'm a full-stack software developer with a passion for learning and experimentation. I've got an eye for documentation, and I enjoy technical writing. I love engaging with other developers and expanding my community and knowledge. As I continue to learn and grow, I'm working to share my knowledge, teach, and support others to one day work in a Developer Relations role.

What I work with

What I'm learning

My stats

Check out my 🛠 work or say ✉ hello !

---

cascade's Issues

Game Player #4

Story

Once the user selects an available game title, the user can load the title and initiate gameplay.

Acceptance Criteria

Given Registered user selects a game title
When User clicks the play button
Then A play page loads with an embedded element from API
And Page provides details about selected title

Favorites & Recently Played widgets #9

Story

When a returning user loads the home page, they are presented with two widgets that display a short summary of recently played titles and favorites.

Acceptance Criteria

Given Registered user logins one or more times
When User has played a minimum of one title or marked one game as favorite.
Then Widget(s) displayed dynamically one home page featuring thumbnail of game artwork and game name.
And User can launch game details or navigate to game player from widget.

Game Library #3

Story

Users should be able to visit a single page and browse all available titles.

Acceptance Criteria

Given User wants to view all available game titles
When User clicks the Library button in the navbar element
Then User is presented with a full game library in card view with game title, release year, publisher, and more info button.

Game Search #5

Story

The application should allow a user to search for a specific title by name and be presented with a list of similar matches available in the game library.

Acceptance Criteria

Given User attempts to locate a specific game by title
When The Home or Search loads and the user enters in a search query
Then User receives a list of matches returned by the search provider

Game View Toggle #10

Story

When the user browses a list of games, they can display the title in either a graphical card view or a detailed list.

Acceptance Criteria

Given Registered user logs in
When User selects Library, Favorites, or views results returned in Search
Then User can click a toggle to switch between a grid (card) or list view.

Enhanced Details #8

Story

When a user selects a game title from search, favorites, or library—enhanced artwork and details are provided to the user.

Acceptance Criteria

Given Registered user is logged in
When User loads game or clicks game details
Then Secondary API provides artwork, additional game details.

Notes

About – IGDB API docs

Game Favorites #6

Story

A User should be able to select any title found in Library or Search views and mark that item as a favorite.

Acceptance Criteria

Given User would like to save a title to find easily within their user account
When On completed Search or Library page load, the user clicks the Favorite affordance on a specific game.
Then Game is identified as a favorite in the database
And Page displays a modal to confirm successful addition.
And Modal provides a link to quickly change to the Favorites page.
And Modal fades after a short time has elapsed.

Given User has marked a minimum of one title as favorite
When Favorites page loads
Then User can add / edit a custom note
And User can rate title out of four stars
And User can remove title from list of favorites

Help #7

Story

A help menu is available across the site in the event the user would like to learn about available features, or can't navigate the application UI.

Acceptance Criteria

Given A registered user is logged in
When User is unable to correctly navigate UI or use a feature
Then User clicks on the help affordance and is provided general information about the application.
And Information is sorted by topic
And User can navigate to a help topic using a table of contents

Authentication #1

Story

Given A user visits the application
When it is the user's first visit to the website,
Then the user is present with a registration affordance and provided information on account criteria.

Given A registered user visits the application
Then The registered user is presented with the login page/affordance on the first load.

Navigation #2

Story

Given A user successfully logs into the application
When Page loads
Then User is presented with a splash page, that provides navigation, prominent search, and getting started banner.