Home » browser based process development » sharepoint » The SharePoint 2013 Development and Office App Models Promise Expanded Roles for SharePoint Site Designers

The SharePoint 2013 Development and Office App Models Promise Expanded Roles for SharePoint Site Designers

SharePoint Users with successful experience branding sites with HTML, JavaScript and Cascading Style Sheets (CSS), can now look forward to a new role, with, arguably, an expanded importance within their communities. The new SharePoint Development, and Office App Models are both built, in entirety, on these skills.

SharePoint-Videos offers a very rich set of video tutorial content on these new development models. Yaroslav Pentsarskyy, a SharePoint MVP, acknowledged subject matter expert on SharePoint branding, and a published author led our first online course on this topic, SharePoint 2013: Development. Yaroslav also led an online course for us on SharePoint 2013, Branding. He also authored our video tutorial set on branding SharePoint 2010 sites.

Our second online course on these topics, SharePoint 2013: JavaScript and jQuery. Our instructor for this course, Marc D. Anderson, is, once again, a SharePoint MVP and a published author on related topics. He is also the author of the jQuery Library for SharePoint Web Services.

Finally, we offer a video tutorial set composed from recordings of an online course led by Steve Fox, Director of Services for Microsoft®. The title of this course is SharePoint 2013: Beginning Development.

Perhaps it will be helpful to offer a likely explanation of why we opted to present so much technical training information on the SharePoint 2013 Development model. The model is, in fact, a radical departure from its predecessors. Speaking for myself, I like the new development model. I’m very interested in SharePoint security. The new SharePoint 2013 Development model, at least on paper, appears to offer a much more secure approach to how best to satisfy organization-specific requirements for custom applications. Earlier development models required these organizations to produce “trusted solutions”, which consumed server cycles as farm solutions. With the SharePoint 2013 development model, there is little incentive for custom application stakeholders to plan on building “trusted solutions”. The applications built with the new model run, in entirety, on the client side, making no direct demands on the server, whatsoever. The added benefit is a more secure serving environment, which is now insulated from any problems arising from these custom, client-side solutions.

Please contact us for further information.

Comments are closed.