Clarity and consistency to benefit the SDK end-user.


How we developed content optimised for their business needs and for the needs of their users.

WACOM needed a team that could work with minimal input, dealing with highly technical and detailed content in a timely manner while providing business-boosting enhancements at every step of the SDK value chain.


TWi quickly understood how our internal documentation generation tools work. They proactively made suggestions to enhance our HTML tools for previewing the SKD content. which we implemented.

Branimir Angelov, System Architect,
Wacom Europe GmBH

WACOM: Clarity and consistency to benefit the SDK end-user

Wacom is the world’s leading producer of graphics hardware for designers, artists, and engineers, especially high-end graphics tablets and digital pens. The company was a trailblazer in tablet computing, partnering with Compaq to produce an ancestor of today’s tablets in the early 1990s. Wacom provides technology to Samsung for their Galaxy Tab and Galaxy Note products, most notably the S Pen.




Wacom opens its software to external developers through an Application Programming Interface (API) called Wacom Ink Layer Language (WILL). Using WILL, developers build apps for computers, smartphones, and tablets that can translate mouse or touch inputs into onscreen graphics.

Wacom’s aim is to make WILL a standard model for onscreen graphics, just as HTML is the standard for web development. To enable widespread adoption, the WILL Software Development Kit (SDK) supplied to external developers must be easy to use. Improving the kit’s built-in documentation was crucial. Wacom needed a major update to the API content for its WILL SDK to achieve their goal.




Initially, Wacom’s WILL developers wrote the SDK documentation themselves. They are gifted developers, but they lacked technical writing training. This led to some issues with their content, such as:

        • The SDK content was originally written in Japanese. Subsequent international versions were written by non-native English speakers. Read this to see how translation makes a big difference.
        • Knowledge that was especially important for new users was not identified
        • Techniques for effective knowledge sharing were overlooked
        • Links between tutorials and the API reference material were not highlighted
        • Some content was badly formatted, poorly structured, or difficult to follow

Having identified these issues, Wacom sought a partner with a proven track-record in writing clear, concise API documentation. They needed a team that could work with minimal input, dealing with highly technical and detailed content in a timely manner while providing business-boosting enhancements at every step of the SDK value chain. This included high-level concept articles about WILL, API reference documentation, and tutorials for using WILL on iOS and Android devices and across a wide range of online applications.




TWi’s information architects and technical writers worked with Wacom’s developers to improve their WILL SDK documentation. The company selected our Managed Service option, which is designed for projects with a pre-defined scope and budget.

Our initial process was as follows:

        1. Analyse the existing SDK deliverables and review Wacom’s documentation.
        2. Provide Wacom with a full list of potential improvements.
        3. Discuss proposed improvements and agree on a prioritised list of content updates while working to Wacom’s timeline.
        4. Rework concept articles to improve their structure and organisation using Wacom’s system.
        5. Expand Wacom’s tutorials to fully support novices while facilitating quick understanding and adoption by experienced users.
        6. Implement comprehensive linking between these tutorials and related Wacom API reference topics.
        7. Develop new information structures for Wacom to protect their content against obsolete or broken links.


Our writers’ technical knowledge is an integral part of our service. TWi’s experts highlighted instances where code in the WILL SDK documentation did not match code provided in sample files. We also identified areas where API references linked to deprecated or missing objects. Inconsistencies such as these can negatively affect the user experience and damage users’ perceptions. Upgraded content enhanced end-user perceptions of the API and the wider Wacom brand.

Detailed status reports and continuously updated timelines allowed Wacom to control review schedules. This significantly reduced waiting times between draft and review handovers, resulting in faster and more efficient content production. Optimising the feedback cycle made the entire development process more efficient.


Other key actions included:

        • Identifying information gaps and proposing effective solutions to close them
        • Highlighting specific code for use in tutorials, increasing the tutorials’ value to learners
        • Updating Wacom’s metadata to ensure correct outputs, minimising delays
        • Creating consistency to provide maximum functionality to the end user and reinforce trust in the Wacom brand



TWi’s project enhancement for Wacom resulted in:

        • Increased external adoption of the WILL API thanks to improved SDK documentation
        • Improved quality, structure, styling, and formatting of content
        • Effective project management
        • Knowledge that was optimised to be accessible to all users
        • Greater consistency
        • More user-friendly tutorials directly linked to relevant API content
        • Improved data sharing

The client appreciated the efficiency generated by TWi’s client-communication methodology. The WILL SDK developers were impressed with our initiative in flagging technical issues and ability to carry out constructive changes and updates without their input.

Following our engagement, Wacom extended the project’s scope. Phase 2’s expanded targets and criteria were based around TWi’s ability to provide content optimised for their business needs and for the needs of their users.




“TWi’s assistance proved invaluable. They quickly got to grips with the technical nature of the material and took a fresh look at everything we had. The content is now structured and clear, and its usability has been greatly enhanced. TWi quickly understood how our internal documentation generation tools work. They proactively made suggestions to enhance our HTML tools for previewing the SDK content, which we implemented. We’re very happy and are planning to work with TWi on future documentation projects.”

– Branimir Angelov, System Architect, Wacom Europe GmBH

Related Insights

Interdisciplinary Synergy in Technical Communication

Interdisciplinary Synergy in Technical Communication: Written by Neil Mahony and originally published in the Winter 2023 edition of the Communicator Magazine. Across all industries, companies struggle with the drawbacks of siloed departments. They create change...

The Need for an Artificial Intelligence Codex

The Need for an AI Codex | Written by Dr Sean Power If your organisation develops or uses AI, you probably need an AI Codex. New technology usually forces a gap between, on the one hand, regulations and general industry advice and, on the other hand, what your...

ChatGPT & Me: Memoir of a Collaboration

Written by Heidi Staples. Originally published in the Summer 2023 edition of the Communicator. Artificial intelligence (AI) and human writing collaboration is a growing trend in the field of content creation. While AI technology has made significant strides in...

Is ChatGPT our “Sputnik” moment?

Written by Kieran Fitzpatrick. This article was originally published in the Summer 2023 Edition of the Communicator. Predictably, the inaugural edition of Communicator in October 1968 focused on defining technical communication and its practitioners. In particular,...

Mastering Content Migration Strategy: A step-by-step guide to success

A content migration involves multiple moving parts, and navigating the entire process from start to finish can seem overwhelming. However, with a well-defined content migration strategy and a clear understanding of the necessary steps, you can effectively manage the...

Technical Writing Skills 101

Written by Oonagh Montague, Training Manager at Technically Write IT As a business owner or an employee, you may have heard the term "technical writing skills" and wondered what it means. Is it important for my business?  The answer is yes, it really is. Poor...

Here’s What You Need to Know About Content Accessibility

This article on content accessibility was written by Claire Walsh, Senior Information Developer at TWi Content accessibility is a vital aspect of communication in today's diverse and inclusive world. Whether it is a website, system, internal communication, or any...

SAP Enable Now Webinar Videos

As you know, we recently hosted a webinar in collaboration with SAP focused on how to get the most out of your SAP Enable Now investment, and we have compiled a playlist of six short snippets from our webinar. In this webinar, we share a getting-started approach that...

Who Needs to Write Good? Or What is Technical Writing?

Written by Oonagh Montague, Senior Training Manager. Ten years ago, if I thought about the term ‘Technical Writer’, I thought nerd. I thought nerd with specs and a pocket protector nerding out at their laptop, disappearing down rabbit holes of data and content and...

Writing User Manuals: Five Top Tips

Writing user manuals is a common requirement of the technical writer's role across many different industries. It's also not uncommon for this task to fall to someone who is not a technical writer by trade — and in this case, writing user manuals can seem like a...

Start your content transformation today.