coda Maker Cheats

icon picker
Templates, Patterns and other fine things

What are the top features of the doc?

Cheat Sheet content - high quality content to drive the discussion, to set the appropriate flight level and to establish quality standards
Display Workspace - a space to facilitate discussion of the Cheat Sheet content or other versions of the Business Model Canvas
Creative Workspace - a space to dissect, discuss, extend and enhance the content detail during the development process
Moderator Tools - supporting the workshop process, participants and individual discussions with their deliverables

Which templates/ patterns might you use?

Potential candidates and use cases:
To-Do List - making this doc; moderator workshop checklist; participant checklists; tracking participant interactions ​P.S.: Used only to manage implementation of the doc and as an
Bulk Add - adding moderator tasks on a per-participant basis ​P.S.: This is a key element in the implementation of Task Assignment
Office Hours Questions - tracking participants questions ​P.S.: Used in a manner in the Contributions & Conversations functionality, but not in as structured a way as the original
P.S.: Text Placeholders - developed further to many workshop-specific contexts
P.S.: A pattern we’d call a 1:N Table Structure - despite our best efforts, we couldn’t get to give us a usable presentation of the Item table data. Different views and layouts just weren’t working. Instead we created a new Table with Building Blocks (the 1:) as the display column and multi-select lookups (the :N) of the Items table creating the accumulation we needed.
P.S.: We also used a simple ThisRow() , without any .Item lookup on the Items table, as a sort of Recursive Lookup to create a nice-looking
chip
representation of the Item itself (a text column) for use in the Workspace canvasses

Sketch out your doc’s basic design.

Version 1 (2nd August 2022) looked like this and shows interface layouts, buttons, displays and data structures all mixed up. However, it serves well as a starting point for a database design discussion. ​P.S.: And it didn’t change much at all during implementation 🤩 ​
msg-1036764929-3254.jpg
The data structures as implemented look like this:
Workshop Cheats Data Model - Frame 1.jpg

Are any special controls needed?

It is envisaged that a set of Controls and Automations will link the two functional blocks.
Buttons within the Moderation Checklist could restrict access/ display/ functionality of the Workspaces in line with workshop progress ​P.S.: This idea wasn’t further developed or implemented
Specifically, the voting and content promotion functionality should be under the moderator’s control ​P.S.: Done
Moderator controls should manage data additions and cleansing, including the (re-)population of the (mirrored) Canvas data on the user side [subject to the rules of play] ​P.S.: Done - very successfully
P.S.: In addition, quite complex control synchronisation was implemented to allow the moderator to control the data seen by all participants - and then to allow the participants to override the moderator’s choice with individual selections

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.