this probably needs multiple sub-tasks, lol. but here's a basic list that might be easier than i suspect.
move inline typography styles to the theme
move copy/paste elements to components. most everything is on the home page right now, so i would accept defining them in the home route component for now. but we need to start identifying re-usable ones as the about and blog pages start to come online
delete commented code or move it to a component if it is useful code for future features
run the linter and typecheck to make sure code quality doesn't get too far behind. we need to enforce those soon AND start writing tests
move the deploy command to a github actions workflow (this already has a ticket), then replace the explicitly stated aws resource values to actions variables so they are not exposed. this isn't super-sensitive but there's no reason to advertise this information publicly.
so definitely break these up into subtasks but until i have time this is an acceptable documentation of what needs to happen
this probably needs multiple sub-tasks, lol. but here's a basic list that might be easier than i suspect.
so definitely break these up into subtasks but until i have time this is an acceptable documentation of what needs to happen