Creating Public Facing Websites with SharePoint 2013
•Download as PPTX, PDF•
0 likes•2,071 views
Considerations and Architecture Options for Public Websites
Recommended
Recommended
More Related Content
Similar to Creating Public Facing Websites with SharePoint 2013
Similar to Creating Public Facing Websites with SharePoint 2013 (20)
More from Perficient, Inc.
More from Perficient, Inc. (20)
Recently uploaded
Recently uploaded (20)
Creating Public Facing Websites with SharePoint 2013
- 1. Public Websites Considerations and Architecture Options
- 2. Overview • Broad categories – Design – Content – Navigation – Search 10/11/2013 2
- 3. Design • Responsive – Pros – Cons • Device Channels – Pros – Cons • Hybrid – Pros – Cons 10/11/2013 3
- 4. Content • Publishing Pages – Page Layouts – Individual pages • Catalogs – List based catalogs – Variations • Search based – Surface content using search and display templates. 10/11/2013 4
- 5. Navigation • Manually configured • Managed Metadata based 10/11/2013 5
- 6. Search • Define search experience for the users – Design display templates – Understand content • Define Query Rules – Define ranking – Promote results 10/11/2013 6
- 7. Tips • Search Results Web Part – Trim Duplicates • Ranking – Rank cannot be based on queried values. • E.g. Boost if Page Field x contains “Queried value” • Design – Responsive can get expensive based on how pixel perfect you need the design to be. – Device channels need customizations to support web parts zones. • Navigation – Catalog based navigation has some issues when there are multiple zones. 10/11/2013 7
Editor's Notes
- Responsive Pros Content authoring easy. Most of the devices are covered $$ Cons Pain to make it pixel perfect New device sizes and resolutions can throw off the design. Device Channels Pros Can target specific devices (rather, user agents) Provider different user experiences to users depending on what device they use. Cons $$ (It depends) Authoring experience can vary. Content duplication. Hybrid Pros Best of both worlds. Not all pages need to have device specific content. Cons Initial investment might be higher.
- Managed Metadata based navigation:Catalogs based navigation can be very powerful. But it can quickly get tricky.Primer on catalogs based navigation.Define a listDefine a column which drives navigation.Custom Control to render the menuNested menu items.Term properties