CloudScript.io News

Tech Adoption Radar 2.5: build a radar in a table

2026-09-07T00:00:00+00:00

Version 2.5 of Tech Adoption Radar for Confluence is now live on the Atlassian Marketplace. The release changes how a radar is authored: until now the macro took its blip list as a block of CSV or radar.js JSON text, which suited people who already kept their radar in a file and left everyone else assembling one first. The macro editor now opens in a Table View, where a radar can be built without leaving Confluence.

Table View

In Table View each blip is a row with its name, ring, quadrant and movement, and a row expands to hold a description and a link. Rows can be typed in one at a time, pasted straight from a spreadsheet (the editor recognises the paste and reports how many rows it added, flagging any ring or quadrant value it does not recognise), or loaded by uploading a CSV or JSON file. The table enforces the 400-blip ceiling as data is entered, and a paste or upload that exceeds it is truncated to the first 400 rows with a warning naming the number discarded.

The previous editor is still there as Text View, one click away, for anyone who prefers to paste CSV or radar.js JSON directly. Both views read and write the same stored source, so a radar built in one can be edited in the other, and macros inserted with earlier versions keep rendering and editing exactly as before.

Images that read on their own

A radar downloaded as an image now carries the numbered legend beneath the chart, grouped by quadrant and ring, so the picture can be dropped into a slide or a document without the page it came from.

Crowded quadrants and accessibility

Below the 400-blip limit a quadrant can still hold more blips than can be drawn without overlap. The radar provides a detailed warning when some items cannot be displayed, while retaining these blips in the numbered legend beneath the chart. The release also includes accessibility fixes to the authoring surface, including a live blip count that screen readers announce as rows are added.

What has not changed

The app still requests no permissions and sends nothing outside Atlassian: the blip list is stored in the macro on your page and the chart is drawn in the reader’s browser. This release makes no change to the app’s scopes or data handling, so existing installations update automatically and no administrator action is needed.

A two-minute demo of the app is on the user guide and on YouTube.

MSG/EML Email Viewer for Confluence: read the attached email on the page

2026-09-02T00:00:00+00:00

MSG/EML Email Viewer for Confluence is now live on the Atlassian Marketplace. An email filed on a Confluence page is often the documentation itself, whether an approval, a client instruction or a piece of incident correspondence, and until now it has been a download link: reading it meant saving the file and opening it in a mail application. This macro renders the attached .msg or .eml file on the page as an email card, under the page’s own permissions, making the email contents more readily accessible to anyone who can already see the page.

The email card

The card shows the subject, sender, recipients, date and body, with inline images in place. Message attachements are displayed as tiles with a download option available for each. Setup is one screen: users can choose to display the Confluence page’s existing .msg and .eml attachments or use a drag-and-drop area to upload an email file (50 MiB attachment cap).

Rendered afresh, from your own Confluence

Your selected email file is read and parsed again on every page view, so the card shows what the attached file contains at the time of viewing. Remote images in a message body are blocked until the reader chooses to load them. Where a message cannot be rendered in full the card displays plain english error messages describing what happened rather than silently omitting data.

Permissions and data handling

Email files are read from your own Confluence page, remain only on Atlassian’s platform and are parsed in the reader’s browser inside the macro’s sandboxed iframe. The macro stores only the attachment’s id, its filename and an optional user-provided label. The app operates no server, has no store of its own, declares no external network destinations and holds no Forge app storage. It requests two Confluence permissions, one to read the page’s attachments and one to attach a file you upload; the privacy policy, terms and a data processing agreement are published alongside the guide.

Read more in our User guide.

NikoNiko Calendar 3.0: on Forge, with a team trend row

2026-08-06T00:00:00+00:00

Version 3.0 of CloudScript.io NikoNiko Calendar is now live on the Atlassian Marketplace. The app first shipped in mid-2020 on Atlassian Connect; version 3 rebuilds it on Atlassian Forge, so entries are now stored in Forge storage inside Atlassian’s infrastructure rather than on a server we operate. The rebuild also carries the first functional changes to the calendar in some years, each of them a response to how teams actually use a niko-niko calendar rather than a new idea about what one is.

Team trend row

A line beneath the grid plots the team’s average entry for each day of the window. Each point is sized by the share of the team that responded that day, so a high average from two people out of nine reads differently from the same average from all nine, and the line breaks on days with no responses rather than interpolating across them. The trend row is on by default and can be switched off in the macro’s configuration.

User can now contribute to multiple calendars

Entries are now isolated to the calendar in which they were recorded. This means that a user can be added to two or more calendars and record a different value on each calendar for the same day. An new optional label above each calendar can be user to specify a topic that the calendar refers to, for example a team can now publish two calendars on the same page, the first asking “How is the merge going?”, and the second asking “How is the sprint in general?” and team members provide a different answer on each calendar. Likewise user working across multiple teams are able to provide different responses in a team calendar for each team.

Deleting entries for better data management

All users can now delete their own entries from the entry picker. They can do this either for a single day on one calendar, or for their entire history across every calendar. Additionally, Confluence site administrators gain a Niko Niko data management screen listing every account for which the app holds entries, with the option to delete all entries for a person or all entries older than a chosen date. The accounts on the data management screen are drawn from the app’s own storage, rather than the site directory, so that administrators are able to delete data for users who have left the organisation or no longer have a Confluence account.

What has not changed

Pages that already contain the macro keep rendering without reconfiguration. The calendar remains sized for a single team, with the same three-or-five-point scale and the same smiley, square and cat themes. Because the app now runs on Forge and requests granular Confluence scopes, administrators will be asked to approve the new version when it replaces the Connect app on their site; the app’s privacy policy describes exactly what is stored.

Tech Adoption Radar for Confluence: a tech radar from a pasted blip list

2026-07-21T00:00:00+00:00

Tech Adoption Radar for Confluence is now live on the Atlassian Marketplace. Technology radars in the Thoughtworks style are usually built with a separate tool and pasted into Confluence as an image, which goes stale the moment a blip moves. This macro draws the radar from a blip list stored in the page, so updating the radar means editing the list.

Two formats, one radar

The macro accepts the Thoughtworks build-your-own-radar CSV convention and the Zalando radar.js JSON dialect, so an existing radar kept in either format pastes in without conversion. Each blip carries a movement marker, and a numbered legend grouped by quadrant and ring sits beneath the chart. The four quadrants can each take a colour from a curated palette of Atlassian accents, and a blip’s link opens in Confluence when it points at the same site.

Export and download

A page exported to PDF or Word carries the radar as a structured table by quadrant and ring rather than a blank space, and a Download as image button on the macro produces the chart itself, drawn client-side, for use in a slide or document.

Permissions and data handling

The radar is drawn in the reader’s browser from the list stored in the macro. The app requests no Forge scopes, declares no egress and stores nothing beyond the page content, so there is nothing for an administrator to review beyond the install itself.

Read more in our User guide.

Cloudscript Renderer for MCP Documentation: server.json as readable Confluence pages

2026-07-17T00:00:00+00:00

Cloudscript Renderer for MCP Documentation is now live on the Atlassian Marketplace. Teams standing up Model Context Protocol servers, and particularly internal servers that appear in no public registry, tend to document them as a JSON dump in a code block or not at all. This macro takes that JSON as pasted and renders it as documentation on the Confluence pages developers, security reviewers and platform teams already read.

What it renders

Paste an MCP Registry server.json document or a tools/list result into the macro and it detects which you pasted, accepting a bare result or one wrapped in a JSON-RPC envelope. A server.json renders as a header with name, description and schema link, package tables with environment variables (secrets badged as such) and an install command. A tools/list result renders as one capability card per tool, with parameter tables, annotation pills whose tooltips explain what each hint means, and a table of contents. It is purpose-built for MCP: not a generic JSON viewer, and not another MCP server product.

Your code stays the source of truth

The page holds the pasted JSON rather than a rendering of it, so editing the source in the macro re-renders the Confluence page and every server documents identically. The macro exports to PDF and Word as native content.

Permissions and data handling

The app requests no Confluence or Jira scopes, declares no egress and has no app-side storage; it works only on the text pasted into its own macro configuration, which is parsed and drawn in the reader’s browser. Control characters such as bidirectional overrides are removed from the rendered text with a notice, and the stored source is left unchanged. Source is capped at 512 KiB.

Read more in our User guide.

Cloudscript Typst Renderer: Typst documents and mathematics on the page

2026-07-15T00:00:00+00:00

Cloudscript Typst Renderer is now live on the Atlassian Marketplace. Teams that need mathematics in Confluence commonly maintain a LaTeX-and-screenshot workflow, in which a formula is typeset elsewhere and pasted in as an image that nobody can edit or search. This macro replaces the screenshot with source: paste Typst into the macro, and the document is compiled and drawn on the page each time it is viewed, so an edit to the source is what the next reader sees.

What renders

Typst covers the same ground as LaTeX, and the macro renders the full document rather than formulas alone: headings, prose, tables and code blocks alongside mathematics set in Typst’s own maths font as vector output that can be selected and zoomed. The bundled sample shows the Cauchy-Schwarz inequality, a Gaussian integral, a matrix and Maxwell’s equations on one page with prose and a highlighted code block. The macro is found by typing /typst in the editor, and the macro browser also returns it for “latex”, “math”, “equation” and “typesetting”.

Compiled in the browser

The Typst compiler runs as WebAssembly in the reader’s browser rather than on a server, so your data is never sent to Cloudscript or to any third party. As such, the app requests no Confluence scopes, declares no egress and stores nothing outside the macro on your page; its one content-security directive exists solely to instantiate the WebAssembly module.

Limits

The above security posture means a page exported to PDF or Word cannot carry the rendered output, since rendering happens on the live page; the export carries the Typst source in a captioned code block instead. This first release renders self-contained documents only, without package imports (@preview), image() or #include, and caps source at 64 KiB with a 10-second compile budget, which a size meter in the editor tracks as you paste. The app is an independent integration, not affiliated with or endorsed by Typst, and bundles typst.ts and the Typst fonts under their open licences.

Read more in our User guide.

Page Sharing for Confluence: read-only pages across Confluence Cloud sites

2026-07-06T00:00:00+00:00

Page Sharing for Confluence is now live on the Atlassian Marketplace. It addresses a gap that consultancies, suppliers and their clients usually fill with exported PDFs or guest accounts: a page maintained on one Confluence Cloud site can be delivered to another site as a real, read-only Confluence page in the recipient’s own page tree, refreshed each time the publisher edits the original. When the engagement ends, the publisher withdraws sharing and the replicas are removed.

How a page is shared

An editor shares a page from its menu and receives a reusable subscription link. On the receiving site, a user subscribes by pasting that link, and the page appears as a replica marked with a byline naming its source. Sharing works in both directions once the app is installed on both sites, and every subscription is revocable by the publisher.

Admin control at both ends

Sharing is admin-approved: a Confluence administrator on the publishing site enables sharing space by space and maintains an allow-list of partner sites, and a subscribe request from a site not yet on the list lands as pending for approval. Both checks are repeated on every push, so a partner removed from the allow-list stops receiving updates immediately.

What leaves your site

Replicas carry native content only: text, headings, lists, tables, code blocks and links. Images, attachments and macros are stripped before anything leaves the publishing site, a deliberate control rather than a limitation to be lifted later. The app runs entirely on Atlassian Forge, with compute and storage on Atlassian infrastructure, and the only network destination is the app’s own Atlassian-hosted endpoint; the share link, which carries the token, is handed to the subscriber out of band rather than over the app’s channel. On the publisher’s side the app only reads the shared page and on the subscriber’s side it only writes the replica. The only personal data it stores is a user identifier.

Read more in our User guide.

Mermaid Diagrams 2.8: rebuilt on Atlassian Forge

2026-06-30T00:00:00+00:00

Version 2.8 of CloudScript Mermaid Diagrams for Confluence is now live on the Atlassian Marketplace. The app first shipped in November 2018 on Atlassian Connect, and this release replaces that codebase with one built on Atlassian Forge, Atlassian’s own hosting platform for cloud apps. This change means that the diagram is now drawn in the reader’s browser from the source stored in the macro, and the app runs on Atlassian’s infrastructure rather than on a server we operate.

Mermaid 11

The rendering engine moves from Mermaid 10 to Mermaid 11 (11.15.0 in this release), so any diagram type or syntax feature in the current Mermaid specification renders in the macro. In addition, the app supports the ELK layout engine for flowcharts and other node-based diagrams, selected through the diagram’s frontmatter (config: layout: elk), which produces tidier routing on larger diagrams than the default layout. The macro’s configuration panel keeps its three settings: the diagram source, a theme chosen from Default, Forest, Dark and Neutral, and a checkbox that prints the source beneath the rendered diagram.

Existing diagrams keep working

Pages created with the Connect version continue to render. The new macro reads the diagram source stored by the older version, so nothing needs re-entering and no page needs editing. Diagrams are also included in Confluence’s Export to PDF as they appear on the page.

Export to Word and Export to Email

Both are temporarily unavailable while they are reworked for Forge. They are in progress and will return in a later release; until then a page exported to Word will not carry its diagrams, so keep the Connect-era expectation in mind if Word export is part of your workflow. Where an export is required, use Confluence’s Export to PDF.

What has changed for administrators

Because the app now runs on Forge, Confluence administrators will be asked to approve the new version when it replaces the Connect app on their site. The app does not send your diagram source anywhere outside of Atlassian, since rendering happens in the browser. Your data is only stored in the macro on your Confluence page.

Read more in our User guide.