A plugin to provide basic social button sharing to MKDocs pages

This plugin allows social sharing buttons to be added to the mkdocs.yml file, which will then build buttons into the site pages.

The plugin defines the buttons in the mkdocs.yml file. This example shows some simple settings.

plugins:
    - social-buttons:
        default_message: "A default message"
        apply_to_paths:
          - blog/path
        exclude_hashtags:
          - guestauthor
        twitter:
          message: "A button specific message"
          button_share_callback: "my_handler"

A section is defined under social-buttons for each button that you wish to add. The settings for generating the buttons are as follows:

• default_message: A sharing message that applies to all buttons (the text to be shared with)
• <button>/message: A specific message to be used for the given button. This overrides the default message
• alternative_url_root: An alternative URL to use as the sharing root in the links (e.g. http://mytesturl.com/). This is required for some buttons (like linkedin) which don't like being built with a localhost URL when testing locally.
• apply_to_paths: a list of paths to apply the buttons to (e.g. you only want to apply them to the blog content). If not present, applies to all pages.
• exclude_hashtags: if you use the meta property tags, exclude the hashtags listed from the share text (note they are listed in hashtag-format with no spaces)

The buttons are generated as list items, so they can be styled conveniently. The list styling is up to the user, generally to allow control of flow and padding etc.

The following config items are available to assist with styling:

• button_class: A class that is rendered as the list item's class, i.e. <li class="<named class>">
• button_style: A style that is rendered as the list item's style, i.e. <li style="<named class>">

social-buttons provides a way of handling button clicks. Where possible this is handled natively by the button itself.

(Coming soon: support for handling any click if there is no native support)

This can be achieved by adding the button_share_callback property to the button's config. This will then call the handler that you have defined with two arguments:

• The path to the page containing the button being clicked
• The button that was clicked to share it.

For example, using the example config above, the following call would be executed if the twitter button was clicked on the blog/about/ page:

my_handler("blog/about/", "twitter")

This handler function must be provided by the client. The typical way of doing this is by adding scripts in the extra_javascript section of the mkdocs.yml config file.

It should be noted however that this only tracks the clicks of the button, NOT the success of sharing the content.

Current supported buttons are:

• Twitter: config section name: twitter
• LinkedIn: config section name: linked_in