### BUILDER UPDATE: Jan 23 - Jan, 2024 (posted via [Build DAO Gateway](https://nearbuilders.org/feed?hashtag=update)) **✅ DONE** - Reviewed bos-workspace 1.0.0.wip, opened a PR with [feedback + quick fix](https://github.com/NEARBuilders/bos-workspace/pull/51) @achraf.near - Tried out @mattb.near's clone, push, pull functionality in [bos-workspace](https://github.com/NEARBuilders/bos-workspace/pull/52) (it's really convenient!) - Initialized [buildbox](https://github.com/NEARBuilders/buildbox) project while testing bos-workpace, to create a [submission form for Abstraction Hacks](https://near.social/#/buildbox.near/widget/AbstractionHacks.Submit) - Wrote documentation on [how to create a canvas with draw.everything.dev](https://near.social/mob.near/widget/MainPage.N.Post.Page?accountId=efiz.near&blockHeight=111574373) - Posted an idea for [autogenerated component libraries & theming](https://near.social/mob.near/widget/MainPage.N.Post.Page?accountId=efiz.near&blockHeight=111572510) - Braindumped [some resources](https://github.com/NEARBuilders/gateway/pull/99) for @dawnkelly.near - Merging various PRs for Build DAO Gateway **⏩ NEXT** - Finishing MVP for request flow this week -- this means next steps for Create app and embedding things in posts. How can we build a better experience for writing markdown documents? - Finishing refactor + clean up for Build DAO gateway, ideally to offer generic feed component by end of week. - Need to revisit Types; this is key for embeddings @archetype-org.near **🛑 BLOCKERS** - I have been stuck on these "organizational" issues for so long... there are so many repositories with code spread about everywhere. When working on anything, it is a lot of killing + restarting bos-workspaces, looking for code from one repo and pulling it into another; it get's pretty exhausting. This is a bit of an issue with local development in general and I've suggested a solution to bos-workspace [here](https://github.com/NEARBuilders/bos-workspace/issues/50), although it means some reworking. These are the main repositories I have: * [near-everything/viewer](https://github.com/near-everything/viewer) - this holds the gateway code for everything.dev and the relevant widgets for every.near. * [near-everything/canvas](https://github.com/near-everything/canvas) - this holds the gateway code for draw.everything.dev and the relevant widgets by everycanvas.near (open to condensing under a different account, probably every.near, although most widgets are specific to tldraw...) ^^ I would really like to collaborate with others on these repos so I've wanted to move them to nearbuilders org (and I've tried this + reverted), but this means moving over domain names too... and I have a lot of apps in near-everything org running through everything.dev rn. -- to be honest, I've thought that both of these gateways should be combined and rewritten, ideally deploying to [web4](https://web4.near.page/) -- then the domain would be something like every.near.page, which I think opens a lot of possibilities. I started an "every.near" repo [here](https://github.com/NEARBuilders/every.near). What could we do with the every.near subaccounts? * [nearbuilders/gateway](https://github.com/NEARBuilders/gateway) - this holds the gateway code for nearbuilders.org and the relevant widgets by buildhub.near (open to condensing under a different account, maybe devs.near, builddao.near, etc -- I think most of the code should be generalized and provided as a solution for other projects in the eco -- see [generalizing the app](https://github.com/NEARBuilders/gateway/issues/83) and [generalizing the feed](https://github.com/NEARBuilders/gateway/issues/82)) * [create](https://github.com/nearbuilders/create) - this holds the code for the [Create](https://near.social/#/create.near/widget/home) app (create.near) and a basic editor deployed to devs.near [everything.dev?page=editor](https://everything.dev?page=editor)... this is confusing. * [devs.near (formally bos-blocks)](https://github.com/NEARBuilders/devs.near) - this holds components like Feed, ContextMenu, Router; I think moving Build DAO gateways generic components here would be nice. * [embeds](https://github.com/NEARBuilders/embeds) - this holds all the code from when I was exploring embeds coming from settings ([see here](https://near.social/mob.near/widget/MainPage.N.Post.Page?accountId=efiz.near&blockHeight=106880385)) -- it deploys to embeds.near. To be honest, I don't think this needs to be it's own repository, but maybe it does. Maybe it can help addressing the security concern solved by a trusted whitelist of available embeds. There's an "every feed" implementation in this repo that is pretty cool too, but it hasn't been deployed anywhere. * [maps](https://github.com/NEARBuilders/maps) - this does not yet hold map related code lol, but it should. We have maps.near. What should we do with it? See the resources we put together for the LibertyDAO Mapathon: https://www.libertydao.online/mapathon. * [discoverbos](https://github.com/nearbuilders/discoverbos) - this holds the gateway code for discoverbos.org and the relevant widgets for discover.near; this really should be converted fully to widgets as to not support another gateway w/ VM updates, etc-- and then what to do with discover.near? And then there are plenty of things that are not in git repositories and are only on social contract, such as [every video](https://everything.dev/efiz.near/widget/App.index) -- this needs it's own project! What should be the purpose of each near account? What are good naming strategies for widgets + apps? I like the repository name reflecting the account it deploys to, e.g. @mattb.near's [sdks.near](https://github.com/NEARBuilders/sdks.near), but how do we solve needing to access widgets from other repos while working in bos-workspace? Should we have a monorepo with submodules? #build #update