---
# System prepended metadata

title: v3 Developer Working Sessions
tags: [v3]

---

---
tags: v3
---

# v3 Developer Working Sessions

## Topics
- Tasks we can start writing and assigning before we have UX spec
    - ops
        - deployment pipelines 
            - gh actions for skynet deployment
                - domains alpha.summon.daohaus.club / alpha.hub.daohaus.club
            - gh actions for npm deployment
                - v0.01
            - gh actions for subgraph deployment
            - gh action for serverless lambda deployment
        - local development env
            - session to fire up apps + readme docs
                - and use libraries in our apps
            - prettier/linter setup
                - task to setup and document the rules nx comes with
                - vscode workspace settings in the repo
                    - format on save
        - figure out qa env
    - repo setup
        - contract
            - baal as an npm package/open zeppelin style?
            - or in repo for local dev
            - how to maintain connection to moloch mystics
        - subgraph in mono repo
            - local dev?
        
    
    - app setup/boilerplate
        - routes
            - hash router
        - pages
        - simple layout
            - hub = hero/banner
        - navigation

- how can we split the teams for this
    - contract/subgraph - db/sk

    - summon rage - jord
        - component library 
            - micros/atoms - aw/jp/jord
        - data sdk - sk/keating
            - utils
    - hub rage - santiago/keating ???? 
        - more components library - aw
        - more data library - sk


- summon + hub design review
    - data inputs/outputs sweep
    - micro/macro component sweep
    - repeatable when new designs are ready
    - material for us to write up tasks
 
    - how can we capture and enact aciton on larger patterns
        - in ui
        - in functionality

    - Summoner app task notes
        - inputs for factory/transaction task:
            - https://hackmd.io/35DFxb31TnW2d7lIMKDu9Q
            - add permission levels
        
        - data sdk
            - encodeActions util

        - atomic components
            - summon buttons
                - need a states
            - inputs
                - text
                - select/drop downs
                    - need states
                - checkbox
                - helper text
                    - props to pass text
            - text and titles
            - link
            - disclosure/accordian
            - tooltip
            - icon
        

        - macro components
            - list import/table inputs
                - add list element
                - import list element
                - data formatting into what the contract wants


    - hub rage app
        - usecases
            - user can log in
            - dao lists
            - basic user data
            
        - data sdk
            - fetch and transform
            - data related to a user address
                - ceramic
                - cross chain daos
            - haus price data

        - components
            - atomic
            - macro
                - address avatar

        - out of scope
            - people
            - proposals
            - badges
            - edit profile


- how/when do we transistion rage apps into sage apps
    - alpha to beta to v1
    - what all gets done with this
        - refactor + tests added

- look forward to core ui

- Haus Data library
    - scope
        - rage: read and transform data
        - rage: utils
            - encodeAction(abi, action, args)
        - sage: 
            - do we support write/tx legos
            - do we have a version with browser helpers/local cache

- Haus Component library
    - can we get a design style guide in figma?
        - ui elements w/ all states


- names for our libraries?

- when storybook?
    - try in rage apps or once we have a few components in the library

- when/how do we want to update/change ui legos


## Activities and questions
- App design reviews
    - where does the data come from?
    - is transformation needed from the source?
    - is there complex interaction needed that requires addtional manipulation or fetching (filtering, sorting, pagination)
    - what components can we start building?
    - macro component sweep


- Discuss fetching scenarios
    - single dao
    - multiple dao/network (hub)

- What are all the sources for UI ready DAO data
    - subgraph
    - s3 style cached json
    - other apis - or is that all wrapped with our functions

- Where might advanced/backend data caching be needed vs. a wrapped api
    - wrapped apis to hide keys
    - when would it be best to cache in skynet/bucket
        - multiple data sources transformed into something easy for UI

- Based on initial apps, discuss SDK feature set
    - formbuilder handles transaction - does SDK need to? 


- How can SDK and redux play together

## Outputs
- general data models needed for UI
    - hub, then core later?
- 1st stab at basic/subset of SDK interface
    - data fetch
    - utils
- 1st stab at a list of components to build
    - atomic
    - stuff in the summon form?

## Reference

v2 data catalog
https://hackmd.io/o7cVYOO4SxiZ03afDDufqA

redux wrapper of an sdk
https://github.com/superfluid-finance/protocol-monorepo/tree/dev/packages/sdk-redux

