Since this button is not technically a link like the others, it does not receive keyboard focus.

Perhaps wrapping it in an anchor with an onClick handler with e.preventDefault()? This may be poor practice; research required.

On mobile, selecting a section tab doesn't always return the window to the top of the page as intended.

To Reproduce Bug:

1. On mobile, go to "About" tab.
2. Scroll to the bottom of the page, or at least a good portion down.
3. Click "Contact" in the top navbar.
4. Contact page appears, but does not scroll up as intended.
5. Clicking "Contact" again will scroll the page to the top as expected.

Expected Behavior:
Clicking a section tab should always return the page to the desired scroll position (top)

This may be an issue with Element.scrollIntoView(). The documentation here mentions:

"The element may not be scrolled completely to the top or bottom depending on the layout of other elements."
I'm not sure what the conditions are for this to happen/not happen.

On the project cards, tabs, other places where the onHover color-changing functionality is used, we shouldn't see the same color twice in a row.

TODO: Add some sort-of check to ensure that the color is not the same as the previous iteration.

Research required.

May be Gmail/authentication related, although I thought that was handled.

The preview images for the websites are pretty small. I'd like to create modal img functionality so that users can click the image and have it expand so they're actually legible.

This is doable with purpose-built React libraries, but I think I'd like to do it myself so that I understand how it works.

Viewport should not remain on the "Send" button after sending... need to implement autoscroll so that the user is able to see success message.

ALSO, the success message is really hard to see! Need to add color, animation, highlight, or something along those lines to make it clear that the action has completed.

As a follow-up to ensuring that the site is keyboard-navigable, it would be nice if the style of the focus outline were aligned with the style of the site itself, rather than just using browser default.

This is probably the CSS property elem:focus { }.

There are now two components (SectionButton and ProjectCard) using identical functions for "color" state. Needs a small refactor, probably to place this in App.js and pass it down as a prop instead. probably just creating a small utilities.js file and importing it from there when needed.

It seems that either something with WidgetBot has changed, perhaps there is some difference with the way I am "logging in" on my end on the site.

Either way, SparksieBOT is no longer listening to commands sent via WidgetBOT. Strangely, SB still responds correctly to "on_message" events even though they are sent by the same "user" as the ignored command attempts.

It is possible that the issue is with SB. If so, it is likely a problem with the way that WidgetBot presents its "users". SB checks to see if the bot sending a command is WidgetBot, and responds if so. Perhaps WidgetBot is somehow adjusting its identity based upon the user it is representing?

TL;DR - SparksieBOT will respond to commands invoked via Discord, however does not respond to commands invoked via WidgetBot from this portfolio site.

Either create a 404 page, OR set things up so that all domains redirect to home.