Help Center
Comment on page

Preserve your Setka Editor content after the service shutdown

This is a step-by-step guide on ensuring your content created with Setka Editor is safe in your CMS after Setka Editor infrastructure shutdown.


To ensure robust content preservation on your CMS after the Setka Editor infrastructure shutdown this guide will do two things:
  1. 1.
    Explain which assets rely on Setka Editor CDN
  2. 2.
    Describe the steps needed to migrate mentioned assets to your CMS's CDN

Assets that rely on Setka Editor CDN

  • images
  • JavaScript code for enabling interactive post elements
  • CSS code which enables all the styling of your articles

Migrating Setka Editor assets to your CMS's CDN

Step 1 — receive the list of posts

Make a request to Setka Content Cloud API to receive your list of Setka Editor posts. Here is a request example:<token>&filter=state:<state>&include=images&limit=10
state determines the publication status of the post:
  • Set to published to only get published posts.
  • Set to draft to get drafts.
  • Set to all to get both drafts and published posts.
limit determines the number of posts you can receive as a response. Please make sure you don't set the value too low and miss some of the posts.
Check the Content Aloud API documentation for more filters.

Step 2 — download assets for every post

If the request is successful, you will receive a response consisting of an array of posts. The response will be paginated if the number of posts is large. Below is an example API request response:
HTTP/1.1 200 OK
posts: [
"id": 2587,
"title": "Stylist",
"style_name": "General",
"layout_name": "6col_19774",
"reading_time": 240,
"preview_link": "",
"state": "published"
"author": {
"id": 44,
"name": "John Smith"
"body_html": "Hello!",
"assets": {
"plugins": [
"styles": [
"images": [
"id": 3310,
"url": "",
"alt": "Alt text"
"sizes": [
"width": 3654,
"height": 5473,
"url": ""
"width": 500,
"height": 5473,
"url": ""
"width": 1000,
"height": 5473,
"url": ""
"hubspot_post": {
"id": 141,
"url": "",
"blog_id": 1315
"created_at": "2019-07-19T10:25:27Z",
"updated_at": "2019-07-19T10:27:40Z",
"published_at": "2019-07-22T13:34:11Z"
pagination: {
"page": 1,
"limit": 20,
"page_count": 1,
"total_count": 1
Download the assets for each post from the array. The possible types of assets are:
The scripts to run interactive post elements (e.g., animations, galleries, or notes).
The CSS files of post styles, including the common style file, the standalone style, and the layout grid file.
The images used in the post, where:
id — the image’s unique ID.
url — the link to the file.
alt — the alternative text.
sizes — several options for the image size, depending on the device’s screen size. Note: Getting the images field in your response will require using additional parameters.

Step 3 — uploading assets to your CDN

When all assets are downloaded, store them in your infrastructure.
Advice – store files with the same path, that will simplify the update script.
For example: If CSS URL looks like: you should store it in your infrastructure and make it accessible via the URL on your domain, for example like this:

Step 4 — replacing asset URLs and updating content

When all assets are downloaded and stored in your infrastructure, you need to replace all links used in the Post body and include CSS files in the Post Page. You will need a custom script tailored to your case.
Inside the Post body there might be images. If you created Posts inside Setka Cloud you’ll find srcset generated for multiple image sizes. It’s a feature provided by Setka Cloud. Links to image variations are not provided. We suggest that you remove everything inside the srcsetHTML attribute for in <img tag> and store the original image in your infrastructure.
You have the following piece of code:
<img src="" data-image-id="248663" data-image-name="Mufasa_headshot.png" class="stk-image stk-reset" srcset=" 1044w, 500w, 750w, 1000w" width="1044" height="1302" loading="lazy">
You should pick the original size – in src attribute (you can find the same link inside Post API response) and make it accessible on the URL like
Then change the link inside Setka Post body and remove the srcset. The result will look like this:
<img src="" data-image-id="248663" data-image-name="Mufasa_headshot.png" class="stk-image stk-reset" width="1044" height="1302" loading="lazy">