We've demo'd many variations of what we must consider a long-running experiment, first with Croquet, then as an asset-based web app, and now at a powerful plugin that works well with the lineup. It's hard to say what the plugin version can and can't do. That is why we will catalog here our must suggestive work.
About Solo Plugin will be the ultimate home for the best advice once we have stabilized markup and workflows. For now we just try things and report here.
# Experiments
Aspects from Assets on the Solo's page.
Collaborating Community, working. views a year of Thompson's community sharing. His authors provide a good test case Aspects of Recent Changes when we can let Solo simplify the workflows.
Freeform Aspects, started. We will spread the diagrams Marc most frequently draws across multiple pages on multiple sites. We hope a lineup will be a good way to assemble and facilitate conversations. See also Merging Graphs from Arrow where this has been anticipated.
Aspects of Driver Trees, suggested. Can we provide additional focus by browsing a CLD driver tree as short range aspects possibly linked together in the Solo interface. See for example, Multi-Vector Learning
Supporting the Ohio Book, promised. Thompson used the Croquet collaborator to advantage curating the garden portion of his last book. We hope with the Solo plugin we can make his process transferable.
Exploratory Parsing in Frames, thinking. We've shown that much of historical Exploratory Parsing can be done client-side even for long-running jobs where the incremental updates of counts on edges provide actionable progress. How will pages of grammar correspond to aspects in Solo?
Collective Learning Felt, opportunity. We anticipate students watching each others learning journeys unfold where this specialization of Recent Changes or the Present plugin provides focused attention.