SharePoint DevOps

https://github.com/SharePoint/sp-dev-docs/issues/417

http://blog.walisystemsinc.com/2017/02/pnp-powershell-overview.html

http://www.fabiangwilliams.com/2014/06/19/gotcha-on-sharepoint-designer-workflows-in-app-step/ http://www.advaiya.com/blog/sharepoint-list-workflow-create-or-update-list-item-on-another-sharepoint-site-list http://blog.portiva.nl/2016/11/03/sharepoint-designer-call-http-web-service-to-create-item-in-other-site-collection/

Go to SharePoint designer and open the site ->Your List->Your View Find all FieldRef in <ViewFields> tag. Then add below attributes to desire FieldRef like this code <FieldRef Name="DateColumn" ListItemMenu="TRUE" linkToItem="TRUE"/>' If you want to remove existing ECB menu then remove the following code and save it. <FieldRef Name="LinkTitle"/> 

The search architecture of Sharepoint 2016 contains search components and databases  that work cohesively to perform the search operation. .   The size and  structure of the search architecture depends on the volume of your content, availability, estimated amount of page views, fault tolerance and queries per second etc. Architecture can vary depending on the composition of the data that is crawled. The search architecture can be for the enterprise or for Internet sites. Sharepoint Search components In SharePoint Server 2016, search components are not hosted on Web servers.  All components reside on application servers and all databases reside on database servers except    query processing component and index components . The query processing component and index components reside on the Web  servers to make maximum use of the available hardware resources and to simplify scaling out the search topology. We'll talk about these. There are several ...

The SharePoint Patterns and Practices JavaScript Core Library was created to help developers by simplifying common operations within SharePoint and the SharePoint Framework. This is open source, community driven library with contributions cross different organizations and teams. Currently it contains a fluent API for working with the full SharePoint REST API as well as utility and helper functions. This takes the guess work out of creating REST requests, letting developers focus on the what and less on the how. PnP JS Core library can be used in SharePoint Online or in on-premises. It's a great library to be used with SharePoint Framework customizations, but it can be also used using classic development models, like with Script Editor Web Part or when you embed JavaScript to SharePoint using User Custom Actions. https://dev.office.com/blogs/sharepoint-pnp-javascript-core-library-v20

http://sharepoint.stackexchange.com/questions/50232/difference-beween-wiki-page-application-page-web-part-page-and-publishing-page