BanklessDAO
BanklessDAO
/
Operations Department
Operations Department
/
📖
Notion Administration
/
Top-Level BanklessDAO Notion Pages
Top-Level BanklessDAO Notion Pages
/
🚧
Projects
/
bDAO Website
/
Website Meeting Notes
/
Website Weekly Sync 31/8

Website Weekly Sync 31/8

Last edited by
Note-taker
Type
Weekly
Brainstorm
cadence
Flow
Date
Aug 31, 2021
Attendance
Last Edited Time
Feb 4, 2022
What has been done:
  • Zberwaldt: A bunch of pull requests have been done, busy with pagination. Claiming is only still a few weeks, should be over, so stopped working on that. Soosh, Turinglabs and Foxyblocks came at the right time. web3 connect is done, just still review the code and do the pull request
  • Lucas: The claiming will be done soon, so no need to still add that.
What's next:
  • Work on issues that are still open in Github. A big one is the translation of the content. ⇒ James: about translations, the functionality foundation is there, but what content should be translated to which language? This will take some time and we are only 5 weeks away from launch. We will have to see how we can implement this for the MVP: automatic or manually or a combination. Grendel will assist with coördination with the translation guild. Having everything translated will be too expensive.
Translation task brain dump from James in the Discord Channel: 1. Automated translations with WeGlot 2. Translation overrides from Ghost locales 3. NextJS static locale generation 4. Global manual site translations by Translations guild (10-18 languages, navigation, core headings & copy) 5. Translation best practices research 6. Select language UI 7. Aria/screenreader support
⇒ This is at least 50 hours of dev work, not including any translation costs (which scale based on what we want done)
So we need to determine quickly: 1. How much time have we spent so far 1a. How much time do we have left to budget 2. What is the remaining required scope 2a. How much time would that scope take 3. Do we need more budget from Grants Committee.
  • work on the must-haves like sign-up page, guilds page, core content pages, products page,...
  • We need a flow for all the new ideas that come in. Where is MrPackman when we need him :-)
  • Lucas and MW came to join the meeting for help with the content. Any help with curation is welcome. We should work on a document of what we want to get implemented and what stuff to link to. A strategy of what we want to show off and needs to be in the featured area.
  • James: We need to decide what success will look like.
Brainstorm:
  • Lucas: Add flavour to the website with the Bed Index Price?
  • MW: Can we visualise how it is to join the DAO? A live feed of a main discord channel for example? Not seen before but could be nice.
  • MW: Should we not put a welcome banner?
  • Yves: the content is everything. A visitor of the website should feel like he's up to date with the space and the DAO.
  • Yves: About the allocations, how will we reward everyone for the work done so far? Pay for the hours, or Coordinape or a combination ? Coordinape is more DAO-like, what do other DAO's do? ⇒ James: paying by the hour can be a difficult excercise, Coordinape generally works in a fair way.
  • We should get more people involved, as the webiste has been seen as a small project so far, but it's actually the project that links everything together. It's time to get the writers and AV guild on board for the content.
Action items
Update the weekly meeting: Put the Developers Room as the place for the meeting and 1 hour instead of 30min. ( MrPackman )
Curation of content that needs to be on the website, to what do we have to link, what needs to be featured? ( Lucas & MW )
Then organize a scoping meeting to map out what still needs to be done and who does what. (Katarina )
Objectives & Budget S2 ( MrPackman & Yves )
Decide on which languages we want to translate to, 10 to start? (Grendel )
Work on a flow for all the new ideas that come in ( MrPackman )
Get all the hours worked so far by everyone and decide on the allocation distribution ( Katarina will send out a form, then meeting with the team )
 
BanklessDAO
BanklessDAO
/
Operations Department
Operations Department
/
📖
Notion Administration
/
Top-Level BanklessDAO Notion Pages
Top-Level BanklessDAO Notion Pages
/
🚧
Projects
/
bDAO Website
/
Website Meeting Notes
/
Website Weekly Sync 31/8

Website Weekly Sync 31/8

Last edited by
Note-taker
Type
Weekly
Brainstorm
cadence
Flow
Date
Aug 31, 2021
Attendance
Last Edited Time
Feb 4, 2022
What has been done:
  • Zberwaldt: A bunch of pull requests have been done, busy with pagination. Claiming is only still a few weeks, should be over, so stopped working on that. Soosh, Turinglabs and Foxyblocks came at the right time. web3 connect is done, just still review the code and do the pull request
  • Lucas: The claiming will be done soon, so no need to still add that.
What's next:
  • Work on issues that are still open in Github. A big one is the translation of the content. ⇒ James: about translations, the functionality foundation is there, but what content should be translated to which language? This will take some time and we are only 5 weeks away from launch. We will have to see how we can implement this for the MVP: automatic or manually or a combination. Grendel will assist with coördination with the translation guild. Having everything translated will be too expensive.
Translation task brain dump from James in the Discord Channel: 1. Automated translations with WeGlot 2. Translation overrides from Ghost locales 3. NextJS static locale generation 4. Global manual site translations by Translations guild (10-18 languages, navigation, core headings & copy) 5. Translation best practices research 6. Select language UI 7. Aria/screenreader support
⇒ This is at least 50 hours of dev work, not including any translation costs (which scale based on what we want done)
So we need to determine quickly: 1. How much time have we spent so far 1a. How much time do we have left to budget 2. What is the remaining required scope 2a. How much time would that scope take 3. Do we need more budget from Grants Committee.
  • work on the must-haves like sign-up page, guilds page, core content pages, products page,...
  • We need a flow for all the new ideas that come in. Where is MrPackman when we need him :-)
  • Lucas and MW came to join the meeting for help with the content. Any help with curation is welcome. We should work on a document of what we want to get implemented and what stuff to link to. A strategy of what we want to show off and needs to be in the featured area.
  • James: We need to decide what success will look like.
Brainstorm:
  • Lucas: Add flavour to the website with the Bed Index Price?
  • MW: Can we visualise how it is to join the DAO? A live feed of a main discord channel for example? Not seen before but could be nice.
  • MW: Should we not put a welcome banner?
  • Yves: the content is everything. A visitor of the website should feel like he's up to date with the space and the DAO.
  • Yves: About the allocations, how will we reward everyone for the work done so far? Pay for the hours, or Coordinape or a combination ? Coordinape is more DAO-like, what do other DAO's do? ⇒ James: paying by the hour can be a difficult excercise, Coordinape generally works in a fair way.
  • We should get more people involved, as the webiste has been seen as a small project so far, but it's actually the project that links everything together. It's time to get the writers and AV guild on board for the content.
Action items
Update the weekly meeting: Put the Developers Room as the place for the meeting and 1 hour instead of 30min. ( MrPackman )
Curation of content that needs to be on the website, to what do we have to link, what needs to be featured? ( Lucas & MW )
Then organize a scoping meeting to map out what still needs to be done and who does what. (Katarina )
Objectives & Budget S2 ( MrPackman & Yves )
Decide on which languages we want to translate to, 10 to start? (Grendel )
Work on a flow for all the new ideas that come in ( MrPackman )
Get all the hours worked so far by everyone and decide on the allocation distribution ( Katarina will send out a form, then meeting with the team )