Latest Music :
Showing posts with label Tips and Tricks. Show all posts
Showing posts with label Tips and Tricks. Show all posts

Flirchi,Sosial Media Perkenalan Yang Asyik Buat Cari Pacar

Flirchi,Sosial Media Perkenalan Yang Asyik Buat Cari Pacar

Oke, daripada lama menunggu, mending langsung saja kita menuju topik pembahasan, nah teman saya punya situs media sosial keren baru saya dapat tadi dari penayangan iklan google Adsense di blog ini, apa itu ? namanya Flirchi, situs ini adalah sebuah jejaring sosial untuk berkenalan dengan semua orang di dunia maya tanpa harus menambahkan teman ke kontak anda, karena otomatis kita akan langsung di chat oleh pengguna flirchi.

Kelebihan lainnya adalah pada saat kita login, semua pengguna flirchi akan melihat kita dalam keadaan online. keren kan, nah bagi anda yang sedang jomblo jangan ditunda lagi secepatnya login ke situs flirchi. Selain Gratis, situs ini juga cukup populer di dunia maya, anda bisa berkomunikasi dengan semua orang di seluruh dunia.

Adapun jika anda belum tau cara menggunakan situs ini, anda dapat mengikuti langkah-langkah singkat di bawah ini:

1. Masuk ke alamat : www.Flirchi.com

2. Pada halaman situs, arahkan kursor anda ke login situs, lalu klik tombol "Login dengan Facebook" 

lihat gambar di bawah !

Demikianlah posting singkat tentang situs populer gratis untuk cari pacar, semoga bermanfaat. terima kasih telah berkunjung ke blog sederhana ini.

Cara Merubah Tampilan Baru Twitter!




Coba sekarang anda masuk ke akun twitter anda, maka anda akan melihat beberapa akun teman anda Tampilan akun twitternya sudah berubah.

Sepertinya saat ini pihak Twitter barusaja mengenalkan tampilan barunya. Tampilan twitternya jika kita lihat sepintas hampir menyerupai akun facebook.

Bagaimana cara merubah tampilan baru Twitter?

Daripada anda penasaran, berikut ini panduan merubah tampilan baru twitter anda.

Biasanya begitu anda baru login kemudian anda buka akun anda, maka akan muncul tampilan seperti gambar dibawah ini:



Jika anda sudah melihat tampilan seperti gambar diatas, itu artinya pihak twitter ingin mengenalkan dan menanyakan kepada anda apakah ingin mencoba tampilan baru twitter?

Jika memang anda menyukai dengan tampilan abru teitter tersebut, silahkan anda tinggal klik NYALAKAN. Dalam tulisan ini menggunakan bahasa Indonesia, jika anda menggunakan bahasa Inggris atau yang lainya, silahkan tinggal sesuaikan.

Jika anda sudah klik Nyalakan, maka otomatis akun twitter anda sudah berubah menggunakan tampilan baru twitter.

Karena dalam tampilan baru twitter ini hampir menyerupai akun di facebook, maka anda bisa memasang foto anda dengan ukuran 1500×500 pixel dengan cara klik edit profil kemudian anda upload foto anda tersebut.

Caranya cukup mudah bukan!

Selamat menikmati tampilan baru twitter anda.!

Perbedaan Produk Resmi, Grey Market, Black Market & Palsu

http://images.detik.com/content/2014/01/20/1279/camera.jpgIlustrasi (gettyimages)
Biasanya, produk seperti kamera, lensa, aksesoris dijual oleh importir berlisensi, yang biasanya disebut distributor resmi, kemudian diedarkan melalui distribusi ke dealer/penjual eceran.

Produk dari grey market pasar abu-abu) tidak melalui jalan distribusi seperti ini, tapi melalui jalan lain, misalnya mengimpor langsung dari penjual atau pabrik yang berlokasi di luar negeri.

Kualitas produknya biasanya sama. Hanya saja, mungkin ada beberapa perbedaan seperti aksesoris, bahasa, kelengkapan. Ada yang nama produknya berbeda, misalnya di Jepang, Canon 650D dinamai KISS X7i, di Amerika namanya Rebel T5i.

Yang paling penting bagi pembeli adalah pelayanan purna jual seperti garansi. Biaya servis jika kamera rusak menjadi lebih mahal dan lambat daripada produk yang dijual secara resmi. Dalam beberapa kasus, pusat servis resmi dapat menolak untuk melakukan pelayanan terhadap produk yang dibeli dari grey market.

Produk grey market, bukan barang palsu. Perbedaannya, produk palsu memiliki komponen elektronik yang berbeda di dalamnya yang kualitasnya lebih rendah, sehingga cepat rusak atau kinerjanya lebih rendah daripada produk asli. Berhati-hatilah dan jangan tergiur dengan harga barang palsu yang terlalu rendah dan tidak masuk akal.

Ada satu istilah lagi yaitu produk black market (pasar gelap), biasanya ini mengacu pada produk yang diperoleh dengan cara yang tidak legal, misalnya barang selundupan atau pencurian.

Yang merupakan daya tarik terbesar produk dari grey market adalah harganya yang lebih murah yaitu sekitar 10%-30%. Produk yang dibeli melalui jalur seperti ini cenderung lebih murah karena tidak melalui jalur distribusi bertingkat (dimana setiap tingkatnya pedagang mengambil keuntungan). Harga produk resmi menjadi lebih tinggi juga karena adanya biaya operasi, iklan, tenaga kerja, sewa, dan sebagainya.

Selain itu, distributor di negara lain memiliki kebijakan harga produk yang berbeda-beda. Misalnya di Amerika Serikat dan Jepang sering ada promosi harga besar-besaran setiap musim tertentu, atau saat melakukan cuci gudang produk lama setelah produk baru dirilis. 

Menjual produk dengan jalur impor langsung merupakan hal yang lumrah dan cukup banyak dilakukan oleh penjual dan toko kamera. Ada beberapa alasan yang membuat mereka menjual dengan jalur ini. Misalnya distributor resmi tidak memenuhi permintaan produk, ataupun ingin meraih keuntungan dalam persaingan harga dengan toko-toko yang ada. 

Sebenarnya bukan menjadi masalah kalau toko menjual dengan jalur ini, asal toko jujur kepada pembeli tentang garansi dan asal produk tersebut. Masalahnya, seringkali ada penjual yang tidak jujur, misalnya mengaku bahwa produk tersebut bergaransi resmi, padahal kartu garansinya tiruan. Setelah di periksa serial nomornya, ternyata produk tersebut tidak terdaftar. 

Jika membeli produk dari grey market, biasanya tidak ada garansinya, atau waktu berlakunya bervariasi, dari 1 bulan ke 1 tahun. Jika produknya rusak, biasanya dikembalikan ke toko dan toko akan mencoba memperbaikinya. 

Jika penjualan toko tersebut cukup besar, biasanya toko memiliki teknisi khusus. Jika tidak, toko akan mengurusnya ke tempat servis lainnya, termasuk tempat servis resmi.


Yuk, belajar fotografi, editing dan ikut tur fotografi dengan infofotografi.com

Inconvenient Anonymous Search Results Cache and User Segments In SharePoint 2013

Anonymous Search Results Cache is a great way of optimizing the performance of your public-facing website that uses search-driven publishing. Unfortunately things look a little less optimistic when combined with User Segments.

Anonymous Search Results Cache in SharePoint 2013

In my recent post on Anonymous Search Results Cache I discussed how it can help you improve the performance of your public-facing website. By storing the results of search queries issued by anonymous users in cache, you can lower the load on your environment and handle more requests and handle them quicker.
Although Anonymous Search Results Cache is enabled for the Content Search Web Part (CSWP) by default since March PU, if you have a website built before that, you will need to enable it manually. While the approach recommended by Microsoft is to remove and re-add all instances of CSWP, you can enable Anonymous Search Results Cache on your existing Web Parts using a few simple steps I showed you in my previous article.

Personalizing search-driven content with User Segments

One of the great improvements in SharePoint 2013 is the ability of displaying personalized content using the Content Search Web Part. By passing User Segments to the search query, you can tailor the results to the particular visitor showing her more relevant content and increase the chance for conversion.
Assuming you have gathered User Segments, that describe the current visitor, passing them to SharePoint 2013 Search for personalizing content is pretty straight-forward, although it differs slightly depending on whether you’re using Client-Side or Server-Side Rendering.
If you’re using Client-Side Rendering, which is the default option in SharePoint 2013, following is how you would pass User Segments to the query of the Content Search Web Part:
?
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
public class TargetedContentSearch : ContentBySearchWebPart {
    protected override void OnLoad(EventArgs e) {
        if (this.AppManager != null) {
            if (this.AppManager.QueryGroups.ContainsKey(this.QueryGroupName) &&
                this.AppManager.QueryGroups[this.QueryGroupName].DataProvider != null) {
                this.AppManager.QueryGroups[this.QueryGroupName].DataProvider.BeforeSerializeToClient +=
                    new BeforeSerializeToClientEventHandler(AddUserSegments);
            }
        }
        base.OnLoad(e);
    }
    private void AddUserSegments(object sender, BeforeSerializeToClientEventArgs e) {
        DataProviderScriptWebPart dataProvider = sender as DataProviderScriptWebPart;
        if (dataProvider != null) {
            string[] userSegments = null;
            // your logic here for retrieving user segments for the current user
            dataProvider.Properties["UserSegmentTerms"] = userSegments;
        }
    }
}
When using XSLT-based rendering passing user segments into the query looks slightly different:
?
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
public class TargetedContentSearch : ContentBySearchWebPart {
    protected override void OnLoad(EventArgs e) {
        if (UseSharedDataProvider == false &&
            AppManager != null &&
            AppManager.QueryGroups.ContainsKey(QueryGroupName) &&
            AppManager.QueryGroups[QueryGroupName].DataProvider != null) {
            string[] userSegments = null;
            // your logic here for retrieving user segments for the current user
            AppManager.QueryGroups[QueryGroupName].DataProvider.Properties["UserSegmentTerms"] = userSegments;
        }
        base.OnLoad(e);
    }
}
In both cases User Segments must be passed as an array of string (string[]) where each value corresponds to an ID of a User Segment Term associated with Query Rules.

Inconvenient Anonymous Search Results Cache and User Segments

Although Anonymous Search Results Cache and User Segments work just fine on their own, as soon as you try to enable Anonymous Search Results Cache on a Content Search Web Part that uses User Segments you will get the following exception:
Specified method is not supported.
[NotSupportedException: Specified method is not supported.]
Microsoft.Office.Server.Search.Query.SearchCacheKeyGenerator.SerializeObject(Object value, StringBuilder& sb) +319
Microsoft.Office.Server.Search.Query.SearchCacheKeyGenerator.DeltaSerialize(IPropertyCollection propColl) +677
Microsoft.Office.Server.Search.Query.SearchCacheKeyGenerator.GetKey(QueryProperties queryProperties, String queryPrefix) +45
Microsoft.Office.Server.Search.Query.SearchResultsCacheWrapper.Get() +197
Microsoft.Office.Server.Search.Query.Query.ExecuteQuery() +582
…
Not Supported Exception when trying to use Anonymous Search Results Cache with Content Search Web Part that uses User Segments
Looking further, you will find out that the logic responsible for building the cache key for the query results doesn’t support string[] types for serializing values. Instead it supports StringCollection(System.Collections.Specialized.StringCollection) for values that contain multiple strings. Unfortunately, if you try to pass user segments as a StringCollection instead you will get another exception:
Type {0} is not valid. Only String, Int32, Boolean and String[] are supported.
Parameter name: System.Collections.Specialized.StringCollection
[ArgumentException: Type {0} is not valid. Only String, Int32, Boolean and String[] are supported.
Parameter name: System.Collections.Specialized.StringCollection]
Microsoft.Office.Server.Search.Query.QueryUtility.Create(String name, Object val) +460
Microsoft.Office.Server.Search.WebControls.ScriptApplicationManager.PrepareQueryForExecution(QueryGroup qg, Int32 lang) +2413
Microsoft.Office.Server.Search.WebControls.ScriptApplicationManager.GetSyncResult(String queryGroupName) +717
Microsoft.Office.Server.Search.WebControls.ContentBySearchWebPart.GetSingleResultRows() +122
…
Argument Exception when trying to pass user segments as String Collection instead of an array of string
This time it’s the process responsible for building the search query failing due to its lack of support for StringCollection-based properties.
As it’s impossible to create an object that would be of type string[] and StringCollection at the same time as well as to plug into the query creation and caching process to change the type of the object that contains User Segments it seems that at this moment it is not possible to use Anonymous Search Results Cache with User Segments.
Although the fix seems relatively easy, it may have impact on the underlying logic of SharePoint 2013 Search, so it’s hard to say how easy it is for Microsoft to fix this issue. One thing that we can hope for is, that this will be fixed in the future releases of SharePoint and that we will be able to optimize our public-facing websites for performance while leveraging the content personalization capabilities of search-driven publishing.

Summary

Anonymous Search Results Cache is a great way of optimizing public-facing websites that use search-driven publishing for performance. Unfortunately, at this moment, it cannot be used with Content Search Web Parts that use User Segments.

Overview Of Facebook Social Plugins And How They Can Help You Integrate Social In Your SharePoint 2013 Website

Facebook offers a number of standard plugins that you can use to integrate with Facebook on your website. The overview of all available plugins is published at https://developers.facebook.com/docs/plugins/. Following is an overview of some of the plugins and how you can integrate them with your website.

Before you start: Insights

When integrating with Facebook, you can add one or more widgets to your website. Although this will allow your visitors to interact with your website using Facebook plugins, it will provide you with very little feedback about how your visitors leverage the social media capabilities that you have provided them with. The great news is that if you want to get more information about the usage of Facebook social plugins on your website, you can benefit from the Insights capability that Facebook offers you. After registering your website as a Facebook app and including the app ID in your website, you will get access to analytics information regarding the usage of Facebook on your website from all the widgets.
More information about Facebook Insights is available at https://developers.facebook.com/docs/insights/

Like Button

The Facebook Like button is probably the most popular Facebook social plugin. With a single mouse click your visitors can let their friends know that they like a page on your website. As a result your page and even your whole website might get some extra attention.
Although you might want to include the Like Button on every page on your web page, it might be most effective on detail pages that contain the essential content your visitors are looking for. Integrating the Facebook Like Button on your website is easy and comes down to including two HTML snippets in your websites.
First there is the Facebook SDK call that should be included once per page directly after the body tag:
 <div id=”fb-root”></div>
<script>(function(d, s, id) {
  var js, fjs = d.getElementsByTagName(s)[0];
  if (d.getElementById(id)) return;
  js = d.createElement(s); js.id = id;
  js.src = “//connect.facebook.net/en_US/all.js#xfbml=1″;
  fjs.parentNode.insertBefore(js, fjs);
}(document, ‘script’, ‘facebook-jssdk’));</script>
If you have registered your website as a Facebook app, you should include your app ID (underlined) in this snippit:
<div id=”fb-root”></div>
<script>(function(d, s, id) {
  var js, fjs = d.getElementsByTagName(s)[0];
  if (d.getElementById(id)) return;
  js = d.createElement(s); js.id = id;
  js.src = “//connect.facebook.net/en_US/all.js#xfbml=1&appId=0123456789“;
  fjs.parentNode.insertBefore(js, fjs);
}(document, ‘script’, ‘facebook-jssdk’));</script>
Because this HTML snippet is shared between all pages on your website, the way to include it in your SharePoint website is to make it a part of your Master Page, as shown in figure 1.
Figure 1. Code snippet Master Page with Facebook code included
Figure 1. Code snippet Master Page with Facebook code included
The second code snippet that you have to include is the Like Button itself:
<div class=”fb-like” data-href=”http://www.contoso.com&#8221; data-send=”true” data-width=”450″ data-show-faces=”true”></div>
Because the placement of the Like Button might vary per page, the best way to integrate it on your website is to include it in the Page Layout.
According to the Like Button guidelines, the Like Button has to contain the absolute URL of the page on which it is integrated. In the code sample above the absolute URL is included in the data-href attribute. Because we want to place the code on the Page Layout we don’t want to include a fixed URL. Instead we want to inject the URL of the current page rendered using the
Page Layout. Considering that SharePoint 2013 offers support for physical as well as Friendly URLs, the best way to get the URL of the current page is to use the SharePoint 2013 Canonical URL control. Combined with the Like Button HTML code snippet, it would look as follows:
<!–SPM:<%@Register Tagprefix=”Contoso” Namespace=”Contoso.SharePoint.Seo.Controls” Assembly=”Contoso.SharePoint.Seo, Version=1.0.0.0, Culture=neutral, PublicKeyToken=a285ef6967f781d3″%>–>
<!–MS:<Contoso:HyperlinkControlWrapper runat=”server”>–>
<Control>
 <control type=”Microsoft.SharePoint.Publishing.WebControls.SeoCanonicalLink” assembly=”Microsoft.SharePoint.Publishing, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c” />
</Control>
<ContentTemplate>
 <div class=”fb-like” data-href=”$Url$” data-send=”true” data-width=”450″ data-show-faces=”true”></div>
</ContentTemplate>
<!–ME:</Contoso:HyperlinkControlWrapper>–>
Figure 2. Facebook Like button
Figure 2. Facebook Like button
When building the Like Button social plugin an interesting option worth considering is including the Send option.
Although designed using a very simple idea, integrating the Like Button on your website can help you expand the reach of your content. An additional benefit that you get from using the Like Button on your website is that  combined with the SharePoint 2013 Search Analytics capabilities, you can leverage the event of someone liking a web page on your website. With this information you can for example present content that has been liked on a prominent place on your website, which again increasing your chances for conversion.

Send Button

When building the Like Button social plugin an interesting option worth considering is including the Send option. While clicking the Like option allows your visitors to share your web page with everyone, they can use the Send button to choose with whom they want to share your web page. This offers them more flexibility and lowers the bar for sharing the contents of your website even further.
Figure 3. Facebook Send button
Figure 3. Facebook Send button

Comments

Publishing original content is a great way for gaining popularity and improving the ranking of your website in search engines. Furthermore, allowing your visitors to provide you with feedback, can help you improve your website to be even more user-friendly and become better tailored to your audience’s interests. Facebook offers the Comments plugin that you can integrate with your website to allow your visitors to comment on your website.
Figure 4. Facebook Comments
Figure 4. Facebook Comments
Giving your visitors the ability to use Facebook to comment on your content, can be of great benefit both to you and your visitors. Although it might depend on the audience of your website, many people have a Facebook account nowadays. It is easier for them to use their existing Facebook profile to leave a comment on your website rather than following yet another registration process.
Another benefit of using Facebook for comments is that whenever someone comments on your content, that comment will be shared with their friends. Theoretically this allows you to expand your reach even further. However, keep in mind that if the comment isn’t flattering everyone will know it as well.
The process for integrating the Facebook Comments plugin is very similar to integrating the Facebook Like Button. In most scenarios you want the Facebook Comment plugin to appear beneath the content of every page. To do this, you can include it in the content of each Page Layout used within your website.
Similarly to the Facebook Like button, the Comments plugins consists of two code snippets. The first one is exactly the same as for the Facebook Like button, so if you plan to integrate both plugins, you only have to include it once.
The second snippet is the Comments plugin itself. It should be placed where you want it to be displayed in your Page Layout:
<div class=”fb-comments” data-href=”http://www.contoso.com&#8221; data-width=”470″ data-num-posts=”10″></div>
Similarly to the Facebook Like button, the data-href attribute should contain the absolute URL of the page for which you want to provide the commenting capability. As this is very likely to be the current page, you could once again benefit of the SeoCanonicalLink control to retrieve the URL of the current page:
<!–SPM:<%@Register Tagprefix=”Contoso” Namespace=”Contoso.SharePoint.Seo.Controls” Assembly=”Contoso.SharePoint.Seo, Version=1.0.0.0, Culture=neutral, PublicKeyToken=a285ef6967f781d3″%>–>
<!–MS:<Contoso:HyperlinkControlWrapper runat=”server”>–>
<Control>
 <control type=”Microsoft.SharePoint.Publishing.WebControls.SeoCanonicalLink” assembly=”Microsoft.SharePoint.Publishing, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c” />
</Control>
<ContentTemplate>
 <div class=”fb-comments” data-href=”$Url$” data-width=”470″ data-num-posts=”10″></div>
</ContentTemplate>
<!–ME:</Contoso:HyperlinkControlWrapper>–>

Activity Feed

Another interesting plugin that Facebook offers for integrating its capabilities on public-facing websites is the Activity Feed plugin.
The Activity Feed plugin shows the recent activity on your website. Whenever someone likes a page within your website, the Activity Feed plugin is used to display the Like in the Activity Feed. Other custom actions custom can also be recorded, stored and presented in the Activity Feed.
Using the Activity Plugin can help your visitors discover new content and with that help you expand the reach of your website. When your visitors are logged in with Facebook, the Activity Feed will show activities that your visitors’ friends have made. As in most situations those are all people that your visitors know and trust. Therefore, the odds are high that they will follow their recommendations and discover new content on your website. If they are not logged in on the other hand, the Activity Feed plugin will show recommendations from across your site and of course suggest logging in to Facebook to show more relevant content.
As with other Facebook plugins, the Activity Feed plugin consists of two HTML snippets required to integrate it with the website. The first one is the Facebook JavaScript SDK snippet that we have seen previously. The second one is the Activity Feed itself:
<div class=”fb-activity” data-site=”contoso.com” data-width=”300″ data-height=”300″ data-header=”true” data-recommendations=”false”></div>
The configuration of the Activity Feed is straight-forward. Using the data-site attribute you have to specify the domain of your website, and which activity information should be displayed. Using other data attributes you can control the user experience of the Activity Feed on your website, and whether you want to explicitly include recommendations or not.
Although you could place the Activity Feed on every page on your website, there is a chance that this would work against you and distract your visitors from your content. Because the Activity Feed allows you to expand the reach of your website, it might be a better idea to analyze your web analytics data and place the Activity Feed somewhat more strategically, for
example on the frequent exit pages and landing pages such as the home page.
Because in most scenarios you will embed the Activity Feed on specific pages, the best way to integrate it with your website is not to include it in the Master Page or Page Layouts, but to add it to the specific pages. The best way to do this is to embed the Activity Feed code snippet in the page using the Script Editor Web Part.
Figure 5. Embed code
Figure 5. Embed code

Recommendations Bar

A slightly different, nevertheless very interesting, plugin is the Recommendations Bar. This plugin can also help you expand the reach of your website by displaying recommended content. What’s different about the Recommendations Bar is its usage scenario.
The Recommendations Bar is located at the bottom of the browser window. Depending on its configuration it might become visible after a certain amount of time, for example after users have scrolled past a certain point of the page. This plugin can be very useful because it provides your visitors with suggestions of additional content they might find interesting.
When integrating the Recommendations Bar on your website, you should consider integrating it with the detail pages. That way, when your visitors have finish consuming the current content, they are offered a next step. Once again this plugin requires the reference to the Facebook JavaScript SDK to work. The plugin itself is represented by the following markup:
<div class=”fb-recommendations-bar” data-href=”http://contoso.com/articles/my-article/”></div&gt;
Because you want recommendations to be visible on every page, you should add it to the Page Layouts used by your detail pages. Following is the markup that you should add to your Page Layouts to ensure that the Recommendations Bar will work for every page. Notice how the contents of the data-href attribute are being set dynamically by using the SeoCanonicalLink control we discussed previously:
<!–SPM:<%@Register Tagprefix=”Contoso” Namespace=”Contoso.SharePoint.Seo.Controls” Assembly=”Contoso.SharePoint.Seo, Version=1.0.0.0, Culture=neutral, PublicKeyToken=a285ef6967f781d3″%>–>
<!–MS:<Contoso:HyperlinkControlWrapper runat=”server”>–>
<Control>
<control type=”Microsoft.SharePoint.Publishing.WebControls.SeoCanonicalLink” assembly=”Microsoft.SharePoint.Publishing, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c” />
</Control>
<ContentTemplate>
<div class=”fb-recommendations-bar” data-href=”$Url$”></div>
</ContentTemplate>
<!–ME:</Contoso:HyperlinkControlWrapper>–>
Like all other content, the recommendations that are displayed by the Recommendations Bar are controlled by the activity on your website, and recorded by Facebook. Although the Recommendations Bar will display personalized content suggestions, it doesn’t offer you any control regarding what content will be displayed where. Although the differences in which items are suggested as recommendations might be subtle, they could decide whether or not your visitors will remain on your website.
An alternative to integrating the Facebook Recommendations Bar that is worth considering is using the content  recommendations capability provided with SharePoint 2013. Although it would require some customizations to achieve similar user experience as the one that Facebook Recommendations Bar has, the great advantage is that you can control which content is displayed as recommendations. Because content recommendations are based on SharePoint 2013
Search, you can leverage all of its capabilities to ensure that the most relevant recommendations are displayed to your visitors.

Bonus:Yamming it!

If your organization offers products or services to consumers, integrating with Facebook might be a wise choice. If however your business is more based on knowledge and is targeted at other businesses, it might be worth the effort to integrate with Yammer as well. To put it simple: Yammer is Facebook for enterprises. It helps organizations share their knowledge by allowing them to communicate within the boundaries of their organization. Making it easier for your visitors to share the content from your website with their Yammer networks might help you reach more of your business customers.
Although Yammer doesn’t offer as many plugins as Facebook does, one thing that you could easily include in your website is a Yam it button. The Yam it button allows your visitors to share the page that they are currently visiting with their
Yammer network with a single mouse click. Following is sample code of a Yam it button:
<a href=”javascript:var d=document,w=window,e=w.getSelection,k=d.getSelection,x=d.selection,s=(e?e():(k)?k():(x?x.createRange().text:0)),f= ‘https://www.yammer.com/home/bookmarklet&#8217;,l=d.location,e=encodeURIComponent,p=’?bookmarklet_pop=1&amp;v=1&amp;u=’+e(l.href)%20+’&amp;t=’+e(d.title.replace(/^ *| *$/g,”))%20+’&amp;s=’+e(s),u=f+p;a=function()%20{if%20(!window.open(u,’sharer’,'toolbar=0,status=0,resizeable=1,width=650,height=550′))l.href=f+p};if%20(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else{a()}void(0);”>Yam it!</a>
The Yam it button is completely based on JavaScript so you can include the above snippet directly in SharePoint without modifying it. From the integration perspective the Yam it button can be best compared with the Facebook Like button, so wherever you feel it is right to include the Facebook Like button, it is probably a good place to include the Yam it button
as well.
Figure 6. Yam It! button
Figure 6. Yam It! button

Summary

Integrating social networks with your website can help you expand the reach of your website and help your visitors discover new content. Most social networks offer standard plugins that can be easily integrated within your content management system. SharePoint is no exception here. No matter if you want to integrate social media only on some specific pages or all
pages of a particular type, SharePoint offers you the flexibility to do so effortlessly.

Additional Resources

About the author

Waldek Mastykarz is a Microsoft SharePoint Server MVP and works as a SharePoint consultant at Mavention. Waldek shares his enthusiasm about the SharePoint platform through his blog, articles published in online and off-line magazines and on MSDN SharePoint Forums. He is also a speaker at community events such as the SharePoint conference in London, SharePoint Connections Amsterdam, and SharePoint Saturday. In addition to his job at Mavention, Waldek is a Virtual Technology Solutions Sales Professional for Microsoft Netherlands. In this role he helps answer customer questions around SharePoint Web Content Management (WCM).
 
Support : Chandra Optiandi || STMIK Amikom Yogyakarta
Copyright © 2014. Welcome,Reader! - All Rights Reserved
Template Modify By : Chandra Optiandi
Proudly Powered By : Blogger