day 1 – content edu summit
soap!
10:30
In this one-hour workshop we will discuss the advantages of DITA XML-based structured content for omnichannel publishing and how to bring subject matter experts, technical writers and marketers on a common platform for collaboration. Think about the challenges in your company when it comes to DITA authoring and publishing, content contribution from non-DITA based subject matter experts, organizing review and approval workflows and delivering DITA-based content to the company website, PDF, and mobile apps and bring your own questions as well.
12:00
1:30
3:30
bubble!
12:30
As GitHub is the most important tool for developers and with so many different companies doing open source it is getting also an important tool for technical writers. Technical writer with experience in Git and GitHub is really valuable. Join our workshop to learn some basics and get some hands on:
- How to use GitHub for documentation purposes
- How to contribute to projects from GitHub
- Do some automation with TravisCI or CircleCI
1:30
3:30
But I also get tired of all the repetitive actions I have to perform. Copy-pasting files, renaming folders, replacing files on FTP servers, sending emails – it all gets so boring after a while.
I sure wish there was something to assist me so that I can just focus on writing my beloved user manuals.
Apache Ant is a tool whose “main known usage (…) is the build of Java applications”, but it can be adapted to perform almost any repetitive task you want.
Together we will find out what exactly Ant is, and how it can help you save time at work. We will learn about basic Ant tasks, and create our own build files from scratch.
5:30
sponge!
12:30
Lorem ipsum is dead, long live content design. In the workshop we’ll work as content designers on design challenges. We’ll start with napkin sketches enhanced with relevant content. Then we’ll dig deeper into the sense of individual words. We’ll create a repository of usable content. Finally we’ll try to put everything on a wireframe.
- You will learn:
- * that good content has its place in low-fi sketches,
- * how to validate words for your design,
- * to make sure the language you use is inclusive,
- * methods of work with words in the design process.
1:00
3:00
5:30
foam!
12:30
Business-wise, this allows designing products and services that actually resonate with the target groups. Life-wise, it just makes you see the world in a larger, more compassionate scale.
1:30
5:30
days 2 & 3 – conference
8:50
9:15
9:55
10:25
10:55
The products of technical communication – manuals, Help systems, user guides – are created using authoring tools that are decades old. And although many of those products are delivered on mobile devices, many are delivered using centuries-old paper technologies, or as PDFs. The applications and services that they document can be cutting-edge and innovative, but documentation is rarely so. In this session, we take a fresh look at how documentation could take new and clever forms, and the roles that connectivity, metadata, and interchange play in making that a reality.
You will learn:
- How “legacy” tools are based on last-century approaches
- Ways in which innovation has transformed approaches in related fields
- How connectivity has impacted document delivery
- Ways in which metadata can be the basis for innovation
- The role standards play in data and document interchange
11:15
11:55
12:25
12:55
2:05
2:45
3:15
It is simple, highly readable and non-technical. It falls under “Behavior Driven Development” practices, which is a pretty innovative topic.
The idea behind it is to describe use cases related to a software in such manner that they are understandable by customers, product management, writers, testers, and developers – basically everybody in the software production chain.
At the same time it is a base used to run automated test scenarios.
3:45
4:05
4:45
Managing graphic assets in documentation can get tedious and time consuming. Companies large and small face challenges when managing their graphics assets, integrating them in a meaningful and productive way into their deliverables. I will present a case study on how my team’s transition into Scalable Vector Graphics (SVG) enabled paths to simplify and innovate in our deliverables, our content strategy, and our authoring process.
5:15
In the USA, the usage of Plain English is regulated by Plain Writing Act of 2010, ensuring that all legal, financial and medical documents are accessible, consistent, and easy to understand.
The presentation describes the benefits of using Plain Language in everyday communication with users, including both online and offline interactions. It will also draw directions of using the method in web and mobile content, which becomes increasingly more consumed form of instant information nowadays.
5:45
Last year two business school professors devised an algorithm to analyze 18 million scientific papers to see how original they were. They discovered that 90% of what was in these “creative” manuscripts was actually old stuff.
So innovation is effectively 90% known material, with a 10% interesting twist.
Don’t start from scratch. See what’s already been done and ask where you can take it to.
Kevin explains how in ten steps.
6:00
8:00
9:00
8:50
9:10
9:50
I have been working in the creative and innovation field for five years now and I think… I think innovation is SHITE! There, I said it!
But before you deem me unstable, let me explain! Let me tell you a story, based on actual events, that supports my claim. Let me show you why it’s actually SHITE!
10:20
11:40
11:20
Content can be created and managed in primarily two different ways – structured, following an XML-based information model or unstructured, without any specific information model. Over the last few years, we have seen a surge in companies (more so in a few particular industries) evaluating or migrating to structured content.
- • What is the current state of these companies and/or the industries? Did these companies migrate successfully?
- • Which specific information model did most of these companies choose? Why did they choose what they did?
Adobe recently surveyed a diverse group of 2000+ content professionals across 30+ countries to better understand their preferences, usage, and practices around structured content. The results revealed interesting trends in the areas of adoption of structured authoring, structured content management, the journey towards chatbots, and collaboration use cases, to name a few.
Join Adobe Tech Comm Evangelist, Stefan Gentz, as he shares the latest insights in structured content management based on the findings from Adobe’s 2017 – 2018 Tech Comm Survey.
11:50
12:20
13:30
2:10
2:40
Did you know that you don’t need to be agile to create UI text 10 times faster? You simply need systemic approach to messaging. And this means you need UX writers or content designers. Yep, and yet another modification of your design process. The more specialties on the team, the greater complexity? None of these things!
-
- The talk discusses:
- * the stages of maturation towards reaching the “content perfect” stage,
- * the idea that UX writing isn’t just delivering the “copy”,
- * content strategy deliverables that support product development,
- * how each strategic deliverable translates into effectiveness and money.
3:10
3:30
4:10
We’ll tell the epic tale of how we charted a vision, built our vessels, navigated constraints and fought monsters of doubt. But we stayed the course (see what we did there?) and the whole company is now arriving at a land of opportunity, where wonders of larger scale await us all.
4:40
5:10
Design Systems and its documentation have been a hot topic in the design industry for quite some time now. Yet, nobody seems to have found the secret recipe for it. Furthermore, everybody is looking for the “right” answer to the same questions – How do you build a system that is comprehensive, always up to date, and easy to maintain? How do you motivate other people to use it and have the system itself grow and evolve? Do we need to invent new tools to solve this problem? Or does it really come down to how our teams are structured? This talk is a collection of lessons learned from building, failing, and iterating on multiple Design Systems.
5:30
on