The VOR ecosystem – how to use it

The problem with legacy systems

A typical media company today runs a publishing system with twenty plugins, Google Analytics beside it, a newsletter tool, the affiliate networks' own portals, an SEO tool, spreadsheets for the revenue and an agency for whatever cannot be clicked into place. Often more than twenty logins, as many truths – and none of them answers the only question that matters: which article made money, and what should we write next?

The weaknesses are the same everywhere. Fragmented data: traffic in one system, reading in another, commission in a third – nobody ties the euro to the article. Built for big newsrooms: expensive, slow to change, needs developers. No AI in the workflow: assistants live in another tab with no access to the archive, the rules or the figures. No real time: analytics tools only see readers who let scripts through, and the numbers arrive afterwards. Two languages require two sites. And nothing keeps watch: buy links break silently, prices go stale, duplicates get published, a failed schedule is noticed when the page is empty – the publisher finds the error when the money is already gone.

VOR's answer – one suite, one truth, more revenue

VOR was created to be at the forefront: a turnkey solution for small and medium-sized media companies that connects the fragmented data into real value. Everything that happens – every page view, every second read, every click on a buy link, every euro from the networks, every search without a hit, every topic the world writes about – lands in the same system and is tied to the article, the section and the person. Only then can you steer: write what is searched for, link what pays, lift what is read.

That gives you the opportunity to earn more as a publisher. VOR Insights shows which articles pay off, which programs are worth applying for, where the revenue leaks and what should be written next. VOR Studio produces the draft in minutes, in every language version, with guards that stop errors before publishing. VOR Analytics counts every reader on the server, in real time. VOR Chat lets agents work in the same system under the same rules – drafts freely, publishing on order. VOR Monitoring watches the system, the money, the content, the audience and the world around the clock, so nothing breaks silently.

Turnkey means: the sections are taken from the site, the archive is imported, the networks are connected, the newsroom is invited and the agents get their accounts – without developers, without an agency, without changing publishing system. The site stays yours; VOR becomes the engine behind it.

The suite at a glance

Five products and the modules that work in all five. Same login, same data, same rules.

Who VOR is for

Media companies, magazines and niche sites with a small or medium-sized newsroom – often with affiliate and commercial content as part of the business – that want one system instead of eight, figures that add up, publishing in every language version and AI agents that do the heavy lifting under the newsroom's control. Management gets the money and the state of play on one page; the newsroom gets a tool where draft, check and publishing belong together; the writer gets an overview in their own name.

Getting started – turnkey in a day

1. The sections: VOR reads the site's real sections and addresses – nothing is hard-coded.
2. The archive: all content is imported with images and rights; the image bank takes over the serving.
3. The money: the affiliate networks are connected (Adtraction, Awin, CJ, TradeDoubler …) – programs, campaigns and commission start flowing in.
4. The newsroom: invite the people, set roles in Team & agents; everyone gets their own overview.
5. The agents: create agent accounts with the right rights and connect Claude to Studio and Insights.
6. Live publishing: test mode until management approves the production switch – then releases publish to the site in every language version.

How it fits together

The world outside (searches, campaigns, what others publish) becomes suggestions in VOR Insights. Suggestions become orders and drafts in VOR Studio – written by the newsroom or by an agent in VOR Chat. The draft is reviewed, approved and published to the site in every language version. VOR Analytics measures what readers do, the buy links measure what they buy, and the numbers flow back into Insights as the basis for the next suggestion.

Underneath it all lies VOR Monitoring: the guards that check the system, the money, the content, the audience and the world around the clock and raise the alarm where you work.

Everything runs in one system with one login. What you see in Studio is the same data the connections and the assistant see – no copy, no export.

The five parts

VOR Studio – the publishing system: overview, content, a two-language editor, calendar, media library, buy links, templates, sections, home page, connections, team & agents, settings – and this manual.

VOR Insights – the panel for management and the newsroom: the money (outbound traffic, revenue per article, stores, programs, the link guard), the audience, the content, the world outside and the orders to VOR.

VOR Analytics – the measurement: Cloudflare's count on the server (every reader, not only those who let scripts through), the site's own measurement of read time and depth, real time, devices, countries, sections – with Google Analytics beside it for comparison.

VOR Chat – work in the chat: the assistant Ask VOR in Studio, the connections that let Claude work in Studio and Insights as you, and the agent accounts (VOR, the editor-in-chief's agent, the writing agents …) that write drafts on order.

VOR Monitoring – the guards and the alarms: the system watches itself around the clock – response times and the database, buy links and prices, duplicates and formats, the publishing schedule, the audience in real time and the sources' health – and raises the alarm where you work: in the order queue, in Insights and in the evening report.

The modules – built in everywhere

SEO optimisation: suggested title, meta description, teaser title, share text and tags per article, the pre-publish check, and the trend watch's scored topic suggestions (search volume, competition, campaigns).

VOR Search: the site's search engine (same hits as the search box on the site) and the Searches page in Insights – what readers look for and do not find.

Buy links (VOR Link Generator): Studio recognises the store, builds the tracked link with the article's id and counts clicks and commission per article. The link guard checks that the money gets through.

The guards: the duplicate guard (the same article is never published twice, never the same hero on two articles within 30 days), the link guard (buy links work and carry the article's id, never outbound links in the body), the price guard (prices are corrected without unpublishing), the format guard (headline length, standfirst, hero 1200×800, tags).

The trend watch: 100+ sources read around the clock, the morning brief and the morning draft (the day's first draft, time set per title), Google Trends. The CMS import every 15 minutes. The calendar and scheduling. Translation into the language versions. The image bank in R2. The evening report (time per title).

Log in

The same account opens VOR Studio (/studio/) and VOR Insights (/management/). Enter your e-mail and click the button in the mail – or use username and password. “Keep me logged in” lasts 30 days on the device.

Your Studio role (super administrator, editor-in-chief/publisher, administrator, writer) decides what you can do in Studio. The panel role in Insights (CEO, CFO, editor-in-chief …) decides whether you see the money.

1. Open /studio/ or /management/.
2. Enter your e-mail › “Send login button” › click the button in the mail.
3. If the database hiccups you see “One moment …” and the page reloads itself – you are still logged in.

Menu, search and theme

The menu on the left is all of Studio, in groups: Workspace (Overview, VOR Monitoring, VOR Insights, VOR Assistant), Create (Content, Media library, Buy links, Templates), Manage (Calendar, Sections, Home page, Apps, Orders, Tags, Dictionary & people, Rates & savings, Team & agents) and Settings (Integrations, Settings, Manual & support). Create also has Suggestions, and Buy links has the Link guard tab (the VOR map). New content and Search are always on top; the menu scrolls in its own area so your name, the theme and Log out always stay at the bottom.

Search (⌘K on Mac, Ctrl+K on Windows) jumps to a view or an article. Under your name you choose the theme: light, dark or as the system. The interface language is chosen in Settings and is independent of the article's language.

Menu rows only some people see

The menu shows what your role may do. VOR Monitoring is only shown to administrators and the editor-in-chief. Under Manage there can be more rows depending on what the title has switched on: Personal finance, Brands and Authorities (when those verticals are active) and the VOR map under Settings. If you lack a row a colleague has, it is the right – not the system – that differs.

Roles and rights

People and agents have different default rights. People in the newsroom do everything their role allows. Agents create drafts – publishing, scheduling and taking down happen only on order from a person with that right, in the same chat.

Accounts for people – invitations, roles, two-factor and locking – live in one place: VOR Insights › Settings & help › Users. It is VOR's only account system and applies to both Insights and Studio. Team & agents in Studio handles the agent accounts and what each person may do in Studio (role, sections, languages).

The VOR map – what lives where

The rule: what you do lives in VOR Studio – create, approve, fix, order. What you read off lives in VOR Insights – the money, the audience, the publishing, the world. Views that have moved from Insights to Studio keep their old addresses for now, with a line pointing to Studio; the same map is in Insights under Settings & help › The VOR map.

The overview – your day

The overview is personal (“Your overview” – with your name). On top the key figures for today, yesterday, two days ago, 7 days, 28 days or a custom span – always compared with the same time in the previous period, so a Tuesday morning is compared with Monday morning, not with all of Monday.

Page views and readers come from Cloudflare (every reader), read time from the site's own measurement, buy clicks and commission from the affiliate networks, published and to do from Studio. Six key figures show at once, the rest behind “Show more” – every tile says exactly what it counts: the span, the source and when the figure was counted. Page views come as today, rolling 24 hours, 7, 14 and 30 full days and yesterday; readers the same way; affiliate today, 7, 14 and 30 days; Loyalty cards is the exact number of cards in the programme with the levels and how many sit on the home screen; Readers per language show page views per language version over the last 7 days. Below the figures: Recent content (the latest changes, with status) and VOR Monitoring with today’s ten most read – five visible, the rest behind “Show all 10”. Under “Customise layout” every key figure gets ← → ✕: move it or hide it; the hidden ones sit in the “Hidden figures” row and come back with +, “Reset the figures” restores the default order. Saved on your account. Below the figures: Waiting for you (what you should approve), Pick up where you left off, The newsroom today – and further down the chart, right now, most read, sources, devices, sections, revenue and countries.

Order, Best ideas and Ask VOR

Order: seven buttons – Shopping edit, Article, Commercial article, Feature, Recipe, Place guide, List. Write the subject and preferably a line about the angle, choose the section, tick “Urgent” if it must happen today. The order is placed in your name in the queue the agents work from, and shows up under My orders with status, reply and a link to the draft.

Best ideas right now: the trend watch's highest-scoring suggestions. “Order” turns a suggestion into an order with angle, keywords and stores as the brief; “Dismiss” removes it.

Ask VOR: the assistant in Studio – one chat per person. It works as you, with your rights, and has the same tools as the connections: find and read content, create drafts, suggestions, check, preview – and everything in Insights (today's state, most read, real time, revenue, campaigns, orders). Status and publishing only on your explicit order. The quick questions above the thread (“How is today going?”, “What have we earned today?”, “What is waiting for me?”, today’s most read, shopping edits for the weekend) send with one tap; the V button on a row in VOR Monitoring or Recent content asks about that very article. The thread shows the latest exchanges, the rest behind “Show earlier”; “Clear” at the top right resets it.

1. Click “Shopping edit” › write “wine coolers under 300 €” › choose Home › Order.
2. The order shows under My orders as “New”; when the draft exists it turns into “Ready for review” with a link.
3. Ask VOR: “How is today going? Short.” – the answer comes from Insights within seconds.

Content – the archive and the status flow

Content is the whole archive – everything published on the site (imported from the site's CMS) and everything made in Studio. The tabs follow the status flow: Draft → In review → Approved → Scheduled → Published, and Taken down when something has been removed from the site. Search in headline, body and tags; filter by section and by person or agent.

Each row shows image, headline and address, type/template, section, language versions (one per active language – green = done, yellow = needs updating, grey = missing), owner, modified and status. The eye opens the preview. The trash is its own view: nothing is deleted, it is moved.

Waiting for your yes: everything waiting for a yes in one place – what VOR wrote outside Studio (the morning draft, articles from the suggestion queue; the same drafts as Insights › Drafts) with Publish now, Schedule, Dismiss and Read and edit in the site's CMS, and Studio's own content that is in review. Publishing requires that you tick that you have read the draft and have publishing rights. A dismissed draft stays in the site's CMS – nothing is deleted.

Language version outdated: the tab shows articles whose source text changed after a language version was translated (the yellow “needs updating” mark). Select them – or any articles – and press “Retranslate” at the bottom: Studio translates one at a time, the row shows how many are done, and each version is saved as a draft on its article. Nothing is published by itself – open the article, read it and publish the version.

The import – the archive comes along, nothing breaks

The archive is imported from the site's CMS: articles, pages, authors, categories, tags and images, in batches in the background. The import is non-destructive and can be re-run: the same article becomes the same record in Studio, and blocks Studio does not recognise are kept as an html block with the content intact. A re-imported article that is republished updates the same page on the site – the address never changes.

Changes made directly in the CMS are fetched every 15 minutes as a new revision; whatever someone is working on in Studio is left alone. Articles unpublished directly in the CMS disappear from the index and section lists by themselves.

Suggestions – from suggestion to order

Suggestions sits under Create: what we should write about, from the monitoring – suggestions with a business case (readers' searches matched to approved stores), purely editorial ideas from hundreds of sources, Google Trends and campaigns to pick from at the networks. No headline is invented.

On every card: Order (choose the type – article, commercial article, shopping edit, feature, recipe, guide, list – and an order is placed in your name in the same queue VOR's runs work from; you see the answer under Orders), New content (opens Studio with the title and section filled in so you write it yourself) and Dismiss. Ordered suggestions sit at the bottom with Undo. On a campaign you order a shopping edit with 10–30 items. Fetch new suggestions runs the monitoring again (publishing rights). The same suggestions as Insights › Suggestions, which keeps working.

Tags – the rule and the ones that break it

Tags sits under Manage. The rule is that no article is published with an empty tag list – an untagged article is invisible in tag search, in “Read also” and in the reader's way onward. The view shows the tag flora (the CMS's own count), the article links in the top 100, how many articles lack a tag and how many have not yet been fetched into the index.

The untagged articles come newest first. Suggest tags gives up to four suggestions from the tag flora, weighted against headline and body; tick them, add your own if you like, and Set tags writes them to the site's CMS (a new tag is created if it does not exist) and updates the search index at once – the row disappears. Requires publishing rights. The figures come from a cache rebuilt every ten minutes, so the counter catches up shortly after. The same data as Insights › Tags, which keeps working.

Dictionary & people – who and what we write about

Dictionary & people sits under Manage and merges Insights › People and Insights › Dictionary. The tag flora shows what the newsroom has decided it writes about; the dictionary counts words and names from the body text of every article in the index and shows what it actually writes. The crossing is the point: names that recur in the body without their own tag are articles that do not find each other.

At the top, those names with Create the tag – the tag is created in the site's CMS and added to the dictionary, then you set it on the articles in Tags (or in the article). The name cloud shows the fifty most written-about people in alphabetical order, size is the number of articles. The table The two hundred most written about has As tag, In text and the two latest articles; clicking a name searches in Content. At the bottom the most common names and words as bars. The figures come from a cache rebuilt every thirty minutes. The same data as Insights, which keeps working.

The link guard in Studio – does the money get through?

Link guard is the tab next to Buy links. Every hour the check fetches twenty published pages and decodes every buy link as a browser does. Broken = the click can neither get through nor be credited; without article ID = the link works but the revenue cannot be tied to the article. The queue is the pages where a broken link costs money – the whole archive once a day.

The tables show the page, the network, what is wrong, how many links and what the page has earned; Find in Content brings up the article in Studio so you fix the link in the product card. Pages that do not respond are listed separately. The runs at the bottom. The same data as Insights › Link guard, which keeps working; broken links also raise an alarm in Orders.

The editor – every language version side by side

The editor shows the article in one or several languages side by side. Each language has its own status (Approved, In review …), preview and history with every revision. Headline, standfirst, hero (1200×800, with a focal point so the teasers crop right), teaser image (same as the hero or its own) and the body in blocks: paragraph, subheading, image, lists, quote, table (fact box), recipe, place with map, product with buy link, embed, related – and banner: house promotion with an image with a focal point, a short heading, one sentence and a button to our own guide or article, low (under the place cards in a guide) or tall (between sections); editorial, no ad label, never an outbound link. The place block gets a guide button next to the booking button.

The buttons on top: View article (the published page), Improve (SEO suggestions: title, meta description, teaser title, share text, tags – nothing is inserted automatically), Check (the format guard: headline length, standfirst, hero, tags, rights, prices, duplicates), Panel (metadata, tags, categories, sponsored label), Take down, Publish (all language versions). “Re-translate” redoes the language version from the source text.

Tags: “Suggest tags” next to the tag field in the panel – and on the tag row in the check – reads the text and suggests tags you add with one click. A tag you type is taken even without Enter. Tags never block a publication; the check only reminds you. Blocking errors (e.g. no hero) stop the release – but the super administrator and the editor-in-chief can tick “Override the rules” and press “Publish anyway”; it is logged with the errors that were skipped.

Save: everything saves by itself 1.2 seconds after each change – and the button furthest left in the top row tells you where you stand: “All saved” (green tick) or “Save” (brown) when something is unsaved; press it and it saves at once. Under the text: words, reading time and the longest paragraph; a paragraph over 120 words is flagged. The panel's parts (Publishing, Section and template, Tags …) can be moved and hidden with “Customise layout” in the panel header – per person.

Link a word: select the word, press 🔗 “Link” in the toolbar (or ⌘K / Ctrl+K), type the address and press “Link”. Own pages as a path, e.g. /fashion/; other sites – a source such as People – with the full address, https://people.com/… (opens in a new tab, marked nofollow on the site). Even faster: select the word and paste the address. Remove: select the word, 🔗, “Remove the link”. The box tells you when the address does not look like a link; the check warns when a link cannot be shown on the site.

Move blocks – as in the site's CMS: point at a paragraph, an image or a card. Two arrows ▲ ▼ appear in the left margin – one click moves the block one step up or down – and the handle ⋮⋮: hold and drag the block where you want it (a line shows where it lands). Clicking the handle opens the menu Move up, Move down, Duplicate, Remove. Keyboard: put the cursor in the block and press Alt+↑ or Alt+↓. The first time, a tip row above the editor shows how it works – “Show me” lights up the arrows on the first block; × closes the tip.

Images: point at an image in the text → Change image, Edit, Remove. “Edit image” (also on the hero and in the image picker) opens the image editor: Crop (choose Free, 3:2 hero, 1:1, 4:5 or 16:9 and drag the box or its corners), Rotate (↺ ↻ 90°, Flip), Scale (type the width – the height follows – and press Scale; “Hero 1200×800” does it all in one click), Undo/Redo. “Save as new image and use” uploads the result as a new file in the media library and swaps the image – the original is never touched, just like in the site's CMS. Alt and caption: Alt is not shown on the site (a description for Google and screen readers); the text under the image is the Caption. If you type “Photo: …” in Alt with an empty caption, Studio offers to move it with one click.

Everything is saved continuously as revisions. Two people cannot overwrite each other: Studio fetches the latest version before every save and asks you to merge if someone else got there first.

1. New content › choose template and section › write headline and standfirst › choose the hero in the media library.
2. Write the body in blocks; put figures and lists in fact boxes; products in product blocks.
3. Check › fix what shows red › Preview › send to review or Publish (all language versions).

Improve – the suggestions in the editor

The Improve button gives suggestions for the article you are in: SEO title and meta description, teaser title and share text, tags, alt texts for the images, standfirst and Read-also links from your own archive. Every suggestion is shown beside the current one – you choose, edit or dismiss, and nothing is saved until you save. “Copy to new draft” makes a new draft of the article to rewrite, for example for a follow-up.

The languages – 15 in the list, the active ones per title

Studio can publish in 15 languages: English, German, French, Spanish, Italian, Dutch, Portuguese, Polish, Czech, Romanian, Hungarian, Danish, Norwegian, Finnish and Swedish. Which ones are active is set per title in Settings; the source language is chosen per article and every language version gets the same address with the language in front (/en/, /de/ …).

Translation is ordered in the editor and arrives in the target language's template with fact boxes, images and links; the format guard checks and a person releases. A correction in the source text can be carried into every version with one order.

How to make a shopping edit – the shopping edit guide

A shopping edit is a list of products the reader can buy. The template is called Shopping edit: choose it and the shopping edit guide opens by itself and takes you through everything in three steps. You need to know nothing about buy links, programs or advertising labels – Studio handles it.

Every product card gets store, price and a tracked buy link (the affiliate program is chosen by the store; the article's id travels in the link when you publish), the site shows the cards as the usual gallery with Buy buttons and labels the article as advertising. The check stops a shopping edit without a hero or without product cards.

Tip: copy the link from the store's address bar – not from a search engine. The image fetched is the store's product image; for your own, press “Change” on the card › Choose image. The price is fetched as it reads in the store right now – check it before you publish.

An old shopping edit from the site's CMS: open the article and press “Convert to Shopping edit template” in the panel under Section and template. You first get a preview – how many items were found in the CMS gallery (or in the text: subheading + image + price), how many have an image, a link and an affiliate program – and then the article is converted in place, same address on the site: the text stays, the items become product cards after it. The site changes only when you publish. Dead links from old networks are left empty – press Change on the card and paste the store's address to fetch today's price.

An old CMS gallery that is not a shopping edit – tip lists such as “in the morning / during the day / in the evening” with an image and text per part: the panel shows “CMS gallery: 3 parts” under Section and template. “Bring into the text” turns each part into a subheading + image with photo credit + paragraphs at the end of the article, as ordinary blocks you can move and edit. “Remove the gallery” removes the parts. Either way the gallery disappears from the site the next time you publish. Do not use “Convert to Shopping edit template” on such an article – it makes product cards without prices.

1. New content › template Plock › section › working title › Create and open. The guide opens.
2. Step 1: title, standfirst and how many products (5, 8, 10, 12 or your own). Next.
3. Step 2: paste the link to each product. Studio fetches name, image and price and builds the buy link – correct name and price if anything came out wrong. + Add product for more, × removes a row. Next.
4. Step 3: read the summary (tracked links, missing images), let the first product's image be the hero if you like, press Put it in the article.
5. In the editor: drag the cards into the order you want (the grip in the margin), press Change on a card to swap image or text, write a line between the cards if you like. Check › View article › Publish.
6. To start over or add several at once: the Shopping edit guide button in the top row.

The Shopping edit list – all picks as a grid

The Shopping edit list is Studio's counterpart to the CMS gallery – only better. The “Shopping edit list” button in the top row (or ⌘⇧L) shows every product card in the article as a grid with image, name, price, store, buy link and one line of text. Everything you do in the grid is written into the article at once and saved by itself – there is no “Update” to forget.

Several images at once: “Images from the library” opens the media library where you click as many images as you like (the number shows the order) and press “Add N images” – every image becomes a card. Or drag several files from your computer and drop them on the grid (or on “Upload images”): every file is scaled to 1080×1080 in the browser – the whole product visible, white background, never cropped – and uploaded to the library. Drop a file on a card's image and only that image is replaced.

The order: grab the handle ⋮⋮ top left on the card and drag it where you want (a line shows where it lands), or press ▲ ▼. Click a card so it gets a frame and move it with the arrow keys. The text between the cards in the article stays where it is.

The fields: write straight into the card – name, price (as it reads in the store, 149 €), store, buy link and one line of text. Paste the product address into the buy link field and Studio fetches name, image, price, brand and the affiliate program exactly as in the product card; a green chip = tracked link, the article id (epi) is set when you publish. The buy button always carries the short verb (“Buy”) – never “Buy here” – and cannot be changed.

“Paste buy links” takes a whole list: one address per line, card 1 gets line 1, card 2 line 2 and so on – more links than cards make new cards. You can also paste the list anywhere in the grid (outside a field). “Preview as on the site” draws the picks as on the site – three across, image, name, brand · price, Köp.

The guards: a card without an image, an image that is not 1080×1080, two cards with the same image or the same link and a link without tracking are flagged right in the grid – and the same things appear in Check before publishing, together with how many picks the article has and a reminder about the section's preferred store. The counter “N picks” shows in the top row, in the panel under the template and in the content list.

1. Open the article (template Plock, or any template with product cards) and press “Shopping edit list” in the top row.
2. Press “Images from the library”, click every image you want, press “Add” – or drop the files from your computer on the grid.
3. Drag the cards into order (the handle ⋮⋮) or select a card and use the arrow keys.
4. Write name and price in every card. Paste the product address into the buy link field – Studio fetches the rest. Or: “Paste buy links”, one per line, “Hand out the links”.
5. Look at the chips: everything should be green (image, tracked link, no duplicates). Press “Preview as on the site” to see the grid.
6. Press Done. Check › View article › Publish – just as before.

Video, embeds, GIFs and link cards

Three ways to get motion into an article. Your own video: press ▶ Video in the toolbar, pick a video from the media library or upload one (MP4 or WebM, up to 60 MB – a longer film goes on YouTube or Vimeo and is embedded). Give it a poster image, caption and credit. Tick “play muted and loop” and it behaves like a GIF; otherwise the reader gets a player with controls. The video plays in the site's own player – no ads, no leaving the page.

Embed: press ⧉ Embed and paste the address. Instagram, TikTok, YouTube, Spotify, Vimeo, X, Facebook video, Threads and Giphy show inline in the article. Fastest: paste the address on an empty line in the text – it becomes a block by itself, just like in the site's CMS. In the middle of a sentence the address stays an ordinary link.

Link card: for pages that cannot be embedded – a Netflix title, a series on en streamingtjänst, an article. Paste the address and Studio fetches image, title and text from the page and sets the button (Watch on Netflix). The card is a large, clear link that opens in a new tab. GIF: upload as an image (a GIF is an image file) or embed from Giphy.

1. Your own video: ▶ Video › Choose video (or Upload) › Choose poster image › caption and credit › Done.
2. Instagram, TikTok, YouTube …: copy the post's address › paste on an empty line. Or ⧉ Embed › address › Insert.
3. Netflix and other pages that cannot be embedded: ⧉ Embed › address › Fetch › check title and image › Done.
4. The check warns when a video has no poster image and stops an embed from a service that is not approved.

Podcasts, Audiobooks and Books – the gallery templates

Three templates for tips in a row with a buy link per card: Podcasts (episodes or series), Audiobooks and Books. The cards are built like shopping edits – cover, title, creator, one line and the buy link – and Studio finds the programme in the right network when you paste the store's address. The format guard requires a square cover (1080×1080) and alt text.

Series box, countdown and the cards

The series box: a Read-also block whose heading starts with “The whole series:” becomes a series menu on the site – the series' name, “Part 4 of 5”, previous and next part. Write the heading that way, put the parts in order, done.

The countdown: a block counting down to an event (a launch, a programme, a sale) is inserted after the hero on the articles management points out in the “countdowns” setting – no text in the article changes.

The cards: the buy button now always sits in the same place in every product card, however many cards the article has and wherever the ad slots fall. If a card still looks wrong, “Preview as on the site” shows exactly what the reader gets.

Lists, image layout and Key points

Four new tools in the editor, built to be as simple as the rest. All of them are blocks: they move with the arrows in the left margin, duplicate and delete like other cards, and translate into the language versions by themselves (heading, text, points and caption).

Sections (the List template): a top list or “10 ways to …” is built from section blocks – heading, an image if you like, and text. Never write the number yourself: the site numbers the sections in the order they sit (01, 02, 03 …). To count down like a top list (10 … 3, 2, 1) switch “Section numbering” in the panel under Section and template. From three sections the article gets a table of contents by itself (Innehåll / Contents) with a link to every section, and search engines get the list as data. The check reminds you when a list has fewer than two sections – it never blocks.

Image layout: point at an image in the text and pick Normal, Wide or Full width in the row above the image. Normal fills the column as before; Wide becomes 120 percent of the column and sticks out on both sides on desktop; Full width fills the whole screen width on desktop with the caption kept in the column. On mobile all three are the same, so choose wide or full width only for landscape images that can take it. In the editor the choice shows as a dashed frame.

Key points: three short points that give the reader the essentials in ten seconds – put the block right under the lead. Press “Suggest from the text” and Studio reads the article and fills in three suggestions; edit freely and press Save – nothing lands in the article until you save. At most 90 characters per point (the check warns above 120). The box carries the name the template gives it in each language.

Updated and Correction: when you republish an article that is already live, Studio saves the time (you see it in Studio) – but readers see no “Updated” line; that is the publisher's decision. If something was wrong, add the Correction block (date and one sentence about what was wrong and what applies) at the top or the end – the site writes “Correction 21 September 2026: …”, in the site's language.

1. List: New content › the List template › write title and lead › + Block › Section › heading, image (Choose an image from the library), text › Done. Repeat for every section – at least two.
2. Countdown: the panel › Section and template › Section numbering › “N … 3, 2, 1”. The numbers on the cards change at once.
3. Wide image: point at the image › press Wide (or Full width) in the row above the image. Undo with Normal.
4. Key points: + Block › Key points › Suggest from the text › edit the points › Save › move the block to the top with ▲.
5. Correction: + Block › Correction › date and text › Done › Publish (all language versions). The site writes the Updated line by itself.

Best in test, Step by step and Event

Three new templates, each with its own rich block that does the work. All three blocks move with the arrows in the left margin, duplicate and delete like other cards, and translate into the language versions by themselves (headings, texts, pros and cons, comments, steps, captions and button text). The templates are on the templates page with a full example each – open it and see how the article looks on the site before you start.

Best in test (the comparison): one row per product – image from the library, name, rating as stars (half steps are fine), the label Winner, Best price or Best budget, price, store and buy link, plus what speaks for and against it and a short verdict. The buy link takes the same route as in the product card: paste the product address in the store and Studio recognises the store and builds the tracked link; the check warns when a link has no tracking. On the site it becomes a table that stacks on mobile and becomes a grid on desktop, with Buy buttons and the advertising label – and search engines get the products with ratings as data. At least two products; ratings only from a real test.

Step by step (the guide): write what the reader needs, how long it takes (15 min, 1 h 30 min) and how hard it is – then the steps, each with a heading, text and preferably a full-width image. The site numbers the steps by itself, so never write the number in the heading. The Done box is the last thing the reader sees. Google gets the guide as HowTo data and can show the steps directly in the search result. At least two steps – the check reminds you, but never blocks.

Event: name, start and end in the site's time zone (the date picker), the place with address and city (the map links to Google Maps and Apple Maps are built by themselves – or write “lat,lon” in the map field), price, organiser, a short text and the ticket link. The site draws a date badge, the time as “Saturday 31 October 2026 · 18:00–21:00”, a ticket button, “Add to calendar” (a ready calendar file) and a countdown that counts by itself – Happening now while it is on, Ended afterwards. The ticket link is the only link allowed to leave the site in the block (new tab). An event without a valid start time is stopped by the check – that is the only thing that blocks; a start that has passed or a ticket link without https gives a warning.

1. Best in test: New content › the Best in test template › + Block › Comparison › one row per product (Choose an image from the library, name, rating, label, price, buy link, pros, cons, comment) › Add product › Done.
2. Step by step: New content › the Step by step template › + Block › Step by step › You need, time, difficulty › every step with heading, image and text › Add step › the Done text › Done.
3. Event: New content › the Event template › + Block › Event › name, start and end, place, ticket link, price, organiser, text › Done.
4. Move a row or a step with ▲ ▼ in the dialog; move the whole block with the arrows in the left margin.
5. Check › Publish (all language versions). The event countdown and calendar file are computed from the site's time zone by themselves.

Interview, Profile and Review

Two new templates and one extended. Interview is the conversation with a person, Profile is the portrait of them, and Review now has rating, quick facts and pros/cons as its own blocks. All new blocks move with the arrows in the left margin, duplicate and delete like other cards, are never drawn on the site when empty, and translate by themselves – questions, answers, rows, timeline texts, pros and cons and the verdict; labels such as Quick five, Born, Star sign and The verdict always become the same words in every language version. The templates page shows Interview and Profile with a full example each, and the review example shows the new blocks.

Interview: write the title, lead and a portrait as hero as usual, then + Block › Questions and answers. Choose the mode: “Quick five” for short questions with short answers – the site draws them as a tight box headed Quick five – or Interview for the longer conversation, where the question is in bold and the answer becomes running text (blank line = new paragraph). Add, move and remove questions in the dialog. Pull quotes go in as before with Quote. Quick facts about the person (below) tell search engines who the article is about.

Quick facts exist in every template: a compact table in a box – label and value on every row. Write the name of the person (or the title, the product) at the top and the dialog suggests the rows for the template: Born, Star sign, Known for and Currently in a profile or interview; Title, Genre/type, Price, Where and Premiere/released in a review. Press “Fetch from the celebrity data” and Studio fills in born, star sign and known for when the person is among the site’s celebrities – if not, the fields are left empty, and Studio never invents anything. A row without a value is not shown; the check tells you.

Profile: quick facts at the top (they are required – the check warns), then the text, Timeline (a year or date and one sentence per row – the site draws a vertical line with the years), Social channels (write only the username without @ for Instagram, TikTok, YouTube, X and Facebook, and the web address – the site draws buttons with icons that open in a new tab) and “Latest about the person”: add Read also, choose “Automatic – the latest articles with the tag” and the person’s tag (the same as the article’s tag). The site fetches the five latest articles with the tag every time the page is shown, so the list stays current by itself; if no article has the tag yet the block is not shown, and the check says so. Search engines get the profile as a ProfilePage with the person, the birth date and the channels.

Review: Rating (1–5 stars – never an invented one), Quick facts about the title and Pros and cons – what speaks for it in one column, what speaks against it in another, and “The verdict” as a short closing box. The check warns when any of the three is missing but never blocks. With the rating in place search engines get the review as Review data (the stars can appear in Google); the Genre/type row in the quick facts decides whether it is a film, series, book, album, restaurant or product.

1. Interview: New content › the Interview template › title, lead, portrait as hero › + Block › Questions and answers › choose Quick five or Interview › question and answer per row › Add question › Done.
2. Quick facts: + Block › Quick facts › write the name › Suggest rows (for the template) or Fetch from the celebrity data › fill in the values › Done.
3. Profile: New content › the Profile template › Quick facts › text › + Block › Timeline (year and text per row) › + Block › Social channels (usernames) › + Block › Read also › Automatic – choose the person’s tag › Done.
4. Review: New content › the Review template › + Block › Rating › + Block › Quick facts (Title, Genre/type …) › + Block › Pros and cons (for, against, the verdict) › Done.
5. Move a row with ▲ ▼ in the dialog; move the whole block with the arrows in the left margin. Check › Publish (all language versions).

Live report, Quiz and Picture story

Three new templates for what moves: Live report when something happens right now, Quiz when the reader should do something themselves and Picture story when the pictures carry the text. All new blocks move with the arrows in the left margin, duplicate and delete like other cards, are never drawn on the site when empty and translate by themselves – updates, questions, options, results and captions; labels such as Live, Ended, Latest update, Pinned, Try again and Share the result always become the same words in every language version. The templates page shows the three with a full example each.

Live report: write the title, lead and hero as usual, then + Block › Live updates. In the dialog press “Add update” – the time is filled in with now (the site's time zone) and can be changed – write the text (blank line = new paragraph) and preferably choose an image from the library. “Pin” puts an update first regardless of time (good for “How to follow the evening”); the arrows move an update by swapping its time with its neighbour. At the top of the dialog is the button Live / Ended: Live as long as the report runs, Ended when you close it. The site never shows “Updated …” – only “Live” or “Ended” and “Latest update 21:15” from the updates’ times. Every new update is published as usual (Publish (all language versions)) – the reader with the tab open gets it within half a minute without reloading.

Quiz: + Block › Quiz. Choose the type: Personality quiz (every option gives a point to a result – A, B, C …) or Knowledge quiz (tick the correct option in every question). Write the questions with at least two options, preferably an image per question, and the results: in a personality quiz one result per letter (“You are the camel coat” with a text), in a knowledge quiz one result per score range (0–2 correct, 3–4 correct …). At least three questions. On the site the quiz runs in the reader’s browser: one question at a time with “3 of 8”, the result with heading and text, “Share the result” (the phone’s share sheet, otherwise the link is copied) and “Try again”. The check warns when a result can never win or a question has no correct answer.

Picture story: + Block › Gallery, choose the mode Story and add at least four images from the library – every image with a caption and a credit (“Photo: Instagram @name”). On mobile the reader swipes image by image with the counter “4/18”; on desktop the images stack at full width with the counter in the corner. The Grid mode is the gallery as before (two images side by side). Search engines get the picture story as an ImageGallery with caption and credit per image.

Rules that apply: never invent a time – the time is when the update was written; two articles never share an image; only images from the library with a credit; no links out of updates, questions or captions. The check warns (never blocks) when a live report has no updates, an update has neither text nor image, a quiz has fewer than three questions or a picture story fewer than four images.

1. Live report: New content › the Live report template › + Block › Live updates › Add update (time, text, image) › Pin the most important one › Live › Done › Publish (all language versions) – and republish for every new update; Ended when it is over.
2. Quiz: New content › the Quiz template › + Block › Quiz › type (Personality or Knowledge) › questions with options (points to A/B/C or the correct answer) › results › Done.
3. Picture story: New content › the Picture story template › + Block › Gallery › the Story mode › Add image from the library (caption + credit) at least four times › Done.
4. Move an update, a question or an image with ▲ ▼ in the dialog; move the whole block with the arrows in the left margin.
5. Check › Publish (all language versions). The reader’s tab fetches new live updates by itself; the quiz and the image counter run in the browser without login.

Publish, schedule, take down

Publish (all language versions) creates a release: the source language is published on the site's article page and every language version is written to its address (/en/, /de/ …) at the same moment. Choose “Now” or “Choose date and time” (YYYY-MM-DD HH:MM, the site's time zone). A date in the future is scheduled – the article lands in the calendar and goes live by itself. A date in the past publishes the article now but dates it so: it takes its place in the archive, the feed and the section. The date can be changed on an already published article – open it, Publish, choose a date; “Set to now” fills in the current time. Every release is logged; failed ones show in the overview.

Live publishing (Settings) decides whether releases go to the site or stay as drafts in the site's CMS (test mode). Take down removes the article from the site but keeps everything in Studio. The byline is always the newsroom, never a person's name. Prices are corrected without unpublishing – fix in the editor and republish.

View article – a shareable preview without login

“View article” opens the article as it looks on the site, with the language versions as tabs and a switch between phone, tablet and desktop. The link can be shared with someone outside the newsroom – it works without login for three days (at most fourteen if you extend it) and always shows the latest saved version. Nothing is published by someone looking.

Sitemap and RSS – the site tells the world what exists

The site has a sitemap with every article and language version (hreflang and canonical address) and an RSS feed per site and per section, built from Studio's index – they update when you publish, without anyone doing anything. Search engines and feed readers find the new within minutes.

The publishing hook – the page cache empties itself

When you publish, update or take down an article, the site's page cache is emptied the same second for everything affected: the article's section page and its sub-pages, the home page, the language versions and the article itself. You never empty the cache by hand, and readers see the new version at once. The hook is logged like every other action.

Templates – which for what

Choose the template by what you are making, not by its name. Nineteen templates: News (something happened), Feature (long read), List (top list, “how to”), Recipe, Shopping edit (shopping tips with buy links), Place guide (hotels, restaurants, destinations with map and weather), Review, Information page (about us, terms), Best in test, Step by step, Event, Interview, Profile, Live report, Quiz, Picture story, Podcasts, Audiobooks and Books (the last three are gallery templates with buy links).

Every template is shown as it looks on the site, with the site's own images. “Open full example” shows the page on phone, tablet and desktop; “Create a draft from the example” gives you a finished draft to rewrite; “New article with this template” starts empty. The template decides which blocks are required and which sections it fits.

The calendar

The calendar shows everything scheduled and published, day by day, both what lives in Studio and what is scheduled directly in the site's CMS. Click an item to open it. Below the month: the list Scheduled this month. The day's first draft (the morning draft) shows here too.

The media library and rights

All images – the site's entire archive and what is uploaded in Studio – live in the image bank (R2) and are served from there. Every image has a right (press, shutterstock, own, licence, ai), a photo credit and alt text. The tab Rights missing shows what must be sorted out before the image may be used. Search by alt, photographer, source or file name.

Rules Studio keeps: hero exactly 1200×800; two articles never share the same image; product images show exactly that product; Instagram is embedded, never downloaded.

Buy links – VOR Link Generator

Paste the product's address in the store – Studio recognises the store, finds the program in the right network (Adtraction, Awin, CJ, TradeDoubler, Partnerize, Impact …) and builds the tracked link. In an article the product block does the same, with the article's id (epi) set automatically, so every euro can be tied to an article.

Campaigns right now: the networks' latest campaigns per section – material for shopping edits. All programs: everything we are approved for; ✓ = Studio builds the link itself. If a program lacks tracking: paste a ready link from the network once and Studio learns it. The price is always the store's own price on the product page – never a member price.

The links on the site – /ut/ and why they do not look like the network's

The buy link in an article goes through the site's own address (/ut/<group>/<id>) and is forwarded from there to the network with the article's id. That is why the link survives ad blockers that stop the networks' addresses, why clicks can be counted per article and day on our side – and compared with the network's figures – and why a link can be replaced afterwards without changing the article.

The buy-link guard – every hour, all the way to the store

Buy links working is the highest priority. Every hour the guard picks the latest articles with buy links, follows each link all the way (up to six hops through the network's interstitial pages) and classifies it: ok (lands in a store), warning (the store's bot protection answers 403/429 – not broken) or broken. A broken link becomes an urgent order in the inbox (at most one per article and day) and shows in Insights › Link guard; the site never unpublishes for a link.

Prices are compared with the store's own page once a day; a price lower than the store's is flagged, member prices do not count as errors. Networks with an API (for example Tradedoubler) are read directly, so programmes, commissions and link formats arrive without anyone logging in to the portal.

Older articles written before Studio existed get their store links rewritten to tracked links when the page is shown – nobody has to edit them.

The sections

The sections are the site's real ones: each section is its own content type with its own address (/fashion/, /en/fashion/ …), a stable id and names in both languages. The table shows which templates fit where – Recipe in Food & Drink, Place guide in Travel, Shopping edit in Fashion, Beauty, Home … (examples) Sections are changed in the configuration, never in the code.

Section headers and sections on another domain

Every section has the same header: title and description in a band at the top, read from the section's settings in Studio – change the description and the site follows within five minutes. The same look on the theme's sections and your own, so the site stays homogeneous.

A section can publish to another domain than the site's: in the section list the domain stands beside the name (for example the company's own news page or a sister title). Articles in such a section get their own shell, address and sitemap – but are written, translated and released exactly like everything else in Studio. That is how a group's other sites are run from the same newsroom.

The home page – the hero, the menu row and the rotations

The big hero: up to five articles per place – the home page and every section (pick the place with the chips or “More sections…”) – rotate one at a time, switching every ten minutes. Your own pick stays up for 24 hours unless you choose longer; then the rule takes over: the hero always shows the latest from the sections you choose. Release – let the rule decide.

The menu row: the fixed places sit in their own list on top – move them with ↑ ↓ or “Release” to let the section compete; “Pin” on a competing section gives it a fixed place. The rest compete for their place by yesterday's page views (the figure and the bar show for every section, the fixed ones too), recalculated every morning or with “Recalculate now”. “Save the menu row” reaches the site within a minute. The campaign teaser under the top teasers (e.g. a seasonal campaign) is switched on with a date. Pinned on top: a published article can be pinned on top of its section from its page in Studio; the strip shows what is pinned right now.

The shopping rotation: the two store rows on the home page that switch shopping edit every 15 minutes. The latest shopping edits from the chosen sections with saved links rotate (you choose how many). Each edit has a switch (off = outside the rotation) and “Pin” (always in, regardless of age); “Up now · row 1/2” shows what is out and when the next switch happens. Changes are saved with “Save the shopping rotation” and reach the site within a couple of minutes.

The rotation: theme articles allowed to rotate on the home page and in their theme section, by group (e.g. Season, Guides, Series …). The group switch turns all on or off, every row has its own; search finds an article across all groups; six rows show per group, the rest behind “Show all”. Changes are counted, “Undo” restores, “Save the rotation” takes effect within a minute.

Apps – the library in the app

Apps shows every app installed in the app – the same list the app itself draws – family by family: My apps, The checks, Tools and Play. Each card has the name in both languages, the description, the address in the app and the usage: users, views and minutes over the last 7 days, users over the last 30 days and one bar per day for 14 days. “Open in the app” opens the app on the site.

The figures come from the summarised tables (one row per app and day) and are kept in memory for ten minutes – the page never loads the database. The apps that live only on the phone (the shopping list, the recipes, the wishlist, the guides) keep everything locally and send nothing to the server; they are marked “On the phone” instead of showing zeros.

Personal finance – a vertical with its own tools

The personal-finance section is a vertical: its own front page with sub-sections, search, today's figures with source, the finance calendar, the glossary and the quiz – and the personal tools My subscriptions, My month, the mortgage calculator and the watches. Articles are written in Studio as usual (the News, Best in test and Step by step templates fit); the tools are part of the platform and are switched on for the title in Settings.

Reading and trying is open to everyone; keeping your entries needs a sign-in – that is where a visitor becomes a member. The reader's entries belong to the reader: they can be exported and deleted from the account.

The finance calendar: the coming 30 days, the year strip and search, open without sign-in; the newsroom enters dates (tax, payouts, rate decisions) in Studio › Calendar › Finance. The glossary and the quiz are filled in Studio › Glossary.

Rates & savings – the figures the tools show

Under Manage › Rates & savings the newsroom enters the list rates and savings rates that the mortgage card, the comparison table and the calculators show – bank by bank, with a date. The figures are checked against the banks' own pages by the guard; a change reaches the site within five minutes and is logged with who changed it.

Brand and authority pages – fully automatic

Two content types with their own menu rows in Studio: Brands and Authorities. The import runs automatically every hour (facts, offers, plans, rates, price history, customer service) and the pages publish without an editorial gate – management's decision. Every page follows the template: hero with facts, offer, plans, quick facts, compare with others in the category, “Where to find the brand”, Read also.

In Studio you can search, filter by category, section, level and partner, and edit a page by hand – then your text wins over the import until you remove the lock. Partner pages get buy links and offers from the networks automatically.

Orders in Studio – the queue, the replies and the previews

Manage › Orders is the queue of everything ordered from VOR: from the Order card, from Insights and by management. Every row shows status (waiting, running, done, stopped), who ordered, VOR's reply and the link to the preview. The queue is emptied every full hour; an order can be prioritised, commented or cancelled. Alarms from the guards land in the same queue as urgent orders.

1. Create › Suggestions › Order on a card – or Manage › Orders › New order with your own text.
2. Follow the row: waiting → running → done. Open the preview in the reply.
3. Read, fix in the editor and publish – VOR never publishes by itself.

Integrations – Claude works as you

A connection lets Claude (or another assistant) work in Studio as you – with your rights, in your name, and everything shows in Studio at once. No key anywhere: you log in once and press “Allow”. Disconnect at any time – it stops working immediately. See the chapter VOR Chat for the steps.

Images through the connection: the assistant can search the media library, upload a new image from an https address (press room, agency) or a file, replace the contents of an image that already sits at an address, and set an article's hero – always with alt text and credit, never with an image another article has used. Links to other sites in the text are added only when you ask for them.

Team & agents

The newsroom's roles: every account from Insights gets a Studio role (super administrator, editor-in-chief/publisher, administrator, writer), sections and languages. The editor-in-chief publishes to the site's CMS, schedules releases, approves translations and gets e-mail when something awaits review.

Agent accounts: every agent (VOR, the editor-in-chief's agent, the writing agents …) has its own service account with a traceable identity (agent:<name>) and a key shown only once. Default right: create drafts. Publishing and scheduling are granted explicitly per section, template and language. Only the super administrator creates, changes and revokes agent accounts. The OpenAPI button shows the whole API.

The start view and the translation engine

Settings › Start view decides what the overview greets you with: the background image, the weather for up to three cities and the quote of the day. Settings › Translation chooses the engine that makes the language versions (the built-in model or a connected assistant) – the change applies from the next order, and versions already made are left alone.

Settings

Languages: the source language and the active language versions are chosen here; every language version gets its own public address (/xx/). The interface language is your own choice. Publishing: Live publishing on = releases publish to the site; off = test mode, the CMS gets drafts only. CMS sync (WordPress today): changes made directly in the site's CMS are fetched every 15 minutes as a new revision – whatever someone is working on in Studio is left alone. Export: all content, language versions, revisions, media records and releases as JSON; OpenAPI describes the API.

Home – today

The home page in Insights is the most important from every view on one page: today's money against the daily goal, the revenue leak (commission without article id), today's users, Cloudflare 30 days, today's content, what is waiting for you, alarms and health, the world outside. The chips on top jump to each card. Times are in the site's time zone; “Reload” fetches everything again. The menu on the left is the whole panel in four groups: Money, Audience, Content, The world – and To do.

Money – outbound traffic, articles, stores, programs

Outbound traffic: clicks and commission per network and day – affiliate is read, display and native are forecasts. Article revenue: which texts pay off; every buy link carries the article's id (epi), and the share “without sender” is the scoreboard of the archive rewrite. Stores: which stores sell. Programs: every affiliate program we have access to, per network and status, with EPC – search by store or category and apply where it pays. Fetch now forces a new fetch from the networks.

The link guard in Insights – the same view, read-only

The link guard is also in VOR Studio › Buy links › the Link guard tab, with “Find in Content” so the link is fixed in the article (the VOR map); the page in Insights keeps working. Every hour twenty published pages are fetched over the open web, every buy link is decoded as a browser does it and judged by its address. Broken right now, Works but without article ID, Not responding and The runs – with the revenue at stake per page. Fix in the editor (the product block rebuilds the link) and republish; Studio never unpublishes for a broken link.

Orders to VOR – say what you want done

The same queue is in VOR Studio › Manage › Orders (the VOR map); the page here keeps working. Here is everything VOR is working on: what awaits your review, open orders, done. Every row has your order, VOR's reply, the preview (an ordinary page you can send to anyone) and the buttons Approve/Dismiss. Approve puts the article as a draft in CMS:et/Studio – it is published only when someone with the right presses publish. The orders from Studio (the Order card) land in the same queue.

Suggestions – what we should write about

The suggestions are in VOR Studio › Create › Suggestions, where Order becomes an order and New content opens Studio with the title filled in (the VOR map); the page here keeps working. No headline is invented: every suggestion rests on what users searched for, what other newsrooms published in the last week, which campaigns are running and which stores we are already approved with. Campaigns, Ask VOR for something, Business opportunities, Google Trends, Editorial. “Fetch new suggestions” recalculates. The morning draft is the draft that is ready every morning (the time is set per title) – Read and edit, Preview, Publish now or Schedule.

Publishing – publishing, drafts, tags, people, the dictionary

The group is called Publishing – creating happens in VOR Studio. Drafts are now in Studio › Content › Waiting for your yes, Tags in Studio › Tags and People + the Dictionary in Studio › Dictionary & people (the VOR map); the pages here keep working. Publishing: what we published per day and section, and what the whole archive looks like, year by year. The base schedule is one article every full hour 07–22. Drafts: everything waiting. Tags: the tags and what they give. People: who wrote what. The dictionary: the site's own words and how they are spelled.

The world – watch, morning brief, Google Trends

The trend watch reads over a hundred sources around the clock – domestic and international – and shows what others publish, country by country, and which sources are healthy. The morning brief sums up the night. Google Trends: what the world is googling right now, judged against our topics – “never written”, “older than a week”, “covered this week”. All of this is the raw material for Suggestions and for Best ideas in Studio.

Interface language in Insights

The EN button top right switches the menu and headings to English (SV switches back). The choice is remembered per browser. The figures and periods (Today, Yesterday, 7 d, 14 d, 30 d, 90 d, This year, More) are the same.

Real time and the users

VOR Analytics is Cloudflare's count on the server: every user, page view, hour and section is counted – including readers who block scripts, whom Google Analytics never sees. Real time shows the last 30 minutes, updated every fifteen seconds: users in the last hour, page views, active for five full minutes, visits, requests, pages per user, users per minute, page views per device, country, page and section. The shaded bars are the last minutes, filled in afterwards.

The periods on top (Today … This year) apply to the whole page. The same figures are in Studio's overview, in the VOR Insights connection and in Ask VOR.

Own measurements and Google Analytics

The site's own script measures what Cloudflare cannot see: active read time, depth, shares, clicks and sources – per article and section. Google Analytics is shown beside it, with the caveat that GA only sees users who let the script through. How to read the figures: Cloudflare for how many, the own script for how they read, GA for comparison with other sites. Most shared, Games & engagement and the app have their own pages with the same period choice.

VOR Search – what readers look for

VOR Search is the site's search engine – the same hits and order as the search box on the site – and the Searches page in Insights. The search box is the only place where a reader states their need in their own words: a keyword without hits is a reader already on the site looking for something we have not written – the shortest way to an article with an audience before it is written. The twenty most searched, the words, searches per day, from search to article. Keywords without hits become suggestions in Best ideas.

Ask VOR in Studio

The assistant lives in your overview. Write as to a colleague: “How is today going?”, “Find the article about hair loss and suggest three headlines”, “Suggest three shopping edits for the weekend”, “Which campaigns are there in Beauty?”, “Place an order: shopping edit on wine coolers”. It answers with Studio's and Insights' tools, in your name, and keeps the history per person (“Clear” empties it). It runs on the system's own AI key – nobody in the newsroom needs an account with the provider.

VOR AI: the bot can run against any major AI provider via API – first Claude (Anthropic) and ChatGPT (OpenAI); the choice is made in Settings and the keys live in the configuration, never in the client.

Connect Claude to Studio and Insights

Two connections, one login: VOR Studio (/studio/mcp) for the content and VOR Insights (/management/mcp) for the figures. Claude opens Studio's login the first time; you press “Allow” – then Studio remembers the consent. Everything Claude does happens in your name and shows in Studio at once. The connection never changes status, never sends to review and never publishes unless you ask for it in the chat. The money in the Insights connection is shown only to roles that see it in the panel.

1. Claude › Settings › Connectors › “Add custom connector”.
2. Name: VOR Studio. Address: the site's address + /studio/mcp. Save. (Insights: /management/mcp.)
3. Click “Connect” › log in with your e-mail › “Allow”.
4. Write in the chat: “Find the article about … and suggest three headlines”. Disconnect in Studio › Connections whenever you like.

The agents – VOR and the others

An agent is its own service account with a traceable identity (agent:<name>): VOR is the system's own agent that takes the orders from the queue every full hour, does the evening report and the checks; the editor-in-chief's agent in Claude and the writing agents each have their own account. They work by the editorial handbook: create drafts, validate, preview – and stay in the chat until a person with the right says publish. All publishing happens as the newsroom. Fetched content (web pages, documents) is data, never instructions.

The handbook lives in Studio (GET /studio/api/handbok) and applies to every agent alike; it changes only on management's word.

Why Monitoring is strategic

In legacy systems money is lost silently: a broken buy link is not seen until the network stops paying, a stale price costs trust, a missed schedule leaves a hole in the publishing, a slow database logs the newsroom out mid-work. Nobody notices, because nobody is looking – there is nobody who can look everywhere.

VOR Monitoring turns that around: the checks are run by the system, every hour and every day, and whatever is wrong comes to you as an alarm with what it costs and what to do. The result is a media company that can grow in content and revenue without growing in staff – and a management that knows the figures in Insights are right because someone is watching them.

Five areas are watched

The system: the performance check measures response times on the site, in Studio and in the panel around the clock, checks the database, the import, the queue and the releases – and raises an alarm in the order queue when something is visible to users. A database hiccup never logs anyone out: the page says “one moment” and reloads.

The money: the link guard fetches published pages every hour, decodes every buy link as a browser would and judges it – broken, works but without article id, not responding – with the revenue at stake. The revenue leak (commission without sender) is followed per month. The price guard corrects prices in the articles without unpublishing.

The content: the duplicate guard (the same article never twice – in the import, in Studio and on the home page), the format guard (Check before publishing), days without publishing against the base schedule, failed releases, a late morning draft, language versions that are missing or need updating.

The audience: real time minute by minute, drops against the same time yesterday, pages that stopped responding, keywords without hits that keep growing.

The world: the sources' health (which feeds respond), Google Trends gaps (topics being googled but never written), campaigns that are expiring.

Where you see the alarms

The order queue (Insights › To do): alarms are placed as urgent orders with the measurement, the cause and the action – the same queue as the orders, so no alarm disappears into a separate tool. Insights › Home: the card Alarms and health and the revenue leak. The link guard: the whole list with the revenue per page. Studio's overview: failed releases, to do, Waiting for you. The evening report: the day's alarms and what was fixed. Ask VOR: “Are there any alarms right now?” gives the answer from the same data.

How an alarm is handled

1. The alarm says what is wrong, since when, and what it costs (revenue per page, articles affected, visible to users or not).
2. Open what is pointed out in Studio (the article, the product block, the release) and fix it – never unpublish, never delete.
3. Republish or rerun the release. The guard checks again on its next run and closes the alarm when it is green.
4. System errors that cannot be fixed in Studio go to VOR, which puts the cause and the action in the order queue and in the evening report.

The Monitoring view in Studio – the guards and their switches

Workspace › VOR Monitoring shows the sixteen guards with status, last run and number of alarms: duplicates, format, prices, buy links, the schedule, source health, response times, the page cache, images, language versions, tags, the sitemap, the feeds, the import, the publishing pace and the external systems. Every guard has a switch – only the super administrator turns one off or on, management and the editor-in-chief see. A guard that is off shows as off, never as green.

1. Workspace › VOR Monitoring › the guard › the switch (super administrator).
2. Write why in the box – the reason is logged and shows in the evening report.
3. Switch it back on when the cause is fixed; the guard runs at its next turn.

The sources' health and the world

The trend watch reads over a hundred sources around the clock and Monitoring checks that the feeds work: sources with a working feed, sources without a readable feed, sources not yet tried. If an important source stops responding it shows the same day, and the suggestions never rest on an empty base.

SEO optimisation

Three layers. Before the article: the trend watch's suggestions are scored on search volume, competition and campaigns (Best ideas in Studio, Suggestions in Insights). In the article: Improve gives an SEO title (at most 70 characters), meta description, teaser title, share text and tags – you choose, nothing is inserted by itself; Check stops clickbait headlines, missing standfirst, wrong hero size and missing tags. After: Searches shows what readers look for and do not find, and Google Trends what the world is googling.

The guards – in brief (the full picture in the chapter VOR Monitoring)

The duplicate guard: the same article is never published twice – the import matches against what Studio already created, and the home page never shows the same article in two places.

The link guard: every hour buy links on published pages are checked; the body never links out (only to the site itself); external addresses only in product blocks, sources and bookings.

The price guard: prices are the store's own price; a wrong price is corrected in the editor and republished – never unpublished.

The format guard (Check): headline at most 70 characters, standfirst first, hero 1200×800, a subheading every third–fifth paragraph, at least three tags, right and credit on every image, two articles never share an image.

The performance check: response times are measured around the clock and raise an alarm in the order queue when something is visible to users.

What runs by itself

The trend watch reads the sources around the clock. The morning draft: the day's first draft is ready in the morning, time per title. The morning brief sums up the night. The order queue is emptied every full hour by VOR. CMS sync every 15 minutes. The menu row is recalculated every morning. The big hero switches every ten minutes. The link guard every hour. The evening report to management (time per title). Translation into the language versions is done by the AI engine when the source text is ready; the image bank (R2) receives every new image and serves the whole archive.

Publish an article in every language version

1. New content › template and section › headline, standfirst, hero (1200×800, focal point).
2. Body in blocks. Figures in a fact box, products in product blocks, places in place blocks.
3. Improve › choose SEO title, meta description and tags. Check › all green.
4. Preview on phone. The language versions: Re-translate if needed, read through.
5. Publish (all language versions) › Now or a time. Done – the article shows in Content as Published and in the calendar.

Order a shopping edit from an agent

1. Overview › Order › Shopping edit › subject, angle, section › Order.
2. The draft shows under My orders (“Ready for review”) – open it.
3. Check: prices, stores, images of the right product, sponsored label. Fix.
4. Publish (all language versions) – or send back with a comment.

Change the big hero

1. Home page › choose the place (Home page, Fashion …).
2. Add to the rotation › choose the article › validity (24 h or longer).
3. Release – let the rule decide when you want the hero to take the latest from Fashion, Beauty or Film & TV again.

Fix a price or a broken buy link

1. The link guard in Insights (or Check in the editor) points out the page.
2. Open the article in Studio › the product block › fix the price or paste the product address again.
3. Publish (all language versions). Never unpublish for a price.

See how the day is going

1. Studio › Overview: the key figures against yesterday at the same time.
2. Insights › Home: the money against the daily goal, the leak, what is waiting.
3. Or Ask VOR: “How is today going? Short.”

Give a colleague access

1. Insights › Users › Create login (temporary password shown once).
2. Studio › Team & agents › choose Studio role, sections and languages › Save.
3. The colleague logs in at /studio/ – the overview carries their name.

Give an agent a key and rights

1. Team & agents › New agent account › name, sections, languages, templates; publish/schedule only if it really should.
2. The key is shown once – put it in the agent's configuration (never in a chat or a document).
3. Revoke at any time; create a new one when needed. Calls are shown per agent.

Get help – three ways

Ask VOR on the overview answers straight away about the state, the figures and the content – as you, with your rights. Orders (under Manage) is the request: write what you want done or what is wrong, ideally with a screenshot, and VOR takes it on the next run and answers on the same row. The chat with VOR is the third way – what you write there becomes orders and releases, and everything is logged in Orders so nothing is forgotten.

What is live right now is in the menu footer (VOR Studio, the version number and the date) and in Settings › What's new. VOR Monitoring shows operations: the guards, the alarms and the database pulse.

The overview: hidden blocks and the layout

Every block on the overview can be moved and hidden – and brought back. The order is saved per person, so nobody else's view is affected.

Every view: the same applies to Home page, Monitoring, Settings and the editor panel – “Customise layout” in the top row, blocks move with the arrows or the grip, hide with ✕ and come back via “N hidden blocks +” or the dashed tile. The order is saved per person and view.

Key figures: a hidden figure – Loyalty cards, say – is never gone. Next to “Show more figures” there is “N hidden figures +”; press it and customise mode opens with the hidden ones as dashed tiles at the end of the grid – press “+ Show” on one and it is back. “Reset the figures” puts them all in the default order.

1. Press “Customise layout” at the top of the overview. The blocks get dashed frames with arrows.
2. Scroll to the bottom. The row “Hidden blocks” lists what you hid – press the block's name (for example “Key figures +”) and it comes back.
3. “Reset layout” in the same row puts every block in the default order.
4. Press “Done” at the top and the frames disappear.
5. Move a block: drag the grip (⋮⋮ top right on the block) or use the arrows in customise mode.

Account and login

One account system: VOR Insights › Settings & help › Users. There you find New password, Add code in the app (two-factor), Lock, Log out everywhere and Remove – and invitations for new people. The same account applies to Studio. What a person may do in Studio (role, sections, languages) is set in Studio › Team & agents, which also handles the agent accounts; an agent key is shown once only when it is created.

If you are logged out unexpectedly it is usually an expired cookie – log in again with the button in the e-mail. If you see “One moment”, the database is busy; wait a few seconds and try again, nothing is lost.

When figures are missing or look wrong

Affiliate revenue comes from the networks with a delay – today can show 0 € in the morning and fill in during the day. Cloudflare's figures (page views, readers) are counted per day and fetched every five minutes. Some views – Tags, Dictionary & people, Link guard, the campaigns – come from a cache rebuilt every 5–30 minutes, so a change shows with a small delay. The key figures are always compared with the same time in the previous period: a Tuesday morning against Monday morning.

If the page looks odd right after a new release: reload the page (on Mac ⌘+Shift+R, on Windows Ctrl+F5) to fetch the new style. If that does not help – send a screenshot in Orders.

Publishing that is stopped

The check before publishing stops what breaks the rules: tag missing, hero missing or too small, the same main image as an article in the last 30 days, the same topic as in the section in the last week, an external link in a banner button. Fix it in the article and run the check again. In test mode (the badge under your name) the CMS only gets drafts until the mode is switched on in Settings. VOR never publishes by itself – every article requires that a person has read it and pressed the button, in Studio or under Waiting for your yes.

Report a problem

1. Take a screenshot of what looks wrong.
2. Orders › New order: write what you did, what you expected and what happened. Attach the screenshot via the chat with VOR if you like.
3. VOR answers on the same row, often with a preview of the fix before it goes out.
4. The guards raise alarms in Orders by themselves: broken buy links, duplicates, the database pulse, pages that do not respond.

Studio 2.5.36–2.5.43

Fifteen languages in the list (2.5.43). The gallery templates Podcasts, Audiobooks and Books (2.5.41). Tracked buy links in every template and editing of older shopping edits (2.5.38–2.5.40). Programme status per network and square covers 1080×1080 (2.5.37). Shopping edit visibility per rotation (2.5.36). On the platform at the same time: personal finance as a vertical, brand and authority pages, the section header, the publishing hook, the hourly buy-link guard and networks via API, the series box, the countdown block, the buy button's fixed place in the cards, sections on another domain.

Studio 2.5.21–2.5.35

The shopping edit list – every shopping edit as a grid (2.5.35). Live report, Quiz and Picture story (2.5.33). Interview, Profile and Review (2.5.32). Best in test, Step by step and Event (2.5.30). Lists, image layout and Key points (2.5.29). Language version outdated and Re-translate (2.5.28). Move blocks (2.5.25). Backdated publishing and “Set to now” (2.5.23–2.5.24). Convert old shopping edits and galleries (2.5.22–2.5.24). Video, embeds, GIF and link cards (2.5.21).

Studio 2.0–2.5.20

Studio 2.0: the editor with source language and language version side by side, the templates, the check, the calendar, the media library, buy links, sections, the home page, apps, the integrations (Claude works as you), the agents and the Manual. The VOR map: what you do lives in Studio, what you read off in Insights – Suggestions, Orders, Tags, Dictionary & people and the Link guard moved into Studio.

A–Z – 89 terms

Agent

A service account (agent:<name>) with a traceable identity that writes drafts on order; default right drafts, publishing only if explicitly granted.

Agent key

The key an agent signs in with – shown once when created, can be rotated and revoked in Team & agents.

Alt text

The description of an image for screen readers and search engines; required by the format guard, not shown on the site.

The app

The site installed on the reader's home screen, with the tools, the games, the guides and the loyalty card.

Banner

House promotion in the body: an image with a focal point, a short heading, one sentence and a button to an internal path. Editorial: no ad label, no affiliate link.

Order

A job placed in your name from the Order card or from Orders – lands in the order queue and is answered by VOR with a draft and a preview.

Watch (reader's)

The reader's own watch in the tools – a rate, a price, a decision – sent as e-mail or push, without advertising.

Image bank

The media library's storage (object storage) where every image lives in the original and is served in the right size.

Picture story

A template where the reader swipes image by image, each with a caption and a credit.

Block

The building blocks of the body: paragraph, subheading, image, list, quote, table, fact box, Key points, correction, comparison, step by step, event, Q&A, quick facts, timeline, social channels, rating, pros & cons, live update, quiz, gallery, video, embed, link card, recipe, place, product, related, series box, countdown, banner.

Urgent order

An order placed in the queue by an alarm – for example a broken buy link – that goes before the ordinary ones.

CMS

The site's existing publishing system (for example WordPress). Studio publishes through it from day one and syncs changes every 15 minutes until the site moves fully to VOR.

Daily goal

The revenue goal per day in Insights that the money is measured against.

Key points

The bullet box at the top of an article – at most 90 characters per point; the name follows the template's language.

Deep link

The network's link straight to the product page in the store, with tracking.

Duplicate guard

The guard that stops the same article twice and the same hero on two articles within 30 days.

The editor

The page where the article is written: source language and language version side by side, the blocks, the panel, Check, Improve and Publish.

EPC

Earnings per click – the commission divided by the clicks, per programme or article.

epi

The article's id in the buy link – lets clicks and commission be tied to that very article.

Fact box

The block for facts, figures and lists in a frame – same style as Good to know.

Focal point

The point in the hero that must always be visible when the image is cropped in teasers and on mobile.

Format guard

The guard that checks headline length, standfirst, hero 1200×800, alt texts, tags and the template's requirements before publishing.

Improve

The button in the editor that suggests SEO title, meta description, teaser title, share text, tags, alt texts, standfirst and Read also – nothing is saved until you save.

Preview

The article as it looks on the site before it is published – in Studio, in the suggestion's reply, or as a shareable link without login (View article).

Loyalty card

The reader's card in the loyalty programme: Bronze from the start, Silver and Gold by points, Black by invitation or earned – a level never drops.

Suggestions

What we should write about: business opportunities, editorial ideas, trends and campaigns – with Order on every card.

In review

The status between draft and approved: someone with the right reads and approves or sends back.

Interface language

The language of Studio's menus and buttons – your own choice, independent of the articles' language.

The handbook

The editorial handbook every agent works by; changed only on management's word.

Hero

The article's main image, 1200×800, with a focal point – the same image in the teaser and the share card.

Embed

A post from a social channel or a player placed in the body with its address.

Standfirst

The short text under the headline that sums up the article – required by the format guard.

Integration

Claude (or another assistant) signed in to Studio or Insights as you, with your rights, logged under your name.

Check

The button that runs the guards' checks on the article before publishing and shows what must be fixed.

The evening report

The day's summary to management – revenue, traffic, most read, published, alarms – at the time the title has chosen.

Source health

The check that the trend watch's sources answer and deliver – dead sources raise an alarm.

Source language

The language an article is written in; the language versions are translated from it.

Buy link

The tracked link to a store, built by Studio with the article's id; the button is always the short verb Buy.

Buy-link guard

The guard that every hour follows the buy links all the way to the store and raises an alarm if one is broken.

Alarm

A deviation found by a guard – shown in Studio, in Insights, in the evening report and as an urgent order.

Live report

A template for events in real time: updates with time, the most important pinned, the reader's tab updates by itself.

Link card

An address on its own line that becomes a card with image, heading and description.

Link guard

The view in Studio (and Insights) that shows the buy links' health article by article – what is costing money right now.

Template

The article type that decides which blocks are required and how the page looks – nineteen of them, from News to Books.

MCP

The standard that lets an assistant (Claude, ChatGPT) work in Studio and Insights through the integration.

Member

A reader who has signed in – keeps their entries in the tools and has a loyalty card.

The menu row

The sections at the top of the site: fixed places and places that compete on yesterday's page views.

Monitoring

VOR Monitoring – the guards that watch the system, the money, the content, the audience and the world around the clock.

The morning brief

The night's summary to the newsroom: what happened, what went out, what is waiting – at the time the title has chosen.

The morning draft

The day's first draft, written by VOR from the suggestions and ready in the morning – Read, fix, publish.

Countdown

The block that counts down to an event, inserted after the hero on designated articles.

Taken down

The status of an article removed from the site but kept in Studio.

The trend watch

The module that reads hundreds of sources around the clock and turns them into suggestions, the morning brief and trends.

OpenAPI

The description of Studio's API that developers and assistants read – /openapi.json.

The panel

The tab in the editor with metadata: SEO, tags, categories, sponsored label, section and template.

Partner

A brand with an agreement: the partner page gets offers and buy links from the networks automatically.

Shopping edit

The template for shopping tips with buy links – products in a row, each with image, name, price, store and Buy.

Shopping edit list

The grid with every product in an article – move, hide, pin and edit without opening the cards.

The performance check

The measurement of the site's response times and weight, page by page, with an alarm when something gets slow.

Price guard

The guard that compares the prices in the articles with the store's own page once a day; prices are corrected without unpublishing.

The publishing hook

What empties the page cache when you publish: the section, the home page, the language versions and the article – the same second.

Teaser

The article's card on the home page and in the section: hero, headline, standfirst.

Real time

Readers right now, every fifteen seconds, counted on the server – no script measurement needed.

Release

The publication of an article with its language versions – now or scheduled; every release is logged.

Revision

Every saved version of an article; the history shows them all and an older one can be restored.

Rotation

Articles or products that take turns in one place – the hero, the store rows, the theme groups – with switches and Pin.

Correction

The block that dates and describes a change in a published article; the site writes the Updated line.

Section

The site's department with its own address (/fashion/, /beauty/ …), its own id, names per language and its own templates.

Section header

The band at the top of every section with title and description from the section's settings.

Series box

The Read-also block whose heading starts with “The whole series:” and becomes a series menu on the site.

The page cache

The site's stored pages served without reading the database; emptied by the publishing hook.

Live publishing

The setting that makes releases reach the site; off = test mode (drafts only in the CMS).

Quick facts

The block with short facts in a row – figures, dates, names – at the top of a profile or an event.

Sponsored

The label for articles with affiliate links – set in the panel and shown on the site.

Language version

The article in a language other than the source language, on the same address with the language in front (/en/, /de/ …).

Super administrator

The role that may do everything – including turning guards off, creating agents and changing settings.

Test mode

Live publishing off: releases stay as drafts in the CMS; the badge shows under your name.

Two-factor

The second code when signing in to Insights – required for management's views.

Orders

The queue of orders to VOR with status, reply and preview – in Studio under Manage.

No byline

The byline is always the newsroom, never a person's name – everything is published as the newsroom.

Draft

An article that is not published; saved by itself and found in Content › Drafts.

Guard

An automatic check that runs around the clock and raises alarms – duplicates, format, prices, buy links, the schedule, sources and more.

Vertical

A title within the title: its own front page, sub-sections, tools and membership hook – for example personal finance.

View article

The shareable preview without login, with the language versions as tabs.

VOR

The system's own agent that takes the orders from the queue, makes the morning draft, the brief, the evening report and the checks – never publishes by itself.

The VOR map

The rule for where things live: what you do in Studio, what you read off in Insights.

Waiting for your yes

The tab in Content with everything waiting for a person with the right to publish.

Override the rules

The right to publish despite a stop from a guard – always logged with who and why.

Monitoring view

The Insights view for management with alarms, health and what is costing money right now.