Possibility to make backups is always available

In the project managing view, there are project-specific backup functions that allow you to backup everything or something to be kept somewhere else or to be exported to another project a moment later.

A whole project with its writings, images and other stuff can be wrapped in a zip package with a single button press and if needed, the same zip package can be dragged to the project list in the project list view, where a new project is generated from the contents of that zip package. Please note that this will also regenerate all the image catalogs used by the project, i.e. no attempt will be made to combine the new project with any existing image catalogs in the service.

To be honest, the ability to put multiple projects in a single backup without the backup containing the image catalogs used by those projects multiple times is already available, but the user has to enable such functionality separately due to the potentially high server load. Backups generated in this way can be drag'n'dropped into the project list view as usual (image catalogs would not be duplicated even if multiple projects use the same ones).

Just the writings as JSON data

If you don't need to backup the whole project, but just want to copy collections of writings from a project so that they can be used in another project, you can copy these writings as JSON structured data, which can be passed as input in the importing view of another project. The item moving view would not allow the moving of writings beyond the boundaries of a single project.

Publishing a solution elsewhere (only to those, who have experience in making web pages)

It is possible to export the work contained in the project in to a zip-packaged file, so that the contents of that zip-package can be copied via FTP or SCP to a directory on a server of one's choice and be made publicly viewable in a browser. A work exported this way wouldn't have differences in its outlook, but the contents would be completely "static" (not generated separately at every page load). The images in the work can be distributed via a CDN service or retrieved directly from that another server by the browser. This feature is under consideration and may be disabled.

If necessary, the project list view has a function to generate an index list of published works, but if the user wants to edit the index list in the HTML editor, some know-how about building websites might be required. In practice, generated index.html file contains all images as base64 encoded data with CSS stylefiles/JavaScript libraries included.