back_end

⁠

confluence

as our network is de-centralized, the three touch-points we have with collaborators are our app, our Confluence workspaces, and our coda “system of pages.” communication is key. communication is key (wait, did i already say that?). we hope to use these systems for project management, creative thinking, individual project development, etc. we hope to be different than the guy who wears a suit to work and thrift clothes at home. the back-end is our home, and for this there’s no compromise - we want to wear a suit. confluence is intended to be used primarily for communication and collaboration. our goal is to use a few tools with narrow focus and depth in utilization. confluence is my first choice, and i believe it is the best tool to keep everyone on the same page, productivity continuing, and relieve any/every tension that comes from miscommunication.

⁠

coda

if confluence is for communication, coda is for our “systems.” this is an internal (family of) pages that logs all of our templates, keeps track of progress indicators for individual projects, and otherwise maps the space between various collaborators. this is very simple tool - so our progress lies in our creativity with it. we hope it serves as a priceless tool as we develop the various facets that need to be involved to make this project a success.

⁠

Want to print your doc?
This is not the way.

Try clicking the ⋯ next to your doc name or using a keyboard shortcut (

CtrlP

) instead.