Alex Simoes

The confetti referred to here, is what the user sees when completing the last slide of a level. At one point we were considering making changes to the configuration but...

The idea here was to implement some sort of gamification by giving users "points" for completing various tasks. Things like completing lessons and codeblocks, logging in multiple days in a...

This was a "nice to have" but not required. As a further explanation, React uses the `ref` prop as a means to access the underlying HTML node. It was not...

This is related to #7. Executing this wouldn't require any database changes, though it would require significant API and front-end refactoring.

To give more context, this was a simple UX improvement to help first time users understand how to advance to the next slide.

Similar to #409 this is a series of UX improvements for the contest sign-up form. Users are not required to add their school's location, instead they could check the "I'd...

Originally the intent here was to allow users to find their classmates snippets. For example, on the first island, where there is such a long list, this could be a...

To clarify, the thought here was to add more styling related to the specific island that the slide belongs to as a visual reminder of the lesson they're completing.

Currently there is a bit of an inefficiency with the way the "Map" / user progress is shown in the Nav. Everytime a user clicks the dropdown, it requires a...

To clarify, this is able sending an email notifications when someone replies to your comment in a discussion thread. This would require hooking into mailgun and some database changes to...