Release notes from V1 to V2

We have been working for the last months to bring you a significant improvement of BrixWire News Hub compared to the installed version, i.e. a real major release.

We are changing from the classic version (V1) to the core version (V2). Here we would like to tell you more in detail!


What is new?

Platform independence

BrixWire runs on Linux or Windows systems. It runs with MS SQL Server or PostgreSQL server as DB Backend.

Rest API and Angular


A REST API (Level 2 with ODATA) is implemented in parallel to the existing APIs. It still needs refinement and completion, but it is integration-ready.

  • Angular UI

Finally reached after a long journey. Besides the classic UI, the new Angular UI is available. It is faster, less resource hungry, more customizable or brandable, and simply better.

BrixWire Angular UI
This is how it looks!
  • JWT Support

All Apis are secured by JSON Web Tokens now, to enable the UI to work in public reachable environments.

Push notification of client

The classic version relied on polling to update the UI for new stories. The core version has an implemented push mechanism, which leads to lower resource consumption (e.g. tablet usage) and reduced latency.

Auto publishing, AnyFirst approach

We enhanced the auto publishing features of BrixWire. By consequence, you can publish articles from you CMS directly and without human interaction to WoodWing or vice versa. A pair of Input and Output plugins is required for this to work.


  • Overhauled RSS feeds

RSS feeds with several versions of RSS are supported now. RSS Specification is somehow unclear or too old. By consequence, several formats are out there, and the formats contain mixed structure (i.e. elements from several versions of the standard). We did improve the existing RSS plugin a lot, including cleanup of malformed Html, etc. Besides that, the load is reduced by allowing RSS feeds to use 5 threads in parallel for pulling information. This should reduce the load.

  • Overhauled file system plugin

The file system plugin now supports building up chains, i.e. it can act as a relays station to share imported content with many instances. Besides that, a file system output plugin is available, which allows publishing for consuming application using a filesystem based technology.

  • Woodwing Plugins

The WW plugins are overhauled, and they now support fully duplex mode, i.e. you can mirror a WoodWing instance with BrixWire for input and output.

  • WordPress Plugins

WordPress instances can now be used as a source (to read articles from) or as a target to publish articles to.

  • LivingDocs Plugins

Similar to WordPress the CMS “LivingDocs” is added to the ecosystem. It allows full-duplex support, as is possible with the WordPress plugin.

  • Mail Plugins

Mail plugin allows watching configurable mail hosts and transfers incoming mails to publishable stories. Vice versa it allows for publishing to various mail recipients.

  • Twitter Input Plugin

Tweets are read from Twitter acc. to configured filters and can be imported.

  • Facebook Plugins

Posts and images can be imported and published to various and configurable goals. It is possible to support various output formats. Stories and images in BrixWire can be exported and published on Facebook as a post.

  • LinkedIn Plugins

News can be imported and published to various and configurable goals. It is possible to support various output formats.

  • REST Plugins for generic input and output

BrixWire provides generic input and output, using generic interfaces and configurable transformations. Important for customers, who want to extend the system with their own news sources.

Why should you update?

  • Faster and more intuitive UI.
  • You can include social media channels in your workflow with the new social media plugins.
  • A lot of new possibilities for Your publishing needs are opened.
  • We are heading for a regular update process as well, to keep You up to date regarding security and functionality.

Let us know, what You think

If You have uncovered requirements, ideas or questions, please leave a comment to us.

Add a Comment

Your email address will not be published. Required fields are marked *