Almost created another Google doc, then opened my feed book instead... # @build.sputnik-dao.near | Funding Processes ## **🚧 DRAFT IDEA ~ WORK IN PROGRESS 🚧** *This #documentation #idea is an outline of a guide for navigating the Build DAO processes during this upcoming March funding cycle. Please comment with any #feedback.* ``` --- ``` # Contributor Guide ## Overview Everyone is a builder! Post an #idea on your preferred gateway to get started. **STEP 1:** #BUILD SOMETHING **STEP 2:** COLLAB —> LEARN **STEP 3:** GROW COMMUNITIES Other builders may reply to connect with you. Feel free to share #documentation, and please ask questions (with #question), which builds momentum here @every.near #social ### FURTHER ACTIONS - Create a Near Social post with a widget or any type of thing embedded (courtesy of builders: @efiz.near and @archetype-org.near) - Use #update for daily, weekly, or monthly reports ~ your choice! - Explain your impact in terms of [sustainable development goals](https://sdgs.un.org/goals) #SDGs - Discuss potential strategies and opportunities with collaborators - #Request funds by turning any post into a request for approval by sending proposals to various accounts over time. - Earn #rewards for valuable contributions. Register for donations and other types of public goods funding through PotLock. Patrons can sponsor matching rounds for specific #pots of resources ([more info](https://docs.potlock.io/welcome-to-potlock/understanding-pots-funding-rounds)) #docs This has certain advantages. One is you can turn *everything* into Sputnik DAO proposal or a transfer request to any account, including those with multi-signature capabilities. ##### Build DAO SDK Thanks to @megha19.near, we are building a modular [DAO SDK](https://near.social/near/widget/ComponentDetailsPage?src=megha19.near/widget/daoSDK) to integrate DAO widgets with apps on the blockchain operating system. She also made a [multi-sig SDK](https://near.org/near/widget/ComponentDetailsPage?src=megha19.near/widget/multisigSDK) #BOS ### GENERAL PROCESS ##### Why build together? Start by doing your best to understand the specific problem that you are motivated to solve with a project. Our goal is for every project building value and #impact to a community, a product, or any other type of thing. #NEAR #Builders empower communities to develop sustainable projects on the #OpenWeb! We are building [software development kits](https://near.org/sdks.near/widget/SDKs.App.Pages.Home) (#SDKs), [libraries](https://nearbuilders.org/library), and core [templates](https://everything.dev/?page=core) ~ with forkable demos and composable, multi-chain apps #code #sample *@mattb.near created this [doc](https://sdks.near.social) explaining how to use `VM.require()` @sdks.near* ##### How to build a thing: First, [search](https://everything.dev/?page=search) for an example of whatever you are hoping to build. Try to visualize a basic user interface design (#UI / #UX) with particular styling, layout, and functionality. When you find something that is good enough, fork it by duplicating the code or whatever data is the thing, either in #js, #md, or #json format. Other file formats will be more accessible via @hyperfiles.near ***NOTE:** Sometimes you have to dig into the #app to discover important widgets.* ##### What next? Ask what do people really need. Embrace a "builder mindset" (shout-out to @dawnkelly.near), and think about how to support the #commons. That means helping builders and projects help each other. Figure out how things work. Explore ways to improve types and create better ones. Design templates with features that integrate core modules @devs.near *How can everything evolve to support better futures for everyone?* > --> [architecture discussion](https://github.com/NEARBuilders/gateway/issues/43) via GitHub, started by @jass.near