Yesterday afternoon, June 26, a select group of publishing professionals gathered at the Dolby 88 Screening Room in New York City to preview the next iteration of RSuite CMS.

The software was prescreened to a packed audience of publishing professionals and a global online audience joined via a live streaming broadcast.

Christopher Hill, vice president of product management at RSI Content Solutions, highlighted key features of the 4.0 release and detailed how these changes are based on feedback received from  users over the years.

The flexible user interface offers a new user experience that is better organized with contextual menus that detail what choices a user has based on the current state.

All the fundamental content management capabilities remain that ensure publishers' and media organizations' content and assets are preserved to ensure long-term survival in one central and secure location. But a large and obvious improvement in RSuite 4.0 is the digital asset management (DAM) functionality that offers better visibility of digital assets that will aid content discovery and reuse.

The software screening was the first time an audience of C-level publishing professionals viewed the new user interface, which is spearheaded by Bryan Elliott, user interface architect at RSI Content Solutions. Attendees were invited to speak with members of the RSuite development team and CTO, Lisa Bos, following the software demonstration during a 2-hour networking reception.

The post-screening reception was packed with publishing and media executives. The main regret was that our global audience who watched the demonstration via a live stream online could not imbibe in the libations and food.

Barry Bealer, CEO and co-founder at RSI Content Solutions, welcomed all and served as master of ceremonies for the event. Before the software demonstration commenced, he rolled out the changes of the impending release with a video highlighting the work he has directed over the past 12 years as well as the changes witnessed in the publishing, software, and media industries.

Enjoy:

If you were at the event and have any feedback for how we can improve, we welcome your suggestions!

When implementing RSuite CMS, our content architects and engineers help publishers ensure that the transformation from Word to XML is seamless and easy. The following best practices were developed that can be used in any publishing workflow to ensure content is consistently styled.

The following guidelines are based on a Word-to-XML conversion process using DITA For Publishers, which transforms embedded Word XML to true XML by taking advantage of style-to-tag mapping. All publishers can benefit from this approach, even if an early-XML workflow is not yet on the radar (though it SHOULD be!). What you get out of using real templated Word documents is consistency. Whether it's to generate XML or deliver to an offshore production service, consistent styles make downstream processing easier and allow for automation.

Best Practices for MS Word Authoring by Harvey Greenberg and Paul Eisenberg

Context

• MS Word 2003 and above use docx as default format.
• A docx file is actually a zip – you can rename foo.docx to foo.zip, unzip it, and see what’s there.
• Word to XML conversion process using DITA4Publishers transforms the embedded Word XML to “real” XML using style-to-tag mapping.
• Content that does not have a style accounted for in the mapping is ignored.
• Only styles are processed, not format overrides.
• This applies to character styles as well as paragraph styles.

Templates in MS Word

• Whereas “template” often means a starting document, in MS Word a template is a dotx file.
• All documents are attached to a template – the default is normal.dotx.
• Templates may be stored in the user-defined template location (Word | Options | Advanced | File Locations), or in a workgroup location (generally a shared network drive).
• Best practice is to use a template specific for the project.

Viewing, Applying, and Creating Styles

• Best way to view styles throughout the document is using Draft view with style pane; this needs to be set in Word | Options | Advanced.
• CNTL + SHIFT + S will pop up style dialog appropriate to cursor position; both para and character styles will show up.
• To create new styles, process is:
• Create or open document to which your template is attached.
• Make and test changes, being careful to always select option that applies changes to all documents based on the template, as opposed to current document
• Exit Word.
• Reopen Word, create new document based on your template, and see if changes took.

Some Tips and Tricks

• Templates may contain boilerplate text as well as styles; you can provide starting title, standard sections, etc, for authors to change.
• You can assign keyboard shortcuts and also change the quick style bar.
• A style can automatically assign style for the next para (e.g., Title can create Heading 1).
• A shortcut to a macro that does Edit | PasteSpecial | Unformatted Text is your best friend
• Probably best to avoid use of the default “Normal” para style, because it may not be clear whether para should be normal or you just didn’t take any action; perhaps use something like BodyPara in its place.
• Do not use empty paras for spacing; assign spacing via the style.
• Adding formatting to the styles so that the author can tell immediately that a heading is a heading and a list is a list, etc, is good.
• Trying to replicate the look and feel of the product is wasteful and can distract authors from the task at hand, which is good content.

I hope these best practices will be useful in your publishing workflows. To learn how some of our publishing clients are implementing this, download your free white paper: "How Successful Publishers Deliver Content: RSuite CMS and DITA For Publishers."

Next Tuesday, June 26th, RSI Content Solutions will host an early screening of its next software release, RSuite CMS 4.0. This latest iteration of content management for publishers offers a new approach to creating, managing, and delivering content anywhere, any time, in any format.

There's a lot to see both from a user perspective as well as a developer perspective. The new fluent user interface benefits the user experience with contextual menus that detail what choices a user has based on current state.

A networking reception will follow this screening. If you are a publishing executive in the New York City area and would like to attend, please contact me for details.

One of our readers shared a recent infographic she put together with a team of designers and researchers: