Website Sync 12/01/22

Last edited by
Note-taker
Type
cadence
Flow
Date
Jan 12, 2022
Attendance
Last Edited Time
Feb 7, 2022
Legend:
Decisions are highlighted in yellow
To dos are highlighted in red
Β 
attendees: chkaloon, CompositeFellow, Farmer, Justice, georgeh, JohnChan, KaiDao, Ken, rixcian, Tony Stark, Cheetah,
Β 
  1. Dev work needs to be split between bug fixes and creating new pages/component based off new design
  1. Decentralised Research and Discussion
    1. https://docs.google.com/document/d/11Q6w09CeEjRJLRf6yNckGGY0ua5Y597VCOY1XLIrVAk/edit
    2. Why are we doing this?
      1. Practicality? ROI? - what value does it bring to the product (the website)
      2. Vision element - for what we believe in. decentralisation
    3. Cost vs a centralised solution ( Vercel )
      1. we will have 2 versions. 1 web2 (vercel/netlify), 1 web3 deployment (fleek)
      2. 2x domains that will point to the web2 and web3 (.eth address) version respectively
      3. Fleek has DNS support.
  1. New idea of how content on site is updated
    1. core content will be in the repo
    2. recurring content will just be a link to wherever its being hosted
    3. keep to the writer’s guild current workflow, they continue to post wherever they are currently doing and we just punchout to that
    4. epoch 1 - site is decentralised and design refresh
    5. epoch 2- content gateway where content is decided by community concensus and we integrate with that
    6. come back after we finish all we wanted in the season β†’ to look at decentralised github (radicle)
  1. Set up a show and tell with Radicle.xyz
    1. To use our recurring meeting timeslot

Website Sync 12/01/22

Last edited by
Note-taker
Type
cadence
Flow
Date
Jan 12, 2022
Attendance
Last Edited Time
Feb 7, 2022
Legend:
Decisions are highlighted in yellow
To dos are highlighted in red
Β 
attendees: chkaloon, CompositeFellow, Farmer, Justice, georgeh, JohnChan, KaiDao, Ken, rixcian, Tony Stark, Cheetah,
Β 
  1. Dev work needs to be split between bug fixes and creating new pages/component based off new design
  1. Decentralised Research and Discussion
    1. https://docs.google.com/document/d/11Q6w09CeEjRJLRf6yNckGGY0ua5Y597VCOY1XLIrVAk/edit
    2. Why are we doing this?
      1. Practicality? ROI? - what value does it bring to the product (the website)
      2. Vision element - for what we believe in. decentralisation
    3. Cost vs a centralised solution ( Vercel )
      1. we will have 2 versions. 1 web2 (vercel/netlify), 1 web3 deployment (fleek)
      2. 2x domains that will point to the web2 and web3 (.eth address) version respectively
      3. Fleek has DNS support.
  1. New idea of how content on site is updated
    1. core content will be in the repo
    2. recurring content will just be a link to wherever its being hosted
    3. keep to the writer’s guild current workflow, they continue to post wherever they are currently doing and we just punchout to that
    4. epoch 1 - site is decentralised and design refresh
    5. epoch 2- content gateway where content is decided by community concensus and we integrate with that
    6. come back after we finish all we wanted in the season β†’ to look at decentralised github (radicle)
  1. Set up a show and tell with Radicle.xyz
    1. To use our recurring meeting timeslot