Templates could hold the following information to be complete:
Template title
Template description
Template tags
Template image (optional)
Post/Whiteboard/Callout/Innoflow title
Post/Whiteboard/Callout/Innoflow description
Post/Whiteboard/Callout/Innoflow tags
Post/Whiteboard/Callout/Innoflow image (optional)
Whiteboard: whiteboard template
Innovation flow: innoflow states/order
Call for posts: default post description
Call for posts: default post tags
Call for posts: default post title (but we wouldnt want this probably, maybe a prefix..)
Call for whiteboards: whiteboard template
This translates to a lot of input fields when creating a template. We're thus not showing them all at the moment, but this is causing confusion, for example when creating templates: what description is this, for the template or the callout? and when using templates: why isn't this description copied over?
Initiative / goal
A clear and consistent way of dealing with templates and all the related information
Hypothesis
Fixing this will result in less confusion and frustration for mainly admins who are setting up spaces and challenges, and for the people creating the templates. Also, the templates will be more consistent with the descriptions always being of the same 'type' of description: not template descriptions mixed with callout descriptions on the template cards.
Description
Templates could hold the following information to be complete:
This translates to a lot of input fields when creating a template. We're thus not showing them all at the moment, but this is causing confusion, for example when creating templates: what description is this, for the template or the callout? and when using templates: why isn't this description copied over?
Initiative / goal
A clear and consistent way of dealing with templates and all the related information
Hypothesis
Fixing this will result in less confusion and frustration for mainly admins who are setting up spaces and challenges, and for the people creating the templates. Also, the templates will be more consistent with the descriptions always being of the same 'type' of description: not template descriptions mixed with callout descriptions on the template cards.
Acceptance criteria and must have scope
Stakeholders
Prod/dev/CS
Design
https://stichtingcherrytwist.sharepoint.com/sites/Product/_layouts/15/Doc.aspx?sourcedoc={b0ef1446-f6ac-404c-a33c-71472536494c}&action=edit&wd=target%285.%20Platform%20Content%20and%20Information.one%7Ca745a153-ea3f-4b6e-8f16-9163bfe64932%2FTemplates%7C732f246a-87ed-4759-9823-7cf563a97fc0%2F%29&wdorigin=703
Atoms
Post templates:
Whiteboard templates:
Innovation flow templates:
Molecules
Callout templates:
Member Guidelines Templates:
Template:
Blueprint:
Application Form Templates:
Template:
Blueprint:
Organisms
Collaboration templates:
Community templates