veyepar: [Peninsula] "Structured Authoring to Set Your Content Free" at Genesys

Author(s):	Ed Jamer, Barry Grenon
Location	Genesys
Date	apr Tue 02	Days Raw Files
Start	April 2, 2019, 7 p.m.	First Raw Start	April 2, 2019, 6:44 p.m.
Duration	00:45:00	Offset	0:15:43
End	April 2, 2019, 7:45 p.m.	Last Raw End	April 2, 2019, 8:01 p.m.
Chapters	00:00 0:11:22 0:38:33 0:41:22
Total cuts_time	56 min.

raw-playlist raw-mp4-playlist encoded-files-playlist host archive tweet mp4 svg png

assets release.pdf peninsula_structured_authoring_set_your_content_free_genesys.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:

Locked:

clear this to unlock

Locked by:

user/process that locked.

Start:

initially scheduled time from master, adjusted to match reality

Duration:

length in hh:mm:ss

Name:

Video Title (shows in video search results)

Emails:

email(s) of the presenter(s)

Released:

has someone authorised pubication

Normalise:

Channelcopy:

m=mono, 01=copy left to right, 10=right to left, 00=ignore.

Thumbnail:

filename.png

Description:

markdown

Ed Jamer, Senior Technical Writer, Genesys Information Experience
Barry Grenon, Senior Manager, Genesys Information Experience

How structured authoring, leveraging open source tools, can help your Pubs group grow from being a bottleneck—with complicated toolchains preventing non-writers from contributing—to a service organization that can provide all sorts of content across the organization, including docs-as-code and converged content straddling techcom and marcom, with true single-source-of-truth guiding the overall design of the system.

Focusing on two case studies, this talk will highlight some of the benefits of a pure open source, structured-authoring approach.
As a service group:
* Content experts define the forms and data structures used by all contributors, to enforce consistency of both content and metadata.
* Enable single-source-of-truth content repositories that other groups can pull content from, via REST APIs. In other words, support for a “headless CMS” approach to content re-use between websites (everyone can still own their own websites).
As a writing group:
* Your own technical writing group becomes just another group to service.
* Treat your content like a database, for maximum flexibility of re-use. The structure itself provides the keys from which you can build, sort, link, collate, and automate content.
* Open source allows for rapid prototyping: the “build and show” model for successful projects, versus the “propose and hope” model.

Comment:

production notes