Requirements for Sharing File Assets

[dmolsen]

This issue is related to #126 but is only focused on sharing file assets. We still need to figure out how to address pages.

The first feature that needs to be created is a way to organize sites into collections of related sites. In the past we have called this feature "superspaces." I figure we'll continue to use this term.

• [ ] a UI to create/edit/delete superspaces. The only direct property of a superspace is a name that can be used throughout the UI.
• [ ] a UI to add/remove users that can manage a superspace
• [ ] a UI to add/remove sites that are related to the superspace. A site can be related to more than one superspace.

These are the requirements for sharing file assets from the "Files" section. Assets marked as "shared" are shared with all superspaces that a site is related too. There will be no granularity to the sharing:

• [ ] file assets get marked with a "shared" flag via the "edit" screen
• [ ] file assets get marked with a "shared" flag via a "share" link that comes up with the other links during hover on an element
• [ ] file assets get marked with a "shared" flag via the "select item via checkbox" feature. i don't think there needs to be a modal though.

These are the requirements for choosing images or other media that are shared:

• [ ] when building the collection that's available to pull from in the snippet editor the query should include all files shared in the superspaces that the site is related to.
• [ ] edit and replace links should be removed for shared assets not from the current site in the editor
• [ ] the filter options should include a "source" section with "current site" or "shared" as checkbox options. both should be checked by default.
• [ ] i'd like to see some element that can mark that the item is a "shared" one but short of adding text or image after the name i'm not sure what would fit. @adamjohnson do you have any ideas?

I think this is fairly straightforward. Let me know if you have questions.

[dmolsen]

Per @zeroedin... instead of calling it super spaces it should be called Site Groups in the UI. I forgot to say how to get to it. I'm assuming it can be linked from the "System" menu but I'm not sure how that works for non-admins.

[adamjohnson]

In hoping to learn from others' experiences, here's a writeup about how Concrete5 implemented reusable content, realized their implementation was lackluster, and rebuilt it to be better years later:

http://www.concrete5.org/documentation/how-tos/developers/concrete5-5.5-stacks-vs.-scrapbooks/

There's also this video which demonstrates how Stacks integrate into their UI.

[dmolsen]

This seems different than the problem we're looking to solve. I think the video/concept is helpful when looking at how we share content regions but not as helpful for pure file sharing.

On May 5, 2015, at 5:04 PM, Adam Johnson notifications@github.com wrote:

In hoping to learn from others' experiences, here's a writeup about how Concrete5 implemented this, realized their implementation was lackluster, and rebuilt it to be better years later:

http://www.concrete5.org/documentation/how-tos/developers/concrete5-5.5-stacks-vs.-scrapbooks/

There's also this video which demonstrates how Stacks integrate into their UI.

— Reply to this email directly or view it on GitHub.