gallery-so / gallery Goto Github PK

• Collection name and description view
• Navigation footer
• Select NFT "tray"
• Drag-to-order collection view

modal?

check out react-snapshot

right now the crawlers can't load dynamic JS (twitter/facebook/google/etc), so the title/preview image/etc. would have to sent off the bat via server. this is the benefit of server-side rendering... and one of the things we lose out on by moving off of nextjs 😬

there are ways to pre-render the app for crawlers to hit, which we'd have to configure.

in terms of the images themselves, the server would need to create and save a "preview image" whenever someone creates/edits their collection, which @ivan_nyc should be able to do because he's a master of image editing. the image will be stored at some URL, like assets.gallery.com/collectionID, and whenever the user shares their gallery link it'll pull an image from that assets domain (and use a fallback if none exist)

lock sign up/collection creation behind password for now

by Phil

https://mux.com/

Give Links ability to handle onClick

looks like a text and takes a callback

What's the best way to do web3 logins?

https://walletconnect.org

https://github.com/3box/3box

Draw out the flow of the website so dev can visualize what the pages and flows look like.

by phil

Deactivate wallet connection on sign out

Allow user to connect with a wallet. initial scope can be limited to support for 1 wallet as proof of concept.

Rewrite frontend using Create React App + Typescript.

• Create react app
• Adding Typescript

Get a server error when one of a user's NFTs had null for image_preview_url

core components should go in here

after displaying success indicator, modal should auto-close and reveal logged in wallet

Pull from opensea, rebuild functionality from alpha

We're currently using image_preview_url on the Gallery profile page so the page loads quickly.

Some animated NFTs still animate because the file is a .gif, but others are just static images.

How can we make sure all animated NFTs are animated and looping?

define schemas and endpoints @ openapi v3: https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md

openapi -> golang: https://github.com/deepmap/oapi-codegen

openapi -> typescript: https://www.npmjs.com/package/openapi-typescript

SWR

Example contexts: https://github.com/Robinnnnn/good-vibes-only-client/tree/master/src/contexts

Example with error context:

• Defintion: https://github.com/Robinnnnn/good-vibes-only-client/blob/master/src/contexts/Error/ErrorContext.tsx
• Initialized: https://github.com/Robinnnnn/good-vibes-only-client/blob/7ae3e47c48a97c5f1b6b790b938b9445c6086590/src/App.tsx#L10
• Used: https://github.com/Robinnnnn/good-vibes-only-client/blob/43a9ce6ee50c0939cb04dbd6cce1001dd0886dd8/src/contexts/Auth/AuthContext.tsx#L99

NFTs can belong to multiple users, but it looks like it can't in our system currently. Each NFT entry is unique by id and has only one associated user_id. So we have a situation for example where an nft is actually owned by five of our users, but the owner_id in our db is whoever set up/edited their gallery most recently or first(?).

by robin