Overview over all blog items

Mar 29, 2017

Creating Content Together - Collaborative CMS solutions

Outline of our strategy for collaborative CMS solutions for 2017

Earlier this year we started with the integration of the collaborative editor SMASHDOCs in Plone 5.

Our goal for 2017 is to provide integrations of SMASHDOCs for all major CMS implementations like Drupal, Joomla, Typo3, Wordpress and others.

The technical foundation of all CMS specific implementations are language specific wrappers of the SMASHDOCs webservice API.

At the moment we provide wrappers for the following languages:

All wrappers will be provided for free under the GNU Public License V2 (GPL2). All wrapper share basically the same common API which is fully documented for Python.

On top of the language specific SMASHDOCs wrappers we will provide CMS specific implementations like the one for Plone (screencast).

A prototype integration of SMASHDOCs with Drupal is currently in the making (screencast).

The name of this new project is Creating Content Together. Besides the SMASHDOCs integration we will optionally provide extended publishing capabilities based on our decade-long experience with project based on the Produce & Publish  stack and our XML-Director CMS solution.

creating content together logo www.creating-content-together.info

content-gemeinsam-erstellen logo www.content-gemeinsam-erstellen.de

Further informations about roadmap, functionality and pricing can be found on the websites above. Both sites will be relaunched within the next week. Also the English website will see a native translation (currently automatically translated using Google Translate).


Andreas Jung


Dec 06, 2016

Integration of Plone 5 with SMASHDOCS

SMASHDOCS is a web-based collaborative editor solution that we integrated with Plone 5...and the good thing: Smashdocs is available for free for NGOs.

We are proud to present the integration of  SMASHDOCS - "a web-based intelligent word processing platform" - with Plone 5.

Smashdocs allows you to work as a group of editors or commentators on documents. #

Smashdocs supports

  • the standard editor functionality in combination with change tracking
  • review of changes,
  • commenting,
  • approval or rejection of changes.

Smashdocs can be compared to Google Docs but it works completely different and it is much smarter about versioning, collaboration features and approving or rejecting changes.

Smashdocs supports (similar to Plone) a role-based access model:

  • Reader
  • Commentator
  • Editor
  • Approver

Existing DOCX content can be imported into Smashdocs through Plone. Smashdocs can generate various output formats like DOCX, PDF, EPub, HTML - formatted in the layout and look & feel of your corporate identity. A later version of our integration will be able to pull these formats automatically from Smashdocs and store them directly in Plone. So your documents can be made available for download (DOCX or PDF) and also published directly within the Plone CMS - within the same look and feel as your Plone 5 website.


Smashdocs offers various hosting options (public cloud, private cloud, self-hosted) - see the Smashdocs pricing options.

The integration of Smashdocs with Plone 5 is work-in-progress and is available as open-source here.

Smashdocs is available for free for elegible NGOs - please check the Smashdocs announcement.

You can test Plone 5 and Smashdocs on our Plone demo site www.plone-demo.info.


Andreas Jung/ZOPYX
P +49 7071 793376

Nov 08, 2016

Bringing real collaborative editing to Plone

Integration of Plone 5 with the Smashdocs authoring solution.

As part of our professional publishing strategy we will bring real collaborative editing to Plone.

We started with the integration of Smashdocs - "a web-based intelligent word processing platform".

Smashdocs is about collaborative editing in the browser with decent support for collaborative and concurrent authoring, tracking changes, discuss and comment on content, review and approve/reject content changes. Smashdocs support different roles: readers, commentators, editors and approvers.

Here is a quick&dirty screencast showing the first cut of the integration with Plone 5.


Sep 16, 2016

Press release: XML-Director 2.0 released

XML-Director is our Plone-based integration platform for building high-quality enterprise-grade publishing solutions.

Find the official press release for the recent XML Director 2.0 release here

Sep 13, 2016

Don't use "docker" in Github repo names or as Twitter handles

The strict trademark guidelines of Docker Inc. can easily be turned into a case against any open-source programmer or project using "docker" as a repository name or for example as a Twitter handle. Act now!

The trademark guidlines of Docker Inc. for protecting the trademarks are dangerous and harmful to the open-source community around Docker.

In particular you are not allowed to use 

  • repository names for your open-source projects starting with 'docker'
  • use 'docker' as part of a Twitter names like @dockersucks, @dockerfan or @docker-usergroup-nyc
  • ....

I asked Docker Inc. about using 'docker-' as part of some of my repository projects on Github.

So here is there answer:

So what does this mean?

You are subject to be contacted the Docker Inc. for renaming or removing your project.

In the worst case Docker Inc. can sue you.

To make it clear: every company has a right to defend the trademarks and copyrights - no exception.

However a company like Docker Inc. that is driven and backed by a huge open-source community has certain obligations regarding the fair-use of trademarks by the community.

The current Docker trademark policy is an asshole policy:

Brought to the point: We are Docker Inc, we are the kings. You (the community)....we don't care about you. 

How can Docker Inc. get out of this problem:

  • relax the policy for open-source project regarding repository names, social media names etc. for open-source usage of Docker technology
  • allow the usage of 'docker' in domain names for open-source in general e.g. for usergroups etc. (any person should be allowed to ask 'docker' as part of domain name for non-commercial purposes).

We had the same discussions with Zope Corporation 15 years ago regarding trademarks etc. around the term ZopeIn the end Zope Corporation moved most of the copyrights and trademarks into the Zope Foundation and established a fair-use policy that worked for the years. The same is true for other entities holding copyrights and trademarks like the Plone project with its legal entity the Plone Foundation

Copyright and trademarks vs. open-source community is not a contradiction. The last decade and longer showed that there is reasonable way to deal with commercial interests side by side with community interests.

So Docker Inc play nice and fair with the people that made you what you are.

Clarification: Docker Inc. did not ask me to take down or rename my repositories. As you can see from the screenshot I asked Docker Inc for a clarification on this issue and the answer is shown above. 


Aug 26, 2016

XML-Director 2.0 update

XML-Director is our Plone-based integration platform for building high-quality enterprise-grade publishing solutions.

XML-Director is our Plone-based integration and implementation platform for delivering enterprise-grade publishing solutions to customers.

The core features of XML-Director are:

  • transparent application access to XML databases (Exist-DB, BaseX, Marclogic Server), DMS (Alfresco), WebDAV-based storages (Dropbox, Sharepoint) and cloud storages like Dropbox, Google Drive or S3
  • registries for XML validation and XML transformations
  • export and import of data and content
  • a REST API for managing content, workflows and conversions
  • a very secure CMS with workflow support, user and group management etc. based on the CMS Plone

Due to its modular and generic design, XML-Director is capable to integrate third-party conversion services easily and seamlessly:

In XML-Director Version 2.0 (soft-released lately) we introduce some more new features

  • full support for Plone 5.0 and 5.1
  • a new user interface for navigating and filtering your content and data
  • a reimplemented import form for zipped content or a new multi-file upload
  • support for Dropbox as content source
  • integration Twitter and Facebook for pushing content updated directly to social media
  • integration with Nimbudocs editor for building decent WYSIWYG  web-to-print applications 


  • an easy-to-use browser-based DITA topic editor
  • a graphical DITA map composer for creating maps from existing content repositories using drag & drop 
  • integration with Smashdocs editor
  • planned: integration with XEditor
  • planned: integration with oXygen XML Web Author

Our References


ZOPYX Andreas Jung


Jul 29, 2016

Stellungnahme der Antidiskriminierungsstelle des Bundes zur Beförderung von großen Personen bei Airlines

In einer formlosen Anfrage an die Antidiskriminierungsstelle des Bundes habe ich gefragt, ob es das Zusammenpferchen von großen Personen wie mich (203cm) in der Economy Klasse der meisten Airlines auf dem Platz einer Legehenne rechtlich vereinbar ist und ob sich aus der Körpergrösse ein Anrecht auf eine menschenwürdige Beförderung ableiten lässt. Die Antidiskriminierungsstelle antwortet mit einer interessanten Rechtseinschätzung....

Jul 28, 2016

Cross-browser hyphenation support for Plone 5

Most browsers lack hyphenation support (except Firefox). This Plone 5 add-on brings customizable hyphenation support to Plone 5 e.g. for better readability of the Plone 5 toolbar in German language.

Browsers - even in 2016 - are in general bad when it comes to hyphenation using CSS. CSS provides support for hyphenation for a long-time through hyphens: auto. However most browser excepts Firefox do not support hyphenation of text. There are some Javascript add-ons around for providing  hyphenation support across all browsers and most common languages - solutions like Hyphenator.

In general hyphenation on the web is not that important as hyphenation in print due to different display sizes, responsive design etc. However in some situations you want proper hyphenation for words or texts when the horizontal width of a box is limited and the standard word breaking algorithms of browser just generate a bad result.

This is one of (my) issues with the Plone 5 toolbar which looks like this (out-of-the-box with German as language) with completely unacceptable and improper word breaks.

zopyx.plone.hyphenator solves this problem by integrating Hyphenator with Plone 5. 

As a result the Plone 5 toolbar looks much nicer - in particular because a proper hyphenation. 

zopyx.plone.hyphenator can be configured to apply hyphenation to arbitrary page element by specifying a list of related CSS selectors within the Hyphenator control panel

Hyphenator supports most of the frequently used languages. Further hyphenation options provided by Hyphenator  will be supported by zopyx.plone.hyphenator  over time.


Jul 22, 2016

Plone 5 and XML-Director 2.0 with Dropbox integration

After many months of pain with Plone 5.0, XML-Director 2.0 will be finally available for production soon. This screencast shows you how to integrated Plone via XML-Director with Dropbox (or other databases or (cloud) storages).