Topol Plugin Changelog

This changelog records what changed in Topol Plugin, when, and why it matters. A new entry goes out roughly each month.

Why we keep a changelog

A transparent, chronological log helps developers:

• Discover value
  Spot new features as soon as they land in the Plugin and start using them.

• Follow quality improvements
  See how recent tweaks improve the developer and user experience.

• Track resolved issues
  Know which bugs are fixed, so no time goes to troubleshooting something already solved.

Changelog structure

Each entry sits under one of these topic headers, so the nature of the update is clear at a glance:

• New Features (What's newly possible in Topol Plugin?)
  Brand-new features or options added to Topol Plugin.

• Improvements (What's better now?)
  Enhancements to existing functionality.

• Bugfixes (What's no longer broken?)
  Resolved bugs, glitches, and user-reported issues.

How each entry reads

Every New Feature and Improvement follows the same flat shape, so the reader moves through it in one pass without navigating sub-headings:

1. A bold lead sentence states what the feature is and does.
2. A short paragraph explains why it matters, only when the value is not already obvious from the lead. Self-explanatory additions skip it.
3. The setup, when there is any, flows straight after: a sentence plus a code block, closed by a link to the full documentation. A code fence and a docs link are self-labeling, so no "How to enable" heading is needed.

For a large, multi-part feature, a bold inline lead-in (for example, Turn it on followed by the setting) can flag the setup without adding a heading. The goal is one continuous read per entry, matching how Improvements and Bugfixes already read.

Bugfixes stay a plain bulleted list, one line each, tagged by module.

Module tagging rules

The Topol Plugin is organized around two core modules:

• Email Editor
• Landing Page Editor

Every feature belongs to one of these two modules and is tagged accordingly, so its area is easy to place:

EmailEmail EditorLanding PageLanding Page Editor

Feature tagging rules

Every module tag is followed by one or more feature tags that specify the affected area:

AccessibilityAccessibility featuresAIIntegrated AI toolsAPIPublic endpointsBlocksContent blocksConfigConfiguration optionsDocsDocumentation-only correctionsEventsCallbacks, function callsIntegrationsFrameworks, npmPerformanceRender latency, resource-usage optimisationsSecurityCORS rules, allowed-domain listStorageStorage optionsUI/UXInterface and interactions

Feedback and support

If anything is unclear or missing, contact our Support team.

Full Changelog

Full Changelog

Browse the full changelog from newest to oldest,
or pick a specific month from the menu.