Adobe at STC Technical Communication Summit 2011

Wednesday, May 11 2011 @ 11:52 AM, By Ankur Jain

The STC Technical Communication Summit 2011 is quickly approaching. The Adobe team is going to be present (including me), and will celebrate 25th anniversary of FrameMaker and 20th anniversary of RoboHelp at the STC Summit.

The event takes place May 15-18 in Sacramento, CA. These conferences give us a great opportunity to meet and greet each other. Please stop by the Adobe booth to get your questions answered or just to say hi. If you would like to set up a meeting while we are in Sacramento, please do write to me.

Here are some of the sessions/opportunities you don’t want to miss:

  1. What’s New In Tech Comm Suite 3 and FrameMaker 10
  2. Tom Aldous; 8:30 AM to 9:30 AM on Monday, May 16

  3. Easy and Low Cost Transition to DITA Authoring Using Adobe FrameMaker 10
  4. Kapil Verma; 10:00 AM to 11:00 AM on Monday, May 16

  5. Interactive and Web 2.0 Delivery Mechanisms for Your Content
  6. Ankur Jain; 2:00 PM to 3:00 PM on Monday, May 16

  7. Extending Adobe FrameMaker Beyond What’s In the Box
  8. Rajat Bansal; 3:30 PM to 4:30 PM on Monday, May 16

  9. Delivering Content with Adobe TCS 3
  10. Matt Sullivan; 2:30 PM to 3:30 PM on Tuesday, May 17

  11. Case Study: Adobe FrameMaker 10 Reviewer’s Guide
  12. Bernard Aschwanden; 10:00 AM to 11:00 AM on Wednesday, May 18

See you soon!

Ankur Jain
Product Manager – Technical Communication Suite | RoboHelp
Follow me on Twitter: @ankurjain8

  • Categories

  • Archives

  • Authors

  • Useful Links

  • Recent Comments

    • Jeff Coatsworth: Hey Vikram – the link to the helpx article is still resolving as “https://helpx.stage....
    • Sreekanth: Thanks for allowing us to ignore reference images in FrameMaker book. That is a definite time-saver.
    • Joel: Thanks for fixing the links guys!
    • Maxwell Hoffmann: Ted, one aspect of the blog that may have escaped your notice; you can launch the HTML5 version in...
    • Maxwell Hoffmann: Joel, per comments made above, I discovered that the original URLs were incorrect with pointers to...