@gusfrases presented #SP24S067 Office 365 Public Websites The Good The Bad
the Ugly #SP24 Online conference. The ugliest part was the most attractive one.
In that part he showed the challenges and issues around branding of a SPOnline public facing site.
Here are the most prominent challenges and issues:
Mobile
No customizable device channels
Anonymous users issues
- Can't use search refiners
- No REST API (What Every Developer Needs to Know About SharePoint Apps, CSOM, and Anonymous Publishing Sites)
Workaround:
Sandbox solution
JSlink (and yes, you can do a multiple JSLinks ListView Web Part issues with JSLink and Display Templates – A solution?)
- No cache
Not a real workaround for cache issue:
CDN for jQueryClient -side options for caching
Lazy load;
Content optimization
>> Takeaway>> NO for a Search-driven application on SPOnline public anonymous sites
Site management issue
No UI for Site columns, content types, search schema and creation of the subsite
Some default site templates are not available
Workaround:
Some features are accessible through direct links, some via SPD.
User Code Service not reliable in O365
Instead of Sandbox solution, consider JSLink when possible
>>Takeaway>> Why and why not to use SPonline for public facing sites?
*Search = OOTB Search
Resources:
Blog by Gus FrasesSPOnline Public Site with search which is possible built by Gus Frases
No comments:
Post a Comment