Content Libraries

[toastercup]

We've mostly coalesced behind this idea as our main content distribution model. Content creators would be able to create a 'library' and publish content to it. This library would be able to be distributed outside of a tenant. Upon creation, a user would be able to generate a link that would enable sharing of that content, or specify an email/tenant admin to send a private link to. Upon clicking that link, a different tenant administrator would be able to add that library to their list of libraries for that tenant (or Org?). From there, they'd be able to distribute individual pieces of content or setup distribution rules to automatically make the content available as part of their tenant's feed. Upon applying distribution, this is when uniqueness checks would be performed, and uniqueness conflicts could be resolved.

In the longer term, we may want to consider even more distribution models - this one has its limitations. At that point, however, we would have to prove the use case before we made things more complicated with another way to distribute.

I'll be uploading a diagram sometime this quarter or next that digs into this idea a bit more.

Things to consider:

• Permissions. Upon distribution, who controls the library's settings? Is a copy of the library made, or is it a reference? Is there a thin layer ontop that merely controls the settings of the library rather than copies it entirely?
• After distribution, can the original library creator continue adding content?
• Can someone who picks up the library from a distributor add content to the library themselves? This may be akin to the 'view vs edit' setting you select when creating a public link in Google Drive
• Can the library be distributed outside of the hosted instance entirely? This may be very powerful for some users. Could use a webhook/pubsub/microservice pattern to implement something like this. Would we lose flexibility this way?
• Automatic distribution rules
• Uniqueness validations
• Relationship with tenants and organizations
• Use in API