DOCUFY Layouter allows you to easily design output layouts yourself, save them, and customize them as desired. The new release now offers even more layout options.Continue reading News from DOCUFY Layouter
All posts by Melanie Kunas
How will intelligent information shape our future?
The ii-Blog (intelligent information blog of tekom) has called for a blog parade. Topic: How will intelligent information shape our future? – Melanie Kunas from DOCUFY outlines her future scenarios.
Robots that take on care tasks. Computers that write football match reports, trade stocks or clarify legal doubts – what sounded like a fantasy a few years ago has long since become reality. What happens next with Industry 4.0, Artificial Intelligence and Robotics? And what could my typical everyday life look like in the digital future?Continue reading How will intelligent information shape our future?
COSIMA 7.5 – New release, more usability
What are our plans for 2019? To make our software solutions even more comfortable for you. And we got started immediately: COSIMA 7.5 has been released in January – with a new output format, usability improvements and cost-saving innovations for translation.Continue reading COSIMA 7.5 – New release, more usability
New in COSIMA: IGEL – the integrated callout editor
Explaining complex issues in a simple way – often a very difficult task. Images can help illustrate what you want to say. Because you know: A picture says more than a thousand words! Especially in technical documentation graphics are used to put things in a nutshell. The reference of the graphics to the descriptive text is important. These references are created using item lines and/or item numbers, the so-called callouts. With COSIMA Release 7.0 you now have an integrated callout editor at your disposal with which you can easily add position numbers to your images yourself.
Continue reading New in COSIMA: IGEL – the integrated callout editor
DOCUFY Layouter: create your own layouts
Imagine there is a change in corporate design at your company. Maybe the change is only a general attempt to optimize existing layouts. Maybe it entails a completely new corporate identity with a new logo and different colors. Or maybe your company has a new division that makes new products. Any change, no matter what kind, will have a direct impact on your technical documentation. The cover page needs to be redesigned, and the way headers and footers look will change – as will headlines, safety notices and warnings. It is practical when technical writers can make these layout changes themselves, without any programming skills or troublesome extra work.
What? Another blog?
If you ask Google about good reasons for starting a company blog, you will receive over 307,000,000 results: “5 good reasons for writing a company blog,” “10 good reasons,” “Why companies should have a corporate blog,” etc. According to them, a blog promotes customer proximity and makes those interested more aware of your company. It might even generate some enthusiasm on the part of highly qualified potential employees.
So every company with a healthy sense of self-esteem urgently needs a blog? Perhaps. But we are concerned with one thing above all. At our company, we work with a lot of experts that have a great deal of specialist knowledge about their respective fields: IT experts, technical writers, consultants, marketing experts, support staff, a number of partners from the higher education and private sectors, and – last but not least – our users. All of them have a lot of important expertise that we want to make available to everyone on our new blog. Our motto: No empty blah blah blah, just content with real added value.
Our goal: No background noise, just informative content
Melanie Kunas, DOCUFY GmbH
We see a blog as the ideal medium for exchanging specific information. And for us it is also explicitly about exchanging information between experts on the user side and experts on the DOCUFY side. There is no imminent danger of “content shock” (many channels, a lot of drivel about nothing). We’re not interested in background noise. What we want to do is take our stores of knowledge out of the basement and make them available to our users and anybody else who is interested – quite in line with the concept of Multi-Level documentation.