Icon displays just fine in local development firefox and in google chrome.

I want users to be able to download my resume.

Currently my resume is available on google drive. I will get a link that triggers a download for the file and use that in my button component for downloading the resume

I think I want to prioritize this one as it's lowest LOE and I want to write the copy for it as I develop the site

https://developers.google.com/identity/gsi/web/guides/get-google-api-clientid

Looks like the recommended practice for handling the google login API is potentially to have the request to google's api happen in the backend. This is also beneficial because it keeps our clientId a secret.

We'll need a few things to get this working:

• Backend API
• auth endpoint
• (Potentially) Redeploy website so that it's using https, seems like for frontends this is necessary
• Authorize domain

This one has few pieces.

• Will use highcharts and D3 graphs
• Connect with notion API (will need a backend endpoint to return this data to frontend)
• I want to also add an art gallery for my drawings

See figma for design for this page

Depends on:

• #14

Users should be able to login with their google account via a button on the top right of the web page

Switch out todowheel with the blog, write a few details about it

I'm thinking of staying with the square motif. I'm going to do something simple because it's time to move away from the default favicon.

No testing framework is currently configured for the frontend. Keep in mind that this project is using next.js

I want everything that's not a ui page for nextjs to be in a src folder within app. It will contain anything from components to utility functions. The justification for this is to have a clear separation in code between directories related to next routing and directories housing re-usable blocks of code.

This issue is dependent upon defining a metadata schema for github repositories that will stay relatively stable for the forseeable future. The approach here is going to be to define a proto that will declare the shape of the metadata file. Proto and repo to generate it will be provided in a separate repository.

• Add cloudfront distribution
• Point cloudfront distribution at S3 bucket
• Can cognito identity from blog page be re-used / migrated to a shared stack? This question is cost-driven, but just a gut feeling about my initial dealings with cognito. Based on the service used it can introduce cost based on the user pool. Documentation and code references TBD for this one.

This issue could potentially use a bit more refinement time.

note: This is just the beginning of the API endpoints the frontend will need. Should put consideration into mapping to accommodate other types of requests

• Notion Integration endpoint should be stored as a parameter in SSM
• Lambda + API Gateway to serve info to frontend

Useful links:
Notion Postman API
Notion Filter condition

Highcharts React

https://api.highcharts.com/highstock/
https://api.highcharts.com/highstock/series.line

https://www.highcharts.com/demo/stock/compare

Date time mapping
Date time mapping
Relevant Stackoverflow

I don't want to use redux, I think I can just use a combination of useContext and useState in order to pass around the following states:

• whether or not a user has logged in
• dark / light mode
• (Optional?) Current color scheme -- This one may or may not be necessary because each page has their own color scheme, not sure if global context is the place to set it, but maybe... -- I do like this idea though because we can have a global setter without having to repeat the logic... maybe I can just turn this into a hook called useColorScheme?

Website redesign incoming

Since this is integrating rustdoc, this might be the one of the more complicated pages to implement. Need to build the book and then somehow reference that build in our webpage. I think the play here is to use submodules, as well.

This feature relies on configuring a frontend testing framework.

For this, on a push to any branch, github actions should run the frontend testing suite.

Projects should be listed 6 at a time and paginated if more exist

The new url will become about.nameofthemist.com