Website Sync 10/01/22

Last edited by
Note-taker
Type
cadence
Flow
Date
Jan 10, 2022
Attendance
Last Edited Time
Feb 4, 2022
Legend:
Decisions are highlighted in yellow
To dos are highlighted in red
Β 
Points to note:
  1. For website, The Workflow Board will be the canonical source of tasks / pending items https://www.notion.so/bankless/76a1db3d20254dc3a1f8477f1c6be937?v=2ae8dcf8758e474cb7fd742050d424ca
Β 
Agenda:
  1. Content Section
    1. Aim to repurpose what writers’ guild has already on hand to beef up the content on the bDAO website
    2. Β 
  1. Season 3 Bug Backlog
    1. tightly coupled with the current design of the website since the website is going to under some UI makeover, should we hold off on the bug list?
    2. leave the list for now, see if the redesign cuts down on the
  1. How does posts/articles in the CMS link to the site
    1. Core content vs Recurring content
    2. Core content β†’ part of the DAO and should stay
    3. Recurring content β†’ this can change and different cohorts can have articles
    4. AIM to have ppl WANT to post stuff to publicise their content instead of us paying them
Β 
  1. Analytics
    1. To have some sort of baseline for current site β†’ for a before vs after stats
    2. new site = more eyeballs more page views etc (good publicity)
    3. from website β†’ discord β†’ to guild joins etc
  1. Design
    1. IDEA: bounty for winner of competition to design the site
    2. Β 
  1. Operations
    1. Multi-Sig Transfer β†’ close to being completed
      1. previously there was an β€˜Accounting’ role to handle $$ flow
  1. Hosting the bDAO site using a full decentralised stack
    1. Fleek (https://fleek.co/)
    2. Pinata (https://www.pinata.cloud/)
    3. ENS (https://ens.domains/)
    4. To be explored in terms of time effort and cost
    5. To take the time between now and the website redesign competition to explore decentralised hosting
  1. Community Call
    1. To copy out the template slides to google slides
    2. So that we can fill out our content and just copy pasta it over to official community call deck when it comes out
Β 

Website Sync 10/01/22

Last edited by
Note-taker
Type
cadence
Flow
Date
Jan 10, 2022
Attendance
Last Edited Time
Feb 4, 2022
Legend:
Decisions are highlighted in yellow
To dos are highlighted in red
Β 
Points to note:
  1. For website, The Workflow Board will be the canonical source of tasks / pending items https://www.notion.so/bankless/76a1db3d20254dc3a1f8477f1c6be937?v=2ae8dcf8758e474cb7fd742050d424ca
Β 
Agenda:
  1. Content Section
    1. Aim to repurpose what writers’ guild has already on hand to beef up the content on the bDAO website
    2. Β 
  1. Season 3 Bug Backlog
    1. tightly coupled with the current design of the website since the website is going to under some UI makeover, should we hold off on the bug list?
    2. leave the list for now, see if the redesign cuts down on the
  1. How does posts/articles in the CMS link to the site
    1. Core content vs Recurring content
    2. Core content β†’ part of the DAO and should stay
    3. Recurring content β†’ this can change and different cohorts can have articles
    4. AIM to have ppl WANT to post stuff to publicise their content instead of us paying them
Β 
  1. Analytics
    1. To have some sort of baseline for current site β†’ for a before vs after stats
    2. new site = more eyeballs more page views etc (good publicity)
    3. from website β†’ discord β†’ to guild joins etc
  1. Design
    1. IDEA: bounty for winner of competition to design the site
    2. Β 
  1. Operations
    1. Multi-Sig Transfer β†’ close to being completed
      1. previously there was an β€˜Accounting’ role to handle $$ flow
  1. Hosting the bDAO site using a full decentralised stack
    1. Fleek (https://fleek.co/)
    2. Pinata (https://www.pinata.cloud/)
    3. ENS (https://ens.domains/)
    4. To be explored in terms of time effort and cost
    5. To take the time between now and the website redesign competition to explore decentralised hosting
  1. Community Call
    1. To copy out the template slides to google slides
    2. So that we can fill out our content and just copy pasta it over to official community call deck when it comes out
Β