Component checklist

Generate posts from Lens (and then generate Lens posts from threads)

Update index styling for Lens with the @thirdweb-dev/Lens-Starter-Kit

Proposed user flow for the comments section:

  1. Once the user has viewed the planet on /sailors/dataset/tess/planets/[id], they can then create a proposal post
    1. This creates a new page at sailors/proposals/tess/planets/[id]
    2. Parameters:
      1. User Address (Eth)
      2. User ID (Supabase/Moralis)
      3. NFT ID (including collection in format collectionAddress/tokenId)
      4. Data visualisations (images → links to the images sent from Matplotlib to Supabase/IPFS)
      5. Comment for each data visualisation (referencing the d.v. ID)
      6. Final classification decision
      7. Additional images/assets & comment points (foreign key set to mimic the behaviour of the data visualisations)
      8. Votes required (const, cannot be changed)
      9. Current votes (set to null at creation)
      10. List of voters (set to null at creation)
      11. Proposal id (format collectionAddress/tokenId/[id])
  2. This proposal is then sent to Supabase
    1. Github issues & discussion points will be created on the sytizen repository and then sent to DeWork.xyz
    2. Proposal data can then be sent to IPFS & an NFT id in the MVP stage
      1. This IPFS endpoint will be hosted on DeWork and a trait dework_id will be added. Initially, it will be set to null and updated when DeWork creates a task that calls the IPFS id

Planet page components

Tabbed section to show different iterations of the planet (i.e. different owners)

3D view of the planet

Infrastructure list & actions section