Close
Next
Prev

 

    Loading...

Pluck Blogs are tied in to the user's persona and activity and come out of the box with Pluck Comments, allowing for more community creation within your site. Blogs allow you to create and deliver content to your users in an on-going way, based on the type of blog you decide to deploy.

Pluck BlogsBlogs

Promote an individual user to an “expert contributor” within a blog to create a feeling of inclusion within community. Maintain control over the content being presented in the blogs by creating user tiers, so that certain users can only create drafts that must be approved by a moderator prior to publishing. Lastly, Blogs increase your overall website traffic by driving search traffic with SEO friendly URLs.

Features

  • Multi-author Blogs
  • Personal Blogs
  • Public Blogs
  • Content Tagging
  • Rich Media Support
  • Advanced moderation
  • Integrated Comments and Reactions
  • Integrated Discovery
  • RSS Support
  • Permalinks
  • SEO Friendly URLs

Works With

Mini-Personas
  — Appear when you hover over the blog author's avatar, allowing the reader to learn more about the author and connect with the community.
Comments
  — Stimulate conversation, engagement, and page views by letting users comment beneath blog entries.
Discovery
  — Bubble up blog posts that recently made or are heavily commented on.
User Reactions
  — Syndicated user reactions drives traffic back to the site.
Gamification
  — Encourage participation in Blogs by rewarding users.

Implementation Tips

Blogs is not a content management system.

Frame the article being written as a question to help drive reactions from within the community.

Enable friendly URLs to include post title for ease of searching and use the REST implementation to drive SEO.

Take advantage of tagging functionality to drive additional discovery.

Details

Blogs are an established vehicle for delivering long-form and often rich-media content. SEO Capabilities, such as Vanity URLs, help improve SEO performance and attract new visitors to the brand. There are three types of blogs that can be used as a part of your social media strategy: Multi-author, Public, and Persona. Multi-author blogs provide a platform for expert blogs, allowing multiple users to contribute to the same blog but each being individually identified. Public blogs allow any user on the site to post, generating user participation. Persona blogs are user-specific, and only appear on the Persona page. Blogs help brands build a dynamic, interactive community through rich media embedding and integrated comments.

  • AbuseReportThreshold

    Description: Sets the threshold number of AbuseReports that can be on an item before it is automatically removed from storage search results.

    Default Value: 2147483647

    Applications: Blogs Comments Forums Reviews

    Preference Type: Global

    Import: YES

    Value Range: 1...2147483647

  • ActionUIControl

    Description: A dictionary that defines what authentication type is required for each Action type. If nothing is defined for a particular ActionUIEnum, Weak authentication is assumed, i.e. the HD cookie must be present in order for the user to be allowed to perform the action.

    Default Value:

    Applications: Blogs Comments Forums Persona

    Preference Type: Global

    Import: YES

    Value Range: Serializable Dictionary

  • AllowCommentsByBlogPosterToBypassApproval

    Description: Allows comments by blog owner to by pass approval.

    Default Value: true

    Applications: Blogs

    Preference Type: Global

    Import: YES

    Value Range: true false

  • BlogCommentApprovalDefault

    Description: BlogCommentApprovalDefault determines the default value for approval of blog comments. The default is Everyone, which will require approval from the blog owner for all comments made on a blog post. If set to Nobody, the default is to not require moderation before submitted blog comments are published.

    Default Value: Everyone

    Applications: Blogs Persona

    Preference Type: Global

    Import: YES

    Value Range: Everyone Nobody

  • CanEditViewOtherUsersPostsTier

    Description: Indicates the minimum tier required to edit/publish other peoples posts.

    Default Value: Editor

    Applications: Blogs

    Preference Type: SiteSpecific

    Import: YES

    Value Range: Anonymous All Standard Trusted Featured Staff Editor

  • CanInsertHTMLinTaglineTier

    Description: Indicates the minimum tier required to insert HTML in the tagline of a blog.

    Default Value: Editor

    Applications: Blogs

    Preference Type: Global

    Import: YES

    Value Range: Anonymous All Standard Trusted Featured Staff Editor

  • ExternalUrlsOpenInNewWindow

    Description: Setting to True opens external links in new windows instead of in the same browser window, e.g. links in forums/blogs/comments

    Default Value: false

    Applications: Blogs Comments Forums

    Preference Type: SiteSpecific

    Import: YES

    Value Range:

  • ForgotPasswordUrl

    Description: This is the link that goes to the customer's registration system that allows users to reset their password.

    Default Value:

    Applications: Blogs Comments Forums Persona

    Preference Type: SiteSpecific

    Import: PROMPT

    Value Range:

  • IsAbstractEnabled

    Description: If enabled displays the Abstract text arear for creating/editing blog posts

    Default Value: false

    Applications: Blogs

    Preference Type: Global

    Import: YES

    Value Range: true false

  • IsAbstractTruncationEnabled

    Description: If enabled the blog abstract is truncated and stripped of HTML

    Default Value: true

    Applications: Blogs

    Preference Type: Global

    Import: YES

    Value Range: true false

  • IsCodeButtonEnabled

    Description: Determines if the HTML button is to appear in TinyMCE within the Blog create and edit views.

    Default Value: false

    Applications: Blogs

    Preference Type: SiteSpecific

    Import: YES

    Value Range: true false

  • LoginUrlRedirectQueryParamName

    Description: This is the query parameter that is appended when the login link is followed. It allows the customer's site to redirect back to the page where the user clicked the Login link.

    Default Value: plckRedirectUrl

    Applications: Blogs Comments Forums Persona

    Preference Type: SiteSpecific

    Import: YES

    Value Range: string

  • LogoutUrlRedirectQueryParamName

    Description: This is the query parameter that is appended when the logout link is followed. It allows the customer's site to redirect back to the page where the user clicked the Logout link.

    Default Value: plckRedirectUrl

    Applications: Blogs Comments Forums Persona

    Preference Type: SiteSpecific

    Import: YES

    Value Range: string

  • MailBlogPostSubjectText

    Description: Subject text that will be sent on a blog post notification. {0} expands to post title, {1} expands to username. Example: {0} by {1} on Pluck.com

    Default Value:

    Applications: Blogs Email

    Preference Type: SiteSpecific

    Import: YES

    Value Range: {0} by {1} on Pluck.com

  • OriginalVideoUrlBasePath

    Description: Defines the path under the sitelife application at which we will mount the original videos virtual. This shouldn't need to change and this pref is only as a fail safe which we don't expect to be overriden generally.

    Default Value: Content/Videos/Store/Main

    Applications: Blogs Comments Forums

    Preference Type: SiteSpecific

    Import: YES

    Value Range:

  • PersonaReadableBlogUrlBase

    Description: Used to enable 'pretty' URLs for persona blogs. Note that UseReadableBlogUrls MUST be set to true for this to work. User's display name will be appended to this url, WITHOUT SEOTokenDelimiter in the URL. i.e. if url base is set to '/blog', user 'Zathras' will have the blog URL of 'http://www.foo.com/blogzathras'. You'll probably want to use '/blog/' to get that extra delimiter.

    Default Value:

    Applications: Blogs

    Preference Type: SiteSpecific

    Import: NO

    Value Range:

  • PublicBlogCreatePostTier

    Description: Indicates the minimum tier required to create posts on a public blog

    Default Value: Standard

    Applications: Blogs

    Preference Type: Global

    Import: YES

    Value Range: Anonymous All Standard Trusted Featured Staff Editor

  • PublicBlogPublishPostTier

    Description: Indicates the minimum tier required to publish posts on a public blog

    Default Value: Editor

    Applications: Blogs

    Preference Type: Global

    Import: YES

    Value Range: Anonymous All Standard Trusted Featured Staff Editor

  • PublicBlogViewCommentsTier

    Description: Indicates the minimum tier required to access the view comments on a public blog

    Default Value: Editor

    Applications: Blogs

    Preference Type: Global

    Import: YES

    Value Range: Anonymous All Standard Trusted Featured Staff Editor

  • PublicBlogViewEditPostsTier

    Description: Indicates the minimum tier required to access the view/edit posts on a public blog

    Default Value: Standard

    Applications: Blogs

    Preference Type: Global

    Import: YES

    Value Range: Anonymous All Standard Trusted Featured Staff Editor

  • RegisterUrl

    Description: This is the location of a register new user page on the customer's website, where users would go to sign up for an account. This link is surfaced when a user is not logged in. This preference must be defined. There is no default value.

    Default Value:

    Applications: Blogs Comments Forums Persona

    Preference Type: SiteSpecific

    Import: PROMPT

    Value Range: string

  • RegisterUrlRedirectQueryParamName

    Description: This is the query parameter that is appended when the register link is followed. It allows the customer's site to redirect back to the page where the user clicked the Register link.

    Default Value: plckRedirectUrl

    Applications: Blogs Comments Forums Persona

    Preference Type: SiteSpecific

    Import: YES

    Value Range: string

  • SpamTriggersAbuseReportThreshold

    Description: If true, any content flagged as spam will be treated as automatically exceeding the abuse report threshold.

    Default Value: false

    Applications: Blogs Comments Forums Reviews

    Preference Type: Global

    Import: NO

    Value Range: true false

  • VidaVeeVideoPlaybackUrl

    Description: VidaVee video playback url.

    Default Value: http://prod.publish.vidavee.net:80/vidad/publish.vidavee.com/pluck/Pluck/

    Applications: Blogs Comments Forums

    Preference Type: SiteSpecific

    Import: YES

    Value Range:

To set up PAS MultiAuthor or Public Blogs With REST

  1. Before you can install Pluck applications on your pages, your Pluck Application Server environment must be set up.

  2. Determine on what page(s) you want to add a Blog to.

  3. Make sure any preferences are set. Your Pluck representative can help set those preferences for you and any others that are relevant to your implementation.

  4. Load the Pluck Libraries. Give your site access to the applications on the Pluck Application Server by including the following somewhere in the <head> tag:

    <script type="text/javascript" src="http://yourPluckServer.com/ver1.0/Content/ua/scripts/pluckApps.js"></script>

    where yourPluckServer is the domain of your Pluck server.

  5. Include the Pluck Applications CSS. In the <head> tag, link to the Pluck Application CSS:

    <link rel="stylesheet" type="text/css" href="http://yourPluckServer.com/ver1.0/Content/ua/css/pluckAll.css" />

    where yourPluckServer is the domain of your Pluck server.

    Custom Loading Libraries. If you need to load your own CSS to work with Pluck applications, see Specify Your Own CSS On The Page

  6. Make The REST Call. Call the Blog response with the appropriate URL:

    http://yourdomain.com/ver1.0/pluck/publicblogs.app?plckBlogType=Public&clientUrl=http%3A%2F%2Fwww.yourdomain.com%2Fpageyouareon%3Fquerystring
    

    where yourdomain is the domain of your Pluck server.

    When SEO friendly blog Urls are enabled, it is recommended that clientUrl be the only property included in the REST call. Including any other property may cause unexpected results. Use the UseReadableBlogUrls preference to enable SEO friendly blog Urls.

    Note:

    When installing REST applications, you must pass the SiteLifeHost and AT cookies in the REST call. Depending on your environment setup you may be required to pass additional cookies. The clientUrl is also required and should be passed in as the current page being requested with the full querystring. URLencode the entire value when adding it to the above URL. Don't URLdecode the requesting URL prior to encoding it or you can end up with invalid URLs. For more information, ask your Pluck Representative.

Drop Blogs On a Page

  1. Load the Pluck libraries. In the <head> tag, add:

    <script type="text/javascript" src="http://yourPluckServer.com/ver1.0/Content/ua/scripts/pluckApps.js"></script>

    where yourPluckServer is the domain of your Pluck server.

  2. Build the parameter string:

    The parameter string is a comma-delimited list of required and optional parameters meant to format the widget. For example:

  3. Place the Blogs JavaScript call on the page where you want the app to appear:

  4. Save and reload. The Pluck Blogs application appears on the page where you put the PAS call.

    6.0.11 Release        © 2014 DemandMedia                                   Teacher’s Edition