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,
Β
- Dev work needs to be split between bug fixes and creating new pages/component based off new design
- Decentralised Research and Discussion
- https://docs.google.com/document/d/11Q6w09CeEjRJLRf6yNckGGY0ua5Y597VCOY1XLIrVAk/edit
- Why are we doing this?
- Practicality? ROI? - what value does it bring to the product (the website)
- Vision element - for what we believe in. decentralisation
- Cost vs a centralised solution ( Vercel )
- we will have 2 versions. 1 web2 (vercel/netlify), 1 web3 deployment (fleek)
- 2x domains that will point to the web2 and web3 (.eth address) version respectively
- Fleek has DNS support.
- New idea of how content on site is updated
- core content will be in the repo
- recurring content will just be a link to wherever its being hosted
- keep to the writerβs guild current workflow, they continue to post wherever they are currently doing and we just punchout to that
- epoch 1 - site is decentralised and design refresh
- epoch 2- content gateway where content is decided by community concensus and we integrate with that
- come back after we finish all we wanted in the season β to look at decentralised github (radicle)
- Set up a show and tell with Radicle.xyz
- To use our recurring meeting timeslot