All Collections
CMS Integrations
How to integrate Silktide with Sitefinity
How to integrate Silktide with Sitefinity
Julia Voortman avatar
Written by Julia Voortman
Updated over a week ago

This guide details what the Silktide CMS plugin for Sitefinity does, how to download and install/configure it, and how it is used in practice. You will need Administrator access and be able to upload a plugin to your Sitefinity installation.

This plugin enables two main features:

  • Easily switch from the Silktide application to the appropriate page in your Sitefinity installation to make changes.

  • New or changed pages in your Sitefinity installation will be automatically checked in Silktide when published.

Installing the plugin

File configuration

Move “SilktidePlugin.dll” to your project bin folder.

Example of SilktidePlugin.dll

Move “Global.asax” to your project root folder.

Example of files to move.

Move “SilktideFiles” folder to your project root folder.

Example of the folder to move

Ensure the URL scheme is correct

If you use a different URL scheme for the admin backend to the default. You will need to modify “SilktideFiles/JSON/silktideConfig.json” to ensure “backofficeurl” reflects your new URL scheme. For most installations, this should not need to be modified.

Note that “[pageRelativePath]” must remain within this as it is used for dynamically generating URLs.

Adding Silktide configuration page

Silktide’s Sitefinity plugin requires an administrative page that allows the configuration of our API.

1. Create a new page in Sitefinity

Example of “Create page” button

2. Add the page name and click “Create and go to add content” button.

Example of creating a page

Example of ‘Create and go to add content’ button

3. Drag and drop “SilktideAPI” from sidebar widgets.

Example of ‘SilktideAPI’ widget location

Example of dragging ‘SilktideAPI’ widget onto the page

4. Publish the page to finish.

Configuring the Plugin

Silktide requires an API key for authentication and a meta tag for the editor URL put into place for the webhook to be sent out, and the page inspector to work.

Obtaining your API key

Silktide provides an API key to authenticate calls to the API for CMS integrations.

To obtain your API key:

  1. Login to Silktide

  2. Choose your website

  3. In the top right of the screen, Click Settings > Integrations.

  4. Click New CMS, then select your CMS and Add

API key configuration in Sitefinity

Head into Sitefinity backend and select “Silktide” from the menu. Simply place your API key in here provided by Silktide and hit “click here for verification”. If this returns successfully. Press “Save” for the changes to take effect.

Example of Silktide CMS configuration page

Setting up Silktide CMS meta tag

In the .cshtml page template specify the following line in the header:

meta name="silktide-cms" content="@SilktidePlugin.Services.SilktideBackofficeUrl.GetEncUrl()"

This must be on every page you wish for the plugin to work on. Usually, this is done in the master template that other pages inherit.

Retesting your site

Once the Plugin has been configured in Sitefinity, you will then need to retest your site so Silktide will read the relevant data.

Login to Silktide and select your report – just click Retest in the top right and wait for the site to retest.

Navigating from Silktide to Sitefinity

Once the report has finished running, you can then view your results. If everything has been configured correctly, when viewing the Inspector there will be a "CMS" button in the top right next to the Page and HTML buttons.

Selecting the "CMS" button will instantly take you to your Sitefinity installation with the appropriate page loaded.

Confirmation of working webhook

If you publish a page in your CMS and then immediately switch into Silktide, you should see a blue progress banner appear at the top of the screen, while the updated page is tested.

If you’re experiencing difficulties with this integration, please reach out to us via the live chat built into your Silktide account.

Did this answer your question?