@SPC_ORG SP2013 Search by @bniaulin

Continuous crawl:
 - only works on SP Content sources;
 - by default every 15 min;

Use continuous crawl diligently, only on the content source that they need it.

NO XSLT, use html, css, js

SP2013 SP1 has ability to turn the Optimistic overwrite for title - MetadataExtractorTitle

2 web parts for Search:
SearchResult web part - you have to have a custom display template
Content Search web part - you can re-map the properties

2 types of templates:
1. Control (a container for item display template)
2. Item Display

! Don't touch automatically created js file out from content template

Result types helps to vary item templates based on the rule (conditions)

Resources:
http://tympanus.net/codrops/

@SPC_ORG Go mobile with responsive design by @kyleschaeffer

1. Why Mobile
30% audience are on mobile already for a general content

2. What is responsive design
Future-friendly approach to handle different screen resolution.
The inventor of the term - Ethan Marcotte

3. How does it work?
HTML+CSS+JavaScript
Flexibility & Adaptation

• Stop using fixed width, use %;
• CSS Media query

@media screen and (max-width:800px) {} - basically, a rule when to use this CSS in {}


"Mobile first" is better since the client won't need to download extra artifacts

4. How SharePoint do it?
 this is a tricky question. It takes more effort.
We don't have full control on SP OTB html and css.

Much easier if you start with your own master page.

• Disable "Mobile browser view"
• Activate SP server publishing

(team site don't have master pages, you have to activate the publishing feature, and you need to create a new page for layouts)
Use only Publishing template!

When you create a mobile portal - keep only: publishing site template, custom master page and layouts

• Create responsive templates:
• Master pages
• Page layouts
• Item styles
• Display templates (2013)
• Create responsive content

ListView is still a problem to make it responsible

A kind of workaround: Put a div wrapper.

Resources:

http://spblueprint.codeplex.com/  - a blank blunt template for Sp2013 OTTB Responsive
http://responsivesharepoint.codeplex.com/

@SPC_ORG @DougHemminger on #SharePointApp development

No more authohosted app!
MS announced that the Office 365 Autohosted Apps Preview program will end on June 30, 2014.
So now we have 2 left: SharePoint-hosted, provider-hosted.

App model to solve security issues of full trust solutions.

When to use the App Model
 -SPOnline
 -Strong JavaScript\Client side developers

a nice thing to know: Office dev center has Showcase: Contoso incubation search app

Other recommended read: 

Apps for SharePoint compared with SharePoint solutions

Note:
On Anonymous access for App - How to: Create apps for SharePoint that can be used by anonymous users

@SPC_ORG @helloitsliam on SP2013 Authentication & Authorization

 Claims mentality: there is no user, there is an attribute by Liam Cleary

Authentication = Verification of Claim (login, pwd) - is not on SP
Authorization = Verification of Permission (access verification) - going on SP

Authentication precedes authorization (except anonymous access)

Often mistake: "Too often we focus on Authentication and not Authorization"

Authentication Claims
 - wide support;
 - WF-Trust 1.4
 - SAML Token 1.1 AuthN
 - It was developed for Sign On
 - Federation
Already many providers
-Microsoft standard approach
- before we needed to write custom code to authenticaion

Claim =
1. Identity (AD, Google, Windows Live) +
2. Claim (Attibutes of the Identity) +
3. Token (binary Representation of Idenity) +
4. Relying Party (aka RP) +
5. Secure Token Service (STS)

What is Claims Augmentation:

• Ability to intercept the incoming claims and transform to different outgoing claims
• Add additional attributes

Why to use Claims Augmentation: - retrieve user attributes to LOB

Authentication methods:

1. AD is a classical method authentication.

2. Membership and Role Providers - a custom mechanism for authentication

3. Custom Identity Provider.

Requires Trusted Certificate for communication

4. Azure Control Service (Azure Windows AD)

for O365 - ADFS Type cloud based service

Oauth - is a mechanism based on "Trust"

You trust the app, the app has permissions assigned.

So you can access data that you (as user) don't have access, but app has.

@SPC_ORG by @susanhanley on User Adoption. Observe, Listen and Communicate

A keynote on 5/19/2014 #SharePointConference.ORG - User Adoption

http://susanhanley.com/. Susan is local to me - she lives in Bethesda, MD.

Notes from the keynote.

The factors of Successful User Adoption:

1. WIIFM - what's in it for me.

Make you heard your stakeholders

2. The SP solution should be tight to critical company goal

3. Adoptable solution solves the problem

4. Give people voice

SP2013 features engage users:

 - likes, ratings in RIGHT context;

 - search; Create a Tip web part with tips and feedback. (Sue thinks it's crucial)

5. Engaging content

 - well written content for the web;

 - relevant for user.

6. Keep it simple

7. Start small. 

Turn out solution in 90 days

8.Roll out in gradual manner

9.Engage leaders

"No involvement by leaders, no commitment by employees. No exceptions"

A great tip: " To reduce attachments in the emails, set a rule in the leader's mailbox to reject attachments and ask to provide a link to the document"

10. Look for "early adopters"

11. Train to make people comfortable

Plan a training roadmap - for comfort.

Effective training - training suits people needs. Use different formats for different people.

12. COMMUNICATION

• be persistent
• get feedback whenever possible
• Think about how to communicate THE LAUNCH

The ideas on launch videos:

http://www.scoop.it/t/intranet-launch-videos-and-teasers

Dartmouth-Hitchcock Intranet Home Redesign

don't call SharePoint portal - SharePoint portal

Another idea:

30 minutes for 30 things that you didn't know about SP

"Get Sharp on SharePoint" - webcast

13. OBSERVE the users