uclaacm / selector-safari Goto Github PK

View Code? Open in Web Editor NEW

7.0 19.0 0.0 3.22 MB

a WIP game designed to teach funky CSS selectors!

Home Page: https://selector-safari.uclaacm.com

License: MIT License

HTML 3.78% CSS 10.63% JavaScript 85.59%

teach-la learning-labs

selector-safari's Introduction

Selector Safari

Overview

Selector Safari is a WIP game for learning CSS selectors!

Selector Safari is made by Drew, Nandana, Kevin, Janis, Nhi, and Lisha from the Teach LA Dev team.

This project is the brainchild of Matt and is inspired by Flexbox Froggy, Grid Garden, and Flexbox Defense. It uses React. We promise it will be playable soon :)

figma: https://www.figma.com/file/Hcet8ZB9HjIx13dNu2LEnk/Wire-Frame?node-id=0%3A1

Development Setup

We'll use a really common Node.js project workflow!

First, let's clone our repository, and install all of our node dependencies:

git clone https://github.com/uclaacm/selector-safari.git
cd selector-safari
npm install

To start our app, you just need to run npm start!

npm start

And to build our project for production (with CRA's webpack bundling and all that goodness),

npm run build

Contribution Workflow

Want to make a change? Great! Here are the steps:

Either make a new branch or a fork of this repository. master is a protected branch, so you cannot push to it.
Follow the instructions in "Development Setup" above. If you're on a fork, replace the URL with the fork's URL; if you're on a different branch, check it out using git checkout.
Make your changes!
Before you push, make sure your app builds with npm run build. If there are any errors, our CI/CD service will reject your build.
Once you're ready, stage and commit your changes!
Make a pull request with your changes, and let someone on the dev team know. Netlify has a neat feature called "Deploy Previews" that give you a link to preview your changes; see the blog post for more info!
If your code passes code review, we'll merge it into master. Congratulations! If you'd like, it's now safe to delete your branch/fork.

Licensing & Attribution

This project and its code are licensed under the MIT License. You're free to use them however you wish, though we'd love to hear from you if you found this useful!

Create React App Artifacts

You can delete these if you want!

This project was bootstrapped with Create React App.

Available Scripts

In the project directory, you can run:

`npm start`

Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.

The page will reload if you make edits.
You will also see any lint errors in the console.

`npm test`

Launches the test runner in the interactive watch mode.
See the section about running tests for more information.

`npm run build`

Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.
Your app is ready to be deployed!

See the section about deployment for more information.

`npm run eject`

Note: this is a one-way operation. Once you eject, you can’t go back!

If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.

Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.

You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.

Learn More

You can learn more in the Create React App documentation.

To learn React, check out the React documentation.

selector-safari's People

Contributors

Stargazers

Watchers

selector-safari's Issues

Save progress

Use browser storage to save progress
https://developer.mozilla.org/en-US/docs/Web/API/Web_Storage_API

Related -- if the user switches levels, should we clear the editor? Would be nice if we saved it for each level

Game Tutorial Pop ups

On first level, add little textboxes with arrows that explain what the different tools in our game do.

Level Tutorial: Change from hyperlink to button

The hyperlink for "level tutorial" at the top right of the page should be changed to a button so that it's easier for users to know that they can press it.

Only match level paths for existing levels

E.g. the user could try to go to path /level/50 but we don't have a level 50
https://stackoverflow.com/questions/37269736/react-router-how-to-constrain-params-in-route-matching

level 5 issues -- solution verification needs to ignore background stickers, support null ids

For example, in level 5, the plant stickers aren't supposed to be part of the level, but the game doesn't know that so you can't pass the level unless you change their colors. Also, need to make the color changing work for stickers without an ID.

Change HTML Content Tab for descendants

HTML Content tab currently has incorrect formatting for descendent selectors on level 5, this should be fixed.

Bug: Fix 'Great job! Next level' text

After passing a level, if you go to the next level using the arrows at the top right instead of the 'next level' button, the 'Great job! Next level' text is still shown.

Handle when user uses too many selectors

E.g. most levels could probably be passed using just the ID selector, so we need to restrict that

count selectors by counting brackets?
should every level even have IDs (at least, IDs that we show to the user)?

Background color for each level needs to be changeable

e.g. level 4 only works if the background color is green

Make an HTML + CSS tab, and fill in details

Doesn't need to look as good, but if you want, you can make it look like
https://www.figma.com/file/Hcet8ZB9HjIx13dNu2LEnk/Wire-Frame?node-id=0%3A1

Tooltips for Copied on Hexcode Hover

Add a popup so it's more obvious to the user that a hexcode can be copied when it's hovered over.

Remove left arrow for level 1

On the first level, there is left arrow on the top-right. This doesn't need to be there, however, since there aren't any levels before level 1.

On hover in html tab, highlight corresponding sticker component

Probably a good idea to have highlight the corresponding sticker that an HTML tag refers to to make the game more intuitive for the user.

Copy hexcode to clipboard and display color of hexcode text

Some levels need you to use a specific hexcode, so it would be convenient if you were able to click on the hexcode to copy it

It would also be nice if the color of the text of a hexcode was actually the color of the hexcode itself.

(Optional): Also, there should probably be a little dropdown or something that has all the hexcodes they might need (e.g. background color, "green")

Tutorial section: style code so that it doesn't look like body text

At the moment, the code in the level tutorial just looks like body text, which makes a little difficult to read. We need to fix the font/style of the code so it pops more!

Sanitize user input

Or maybe it's fine since we're using DOM methods as described here: https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Safely_inserting_external_content_into_a_page ?

Code editor colors don't contrast well with background

Fix HTML Tab content

Current HTML content only displays id's of the components, not their class. Need the content to also show the class.

Fix check function that checks if you passed the level

The current check function runs the same check for every single level. Need to fix this function so separate checks run for each level.

Ex.

Make tutorial for level open by default

For accessibility purposes, it would probably be best if have the tutorial banner for each level open by default.

Only go to next level after you complete current level

I think there should either be a reminder or warning if you try to go to a new level before you've completed the levels leading up to that point. Maybe this can be done with 'solved' state / the check function?

Refresh code editor on each level

I think at the moment the code editor currently saves the CSS used on the most recent level even on subsequent levels. There isn't any bug with functionality of the game however, as the old CSS disappears as soon as we refresh the code editor on the current level, even if we haven't inputted anything in the current level yet. I think it would be nice if we could address this issue for polish though.

first level:

third level:

Notice how the zebra is still blue even though the code editor hasn't had anything inputted yet!

Align arrows at top right on first and last level

It's hard to show with these screenshots, but the 'level X' text becomes unaligned on the first and last level. This can probably be fixed by hiding the CSS instead of deleting it

uclaacm / selector-safari Goto Github PK

selector-safari's Introduction

Selector Safari

Overview

Development Setup

Contribution Workflow

Licensing & Attribution

Create React App Artifacts

Available Scripts

npm start

npm test

npm run build

npm run eject

Learn More

Code Splitting

Analyzing the Bundle Size

Making a Progressive Web App

Advanced Configuration

Deployment

npm run build fails to minify

selector-safari's People

Contributors

Stargazers

Watchers

selector-safari's Issues

Recommend Projects

Recommend Topics

Recommend Org

`npm start`

`npm test`

`npm run build`

`npm run eject`

`npm run build` fails to minify