Feature-rich, web-based publishing application. - KotvaWrite Stories

Currently I'm developing this as a solo developer. An instance of the application is installed on a per customer basis. Only server costs must be paid (in advance, about 9 euros per month) via PayPal. Service agreement defines and describes what isn't already told in the visually rich instructions (lots of screenshots). English instructions: http://kwstories.hoito.org/view.... Same instructions in Finnish: http://kwstories.hoito.org/view.... KotvaWrite Stories can be used e.g. to create these kinds of works: - an expression of a deep interest in an academic or everyday subject - live coverage of an ongoing situation - demonstration of skills and abilities - a place to find audiovisual, visual and audio works - a periodically published work - a long-term travelogue in blog format - a finalised telling about a place or experience - an occasionally improved explanation about one's health - a compilation of previous works published in different places - opinion pieces on topical issues - structured reporting within a defined target subject - a better explanation of what can be understood almost as such - fresh view points and insights with assisting images, figures etc. - a call to action using a wide range of arguments - writings having a conversational tone without any specific objectives Privately the publishing application can be used e.g. for preparation of writings to be published elsewhere (e.g. online or in a print publication), for storing online coursework assignment responses and associated images, for planning what to write to email contacts, for coordinating online discussions on forums etc. Server shouldn't get too stressed as all images are delivered using a CDN service, every published work can have its own cache setting and application server is using JPA (Java Persistence API). With 5 seconds of cache time a single server can handle at least 8000 requests per minute (about 70 ms response time for a single writing). Separating different kind of requests like uploads to separate servers is tested, but not thoroughly enough. I strive to make workflows as smooth as possible and I like to experiment (see e.g. https://github.com/markoseppaene...). At the moment there isn't a pricing or a contact page, but you can contact me using Facebook (https://www.facebook.com/markose...), if you are interested to try the product (suggestions and ideas are also absorbed). Be aware that I might choose to wait until there's enough interest before I begin accepting new customers. Good and useful publicity would be nice, so if you don't mind commenting how amazed (or something) you felt after glancing the instructions, please do so here at the Product Hunt. In my application's terminology project is something that can contain multiple solutions (published or private) and which have common image catalogs. Image catalogs can be linked to multiple projects. Published works equal to solutions. Here's a few of my own: http://kwstories.hoito.org/user.... (language mostly Finnish, but should give quite a good impression about what this application can be used for. As embeddable content there can be at least these: YouTube, Vimeo, Soundcloud, Mapbox, JSFiddle, CodePen, Observable, Flourish, streamable audio files, tweets..