Website Refresh
Created
Jul 2, 2021
Type
Status
Project
Priority
Coordinator
Contributors
Guild
Property
Overview
S2 Project Summary
Summary
The Website Refresh is just that, a quick refresh of the current bDAO site to greatly improve our brand image online.
The bdao website is currently not fit for the bankless movement our bDAO represents and we can iterate quickly to get us a lot closer to the vision we have for our brand. This is not a long-term solution, it is a step in the right direction that will give us more time to create the next version that will be better but needs more time to plan and execute.
Website prototype by Yves for MVP :
Organize It
Table
Squad
Name
Notes
Tags
15/12 In Discord Channel and claimed bounty. A full-stack dev for 4 years already and looking to expand my development skills to web3
In Discord Channel 10/12
Fullstack engineer with 7 years of experience located in the US-PST, currently work in Ruby/Rails/Postgres/Mongo/React/Typescript/GraphQL/Apollo
Previous job was Python/Django/Flask(for a couple smaller apps in the company ecosystem) /Vue/MySQL and before that I worked with fullstack JS on MERN stack applications
In Discord Channel 10/12
a decent amount of front-end experience building my own apps as well as React Native experience building for mobile.
16/11/2021fresh out of school with a cs background. I'm interested in front-end dev and love to contribute this website project. Have some React experience.
joined 2/9, guestpass
I'm fullstack js
frontend focused - react, nextjs
can use web3 and such in projects
consulted some ICOs in 2017-18
(done web work)
Typescript too !
built a CEX arbitrage bot once in JS and cloud functions - not scared of backend but FE is fun for me
Table
DAO-wide Meeting Notes
Weekly, Project, Other
Last Edited Time
Last edited by
cadence
Date
Flow
Note-taker
Type
Attendance
User stories
How the product should work for various user types.
User type 1
User type 2
Scope
Requirements
Current project requirements.
- CMS - Ghost
- Web3 connect a wallet
Future work
Future requirements.
- Reconsider CMS and decide if need to replace Ghost
Non-requirements
List anything that is out of scope.
Designs
Include designs here or add directly to the Requirements or User Stories sections.
Alternatives considered
List any alternatives you considered to this approach. Explain why they weren't used.
Related documents
Include links to other pages as necessary (e.g. technical design doc, project proposal, etc.)