Thanks to everyone that attended this morning's call! In case you missed it, we'll post the recording within the next 24h at
http://aka.ms/spdev-videos, but in the meantime, check out the above links for details on the updates - as well as the new samples posted to the GitHub repo.
To a few of the questions that we missed on the call:
- Site designs are currently only available for application to modern site templates (Group-connected team & communication sites). We are evaluating extending this to other templates and will share more as soon as we can.
- Content type support is limited to those included in the site template or defined using the new createContentType action. We are evaluating extending to support other content types (like those defined in a content type hub).
- Site script action limit: is currently limited to 30 (inclusive of sub-actions), but yes, we understand that as more actions become available for use in scripts this limit will need to be adjusted. We are looking at ways to do this in a performant way and keep web front end load to a minimum. Thanks for the feedback on this one!
- Thanks for the feedback re: "export & share/reuse" site script scenarios! We definitely have these in our roadmap and will share more details as soon as we can.
- Yes, we still need to enable (a) making a field defined using Field XML a site column and (b) providing option to reference it in a declarative content type action. This work is in plan.
- I'd love to hear more feedback/details on multi-lingual scenarios.
- You can use the isDefault clause to apply a site design to the base template (one per - team and comm); this would ensure that associated script gets applied when a site is created from non-SP entry points, like OWA and Teams. We are working w/ our product partners to provide ways to support other published designs. Note: we don't currently support hiding the default site templates, so we recommend using this approach to "customize the default".
- Yes, setting a theme was one of the first actions we built! Note that these are "company themes" - custom ones that must be first uploaded to your tenant gallery (check out this set of articles for more details: https://docs.microsoft.com/en-us/sharepoint/dev/declarative-customization/site-theming/sharepoint-site-theming-overview). Note: if you use the joinHub action in your site script, that associated site will inherit the hub site theme (so the applyTheme script action isn't necessary...and in fact, would be overwritten by the hub site association).
Microsoft
