A big thank-you goes out to all who joined us for the Scroll Versions 3.0 webinar. A complete video and all of the submitted questions and a...
On Thursday, November 26, we hosted the tekom RG here at the K15t Software office in Stuttgart. Many thanks to everyone who joined us, espec...
Available now in the Atlassian Marketplace We're proud to announce Scroll Versions 3.0, a major release of the best version management tool ...
Atlassian Summit Survey Results Are In It's no secret that Confluence is a powerful platform for documentation collaboration. At Atlassian S...
Great to See You Once Again in Stuttgart We may be just a bit biased, but we think Stuttgart is the perfect location for the annual tekom/tc...
An exciting and exhausting Atlassian Summit 2015 is now in the books, and with much fanfare it outlined how the company is working to make teams smarter, better, faster, and stronger.
Is your strategy for the tekom/tcworld Conference dialed in and ready to roll? Since tekom is the world’s largest technical communication summit, qualification event, and trade fair, your plan is worth a bit of thought. And as you’ll soon learn, the event has several traits that make it particularly German in character: it's well organized, business driven, and has a strong focus on factual content. We hope we can make it a more enjoyable experience for you, with our unofficially-definitive tekom/tcworld Conference Guide featuring six pro tips from guest blogger and tekom veteran Martin Häberle https://twitter.com/martinhaeberle.
We're just a few weeks away from Atlassian Summit 2015 http://summit.atlassian.com/, and this year K15t Software is bringing new product news, demos, and lots of friendly faces with us from Stuttgart to the Big Powwow by the Bay.
Last Wednesday we threw open the K15t doors to friends, family, partners, and customers to help us warm our new office https://twitter.com/search?q=k15twarming in Stuttgart, and it was a grand time if we do say so ourselves. Check out some scenes from the event after the jump.
“No one reads documentation, and nobody gives feedback on it.” This phrase is bad news for technical communicators – but it’s not the whole story. What actually happens in reality hinges on the way we manage and distribute technical content. (Protip: Host it on the web and invite everyone to get involved). This is the second part in our blog post series https://www.k15t.com/blog/2015/07/feedback-please-why-technical-writing-shouldn-t-be-a-one-way-street about the benefits of crowd-enabled documentation using a collaborative approach. In this post you’ll learn how to get readers’ feedback on documentation easily by building collaborative web-based help content that allows technical communicators to elevate the quality of their work to the next level.
K15t Software has grown once again, and to keep us all from elbowing one another we had to make a change. With a bit of work we have found...
We've now had a week to reflect on our K15t Out-of-Office Adventure, and the unanimous verdict is in: We can't wait to start planning the next one!
For a long time, technical writing was like driving down a one-way street. We’ve sent information into one direction, and nothing came back. But since the age of the Web 2.0, this approach is no longer a best practice. Today, being a technical writer means to communicate and to interact with everyone involved – including our readers. Building documentation heavily depends on feedback, and it’s an iterative process – more like a traffic circle. New processes require new technology – it’s time to move from publishing tools to collaboration platforms. This blogpost is part of a series about feedback in technical communication, In this article, read why receiving feedback is crucial to create helpful technical content and how a web-based collaboration platform can enable both internal feedback and customer feedback.
Last week we had the third Dev Together event at K15t Software. It was a great opportunity for us to bring together Atlassian users, customers & friends to our new office situated in the lovely East End of Stuttgart.
.We would like to invite you the next installment of our Dev Together event series on June 16th, 2015 at 18:00 at our new office in Ostendstr. 110, Stuttgart. This time Dave Meyer of Atlassian and Thomas Büschgens of W&W Informatik GmbH will talk about how they use JIRA. Join us for the talks and for drinks and pizzas afterwards.
Oops, we did it again – and we love it: Creating awesome stuff within 24 hours. Some of us were coding almost the whole night to make our ideas come to life. Here's how we spent our third, Atlassian-rules https://www.atlassian.com/company/about/shipit hackathon that took place in the K15t Software office. And, of course, we've got a winning team: congratulations to Eugen, Maximilian, and Tobias who have built and demoed an awesome multi-layer image map editor for Confluence!
Today, I'd like to share with you a little secret about Scroll Translations. It’s the Confluence add-on which lets you manage Confluence content in multiple languages within a single space. This makes it simple to add page translations. But how about page templates and blueprints? Does the same apply to them? The answer is yes. It's not only possible to create multilingual page templates – it’s easy. In this blogpost, I'll show you how to modify the troubleshooting blueprint (or any other page template) and make it speak in foreign tongues.
The Scroll Viewport 2.1 release is dedicated to all the viewport theme developers out there! Creating and editing viewport themes is now easier than ever (forget FTP!). Here are six reasons why you folks (not only theme developers!) should embrace Scroll Viewport 2.1 – the latest version of an add-on for Confluence that's also a framework for delivering Confluence content even simpler and faster to the web.
Today, we’re going to settle the question once and for all – which is superior? Documentation in a plain-text editor using Markdown, or creating content in a rich-text editor the WYSIWYG (what you see is what you get) way? How will it be decided, you ask? A good, clean head-to-head fight!
Bringing people together in a collaboration platform like Atlassian Confluence also means transferring your legacy content from multiple information silos. These repositories often contain important information that you can’t afford to leave by the wayside when building a new corporate knowledge base. In many cases, legacy content is only available as HTML files, such as online help resources or intranet pages. Is there a way to bring these assets into Confluence efficiently? Yes – but there is no one-size-fits-all method. There are three main approaches to importing a collection of static HTML pages. Your individual needs will determine which is best for you.