Maybe the next iteration of the field editor will be some sort of drag and drop component system, like block code editors e.g. micro:bit’s MakeCode
I'll need to add the possibility for conditional fields and nested fields to my checklist. At this point my goal for Goby is to allow you to create complexity into oblivion, for no necessary functional reason.
Goby's uniqueness is only intelligible through its symbiotic relationship with Are.na itself
Given this, I think I need to lean into replicating/enhancing Are.na's native features with the power of a tabular data system:
- connecting new blocks in goby
- viewing other goby channels and being able to connect blocks to your channel, maintaining the metadata from the original
- an extremely robust, comfortable system for editing and bulk editing data
- a plurality of ways to view the same interface, as a grid or a table or something else altogether
One key difference between are.na's ontology and typical tabular data systems is that a single "column" is always kept constant: the media itself. This is the way that a block derives its identity, and can traverse different channels where it takes on different contextual meanings.
Goby might be understood as something like Airtable superimposed on Are.na's powerful ontological structure.
This isn't exactly a value proposition, although I've been wondering how one would formulate that for Goby. The truth is I wasn't really motivated to keep building Goby by the utility factor — it was just fascinating to build this sort of system from scratch, on a technical foundation that I still consider quite elegant.
I was apparently crashing the API putting my content PUT requests in the URL parameters instead of the body... oops! Anyway it uses the request body now, seems to work
If anyone would like to test out goby, the build page I just pushed allows you to initiate and edit your own Goby channels. goby.garden
Full disclosure: Goby currently uses local storage to hold access tokens, so if you're concerned about security, use it in incognito for now.