Even though the public keys are safe to be shown on the outside, it would probably be better to keep them in .env in the case that someone wants to fork to make their own version or whatever lol.

• Refactor Supabase Client to use variables from .env
• Reset Supabase keys (i think)

https://supabase.com/blog/2022/07/13/supabase-auth-helpers-with-sveltekit-support?utm_campaign=Beta%20update%20emails&utm_medium=email&_hsmi=221545357&_hsenc=p2ANqtz-95DBnhYEt-Jr1nnhGZxwoG4oL0lRa_Oyo-7B0diN06xLDoixpALkSAO_pXNpepYhTnVlj01kQoptyzv-msJOSmXLsTSfoqo7VvAHIRIdjYFMaFPPA&utm_content=221545357&utm_source=hs_email

https://svelte.dev/blog/whats-new-in-svelte-august-2022
https://github.com/sveltejs/kit/blob/master/packages/kit/CHANGELOG.md

• Add description, tech stack, and development instructions to README.md
• Create link from website to repo.
• Update GitHub repo details with deployment link and whatnot

Anchor link that leads to twitter.com/[username]

• Create About page at /about
  Create Privacy Policy page /policy
  Create Disclaimer page at /disclaimer

Moved everything underneath /about page.

• Create links to each page as a footer nav list.

• Add more title/meta tags for all routes
• Add favicon
• Restyle Header to work better on Mobile displays (nowrap)

• Move post schema definition to its own file.
• On input, check if it fits within schema, and if it doesn't, don't update the value

Basically the same sort of thing from symbol-art-vault

Make sure to use pagination (load 20 at a time) and lazy loading

https://github.com/maciekgrzybek/svelte-inview?ref=madewithsvelte.com

Maybe this could help? Also, I could technically just write the SQL directly maybe... lol https://supabase.com/docs/guides/auth/managing-user-data#using-triggers

nvm lol

• Adjust DB function to get user ID alongside the rest of the user's data. (nvm I already am)
• Display delete button if current $user is user_id of the post within SymbolArtCard
• Move displayed posts to store for both index and catalog, with exported loadPosts({page: number, user: number} | null) that fetches according to args, and reloads with the last setting if null.
• Attach postView store to catalog endpoint

It's cheaper lol

• Import adapter-auto rather than adapter-node
• Deploy app from Vercel
• Take down app from DigitalOcean App Platform

• Create /catalog/user/[id]/[page] endpoint that loads catalog similar to /catalog but filtered with the user [id]
• Attach anchor to username within SymbolArtCard component
• Create a link from user card to associated catalog user endpoint

• Similar to symbol-art-vault
• Create table for posts and bucket for both .sar and .png files
• Sends .sar file, rendered .png, title, and associated user ID to bucket and posts table.

Catalog routes log the requested page to console.

• Remove them lol

sveltejs/kit#5774

• Create description (text) column for posts table.
• Create text field for description (textarea)
• ...

• Catch errors and either console.error them or send a 5xx/4xx as response

• Create endpoint /profile that displays user's data in system, including a post count where username matches post's username
• Create delete button within /profile that deletes user's profile on the website alongside all uploaded posts.