Your SlideShare is downloading. ×
Designing an infrastructure to support the publishing lifecycle
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Designing an infrastructure to support the publishing lifecycle

6,385
views

Published on

Slides for LavaCon presentation on infrastructure design for publication process.

Slides for LavaCon presentation on infrastructure design for publication process.

Published in: Technology, Business

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
6,385
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
13
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Designing an infrastructure to support the publishing lifecycle Julio J. Vazquez SDI Global Solutions
  • 2. What I’ll cover
    • Who I am
    • A look at the publishing lifecycle
    • Requirements & Planning
    • Writing and Editing
    • Review
    • Translation
    • Approval
    • Publish
    • What does it look like?
  • 3. Who I am
    • Sr. Information Architect
    • Lead consultant
    • Over 30 years in IT
    • Over 20 years in technical communications
    • Writer of Practical DITA
    • DITA advocate
  • 4. A look at the publishing lifecycle
  • 5. Requirements & Planning
  • 6. Requirements & Planning
    • How do you capture the requirements?
    • How to reflect those requirements in deliverables?
    • How do you validate the requirements?
    • What’s the interlock between the requirements and the plan?
  • 7. Writing and Editing
  • 8. Writing and Editing
    • Ease of insertion of elements
    • Ease of adding or changing attributes
    • Display of content
    • Manage linguistics
    • Ability to launch publishing previews
    • Different editing modes
    • Support for arbitrary DTD
    • Support for CMS
  • 9. Review
  • 10. Review
    • Define your approach.
    • Look for tools that best meet that approach.
    • Ease of access to review mechanism.
    • Ability to see broader context.
    • Collaborative communication.
  • 11. Translation
  • 12. Approval
  • 13. Publish
  • 14. What does it look like?