that would copy a nice json object to the clipboard (to share with friends and fellow learners of course!)
considerations:
copy size could get large (how large? good interview question!)
when do we stop adding functions to that project element? More buttons could be more busy.
potential expansions include:
filters on the copying ("security").
a. If we had a "work-in-progress" wikitree, riddled with stream-of-consciousness notes, but you wanted to share the current version with your coworker, you could filter out all of the notes. If paired with some kind of flagging on wikipedia page node objects
combine with the marketing of great teachable moment about localstorage, indieweb & owning your data
wikipedia page node objects -- the nodes in the main graph pane that represent a distinct wikipedia page
notes -- the nodes in the main graph pane that represent custom notes
We could add a little
guy to this guy
that would copy a nice json object to the clipboard (to share with friends and fellow learners of course!)
considerations:
potential expansions include:
definitions: (see https://github.com/jimmcnulty41/wikitree.website/issues/4)
wikipedia page node objects -- the nodes in the main graph pane that represent a distinct wikipedia page notes -- the nodes in the main graph pane that represent custom notes