Tuesday, April 11, 2017

Welcome to MadCap Central

NOTE 1: This article was originally published in ISTC Communicator, Spring 2017.

NOTE 2: Since I wrote this article, MadCap has released v. 2017 of Flare, which does not change the interaction with Central, and a new version of Central which adds support for Slack. Central's basic concepts and features remain the same however.

If you’re a MadCap Flare user, you’re likely to have run across two issues with your projects.

Issue one has to do with safeguarding your projects, getting them off your local PC and on a server to avoid losing the project files if your PC is damaged, and making them available to additional authors. The traditional answer is to get a version control system like Subversion or Git, but what if you don’t have the budget or IT support? From my training and consulting experience, many MadCap Flare shops are in this position.

Issue two is project management – how to keep track of the projects, tasks, and staff needed to create your projects. Many authors keep project to-do lists but they’re hard to manage and easy to lose, even for a single project with one author. It becomes still more difficult if you have one project with multiple authors, or multiple projects. How to keep track of everything?

MadCap Central is MadCap Software’s answer to both issues. MadCap Central combines project management and version control in one surprisingly easy-to-use package that integrates with the latest version of Flare, version 2016 r2. (If that number seems odd after years of integer versions like 10 and 12, it’s because MadCap has adopted an Agile release policy that promises incremental releases with new features and bug fixes several times a year.)

Let’s take a look at how MadCap Central offers version control and project management.

Version Control Features

Look at Flare 2016 r2’s View ribbon and you’ll see the new MadCap Central icon. Clicking it opens the MadCap Central pane where you can log in to MadCap Central. (You can also click an icon on that pane to quickly open the MadCap Central portal page in a browser and log in there.) Once you’re logged in, you’ve got several options from the MadCap Central pane’s local toolbar:

The principal options are:
Upload this project to MadCap Central – Click  to move the project into (bind it to) MadCap Central. Once you do this, you’ll see a Source Control item on Flare’s menu. Clicking that item opens the Source Control ribbon, shown below, which lets you control the project’s interaction with MadCap Central.

 At this point, you’re using MadCap Central like any version control system.

Remove MadCap Central Bindings from Project – Click  to remove the link from Flare to the project in MadCap Central. You’d do this if you want to take the project back to local status for some reason. Removing the binding from a project does not remove it from MadCap Central; instead, it simply removes the link between MadCap Central and the project.

Import a project from MadCap Central – Click  to download a copy of a previously uploaded project. You’d do this if you hired new authors and need to give them access to the project, or if an author’s PC crashed and the project has to be re-downloaded onto the new PC.
Upload latest local files to MadCap Central – Click to move any changes made on the author’s local PC to the version of the project in MadCap Central. You’d do this to update the version in MadCap Central with the latest local changes.
Open the MadCap Central portal – Click  to open MadCap Central in your browser. You’d do this to quickly access MadCap Central’s project management features.

So MadCap Central is actually replacing a traditional version control system. And you can use it to actually host your output. So binding a project to MadCap Central and managing the version control aspect really does seem to be this simple.

Three points to bear in mind:

  • MadCap Central is in public beta as of the date of writing this article – mid-December 2016. My experience is that everything is working smoothly but, as in any beta, some oddities may emerge.
  • MadCap Software plans to provide a gigabyte of storage for each MadCap Central subscription, shared among the users associated with a subscription. That figure may change depending on the result of the beta.
  • MadCap Software hosts MadCap Central, handling all server administration for you and effectively acting like a shadow IT department. This saves you the cost and effort of hosting a version control system yourself. Note that if you have a mandate to use a version control system that’s already in place, you can use MadCap Central in conjunction with other tools like Subversion or Git.

Project Management Features

Once you bind a project to MadCap Central, you can access a wide range of project management features.

The Home page features that let you display a dashboard, shown below, containing various widgets with information about aspects of all or selected projects or users.

The first release lets you select from eight pre-defined widgets. (Future releases may let authors create their own custom widgets.) You can manage the widgets and filter the information they show.

The Project page has features that let you get a high-level view of all projects stored in MadCap Central, showing the team members and individual users assigned to projects, project status, build and publishing history, and more.

A build management pane lets you see the targets for a project and build one from Central.

The Tasks page has features that let you define tasks with priority levels, the person responsible for the task, start and end dates, and more. You can see these tasks in a task board, shown below.

You can also see the tasks in a calendar view to help you plan your schedule. You can also filter and archive tasks in various ways to focus on what’s important at a particular time and to be able to go back and review what you did for a project post-mortem.

The Users page lets you invite authors into MadCap Central, set their permissions, specify projects and teams in which they can participate, and more.

The Teams page lets you specify what users belong to what teams, send messages to team members, keep tabs on the activities performed by members of a team, and more.

Basically, there’s no one specific way in which to use MadCap Central as a project management tool. Its features let you view projects in many different ways depending on what information you’re looking for. (This is similar to MadCap’s Analyzer add-on tool. Analyzer offers many options; the ones you use are entirely up to you.)


MadCap Central is a well-thought out product that offers easy-to-use project management for Flare projects and an equally easy-to-use alternative to traditional version control systems. It will also serve as a platform for future enhancements to the project management and version control features. In summary, MadCap Central will add control and safety to your Flare projects and is definitely worth a look.

One obvious question – is MadCap Central worth it if you’re a sole author working on one project? In my opinion, yes, if only for the version control system aspect. In fact, that may be the strongest selling point if you’re a sole author because you probably lack the time to deal with the complexity of installing and managing a traditional version control system. The fact that MadCap Central does that installation and management for you is a huge time saving.

Note – For a more detailed look at MadCap Central, watch the introductory webinar. Download it from the list of recorded webinars. Go to http://www.madcapsoftware.com/resources/recorded-webinars.aspx#central and look for “Introducing MadCap Central: An Overview + MadCap Flare 2016 r2” dated November 17, 2016. There’s a second one as well, dated December 15, 2016.

About the Author

Neil is president of Hyper/Word Services (www.hyperword.com) of Tewksbury, MA.  He has many years of experience in technical writing, with 32 in training, consulting, and developing for online formats and outputs ranging from WinHelp to mobile apps and a broad range of tools.

Neil has been using, training on, and consulting on MadCap Flare since 2004 and is MadCap-certified in Flare and Mimic. He is an STC Fellow, founded and managed the Bleeding Edge stem at the STC summit, and was a long-time columnist and contributor to STC Intercom, IEEE, ISTC Communicator, and other publications.  You can reach him at nperlin@nperlin.cnc.net.

Monday, July 13, 2015

Farewell to “Beyond the Bleeding Edge”

The Bleeding Edge was a series of presentations at the annual STC conference (now the Summit). Its goal was to address cutting-edge technologies and methodologies that emerged too close to the conference to be addressed by the standard presentation proposal route. I proposed it after the 1998 conference after hearing comments that there weren’t enough advanced sessions. After approval by then STC-president Mark Hannigan and Assistant to the President Deborah Sauer, I launched the Bleeding Edge in 1999. I ran it from 1999 to 2014 except for a two year hiatus due to some organizational issues in 2008 and 2009.

Bleeding Edge presentations covered JavaHelp coding, XHTML, haptic interfaces (IBM sent a speaker from London, as I recall), the W3C RDF metadata standard, search engine optimization, XSLT, on-demand publishing, and similar topics. My Beyond the Bleeding Edge column in STC Intercom came out of the Bleeding Edge. The Bleeding Edge also spun off a “standards watch” session, with speakers discussing developments in bodies like the W3C and IEEE, and several “standards watch” columns in Intercom.

The Summit organizers decided not to run the Bleeding Edge in 2015 because they thought the Summit’s technical level had risen to the point where the Bleeding Edge was no longer needed. From what I saw of the presentations in Columbus, I agree. Although I’ll miss the Bleeding Edge, its demise is a positive sign for the Summit overall.

My thanks again to Mark Hannigan and Deborah Sauer, and to all the presenters over the years who did such an outstanding job of helping keep STC on the cutting (or “bleeding”) edge.

Sunday, March 22, 2015

What’s New in MadCap Flare 11?

New versions of MadCap Flare combine powerful extensions to existing features and new features that go in unexpected and intriguing directions. Flare 11, released on March 17, continues this tradition. In this post, I’ll look at my favorite changes. (There’s far too much new to cover in one post. The What’s New Guide, http://docs.madcapsoftware.com/FlareV11/FlareWhatsNewGuide.pdf, is 350 pages long!)

By way of a brief introduction, I’m certified in Flare and Mimic and do a lot of training and consulting for MadCap so I’m not only a reviewer of Flare but a heavy user.

Extensions to Existing Features

User-Defined Macros

Help authoring often requires authors to perform the same set of steps over and over, such as applying a style to a series of paragraphs. It’s tedious work. Flare authors have been asking for a macros feature that lets them record the steps and play them back with a few clicks. This feature is now available in the Macros group on the Tools ribbon.

To use this feature, click the Record button, name the macro, and do the steps. When finished, click the Stop button (the renamed Record button). Select a macro to run by clicking the Playback button.

This feature is easy to use mechanically, but recording a macro records all your steps – mistakes too. So it’s hard to whip off a new macro on the fly unless it’s a simple one. But once authors get used to having to work carefully, macro creation is pretty simple and very useful.

Word Import Enhancements

Many Word users focus on producing documents that print smoothly, without regard to whether those documents can have a life beyond printing. Because of that, Word documents often have problems that cause trouble when imported into Flare – two in particular, both dealt with in v.11.

  • Authors who need to insert a screen shot in a Word document often just capture the screen and paste it into the document, but never save the screen as an image file.  This means Flare doesn’t know what to call the image file on import so it uses a random number for the file name, such as 0600001.jpg – technically correct but not very helpful.

    V. 11 partly fixes this. It names the pasted-in (embedded) image file after the name of the topic in which that image appeared. So Flare calls an embedded image in a Texas topic Texas. jpg, for example. This is a partial solution because if a topic has many embedded images, Flare creates multiple images files with names like Texas.jpg, Texas1.jpg, etc. Authors still have to figure out which image is which, but images being named after the topics that contain them simplifies the search.
  • Word authors who create tables usually calculate the number of rows required, then add a row for the column heads. Flare can designate a row specifically as a header and format that row using the Header settings in the Table Stylesheet editor. However, when you import the Word document into Flare, it has no defined header row. The solution has been to open Flare’s Table Properties dialog box and change the Number of Header Rows from 0 to 1. You then have to move the headings in the original heading row into the new, defined Header row and delete the old and now empty original header row. Easy but cumbersome.

    V. 11 fixes this. It can automatically convert the first row of a Word table to a Flare Header row. You’ll still have to clean up tables that have multi-line headers but single-header row tables will import far more easily. This feature is on the Options tab of the Word Import editor.

Cross-Reference Enhancements

I’ll start with a brief review of cross-references for Flare authors who aren’t familiar with them.

Cross-references are similar to hyperlinks but add two benefits.

  • They’re “aware of” their target title and change their wording if the title changes. For example, say you create a cross-reference to a topic called Grinder. The cross-reference wording will say ‘See “Grinder”’. If you then change the target topic title to Hoagie, the cross-reference wording automatically updates itself to ‘See “Hoagie”’. This eliminates the manual editing needed if you use traditional hyperlinks to point to a target topic whose title may change.

  • They can change their format to a page reference when output to a print format. For example, a hyperlink like ‘See “Grinder”’ is fine as a clickable link in online output or a print output viewed online, such as an on-screen PDF. However, if readers print the PDF, the link obviously doesn’t work – the reader can’t tell what page the link pointed to. This means the reader has to refer to the table of contents or index to locate the target of the reference. But with a cross-reference, the format automatically changes from a hyperlink-style like ‘See”Grinder”’ to a print style like ‘See “Grinder” on page 45’.

So what’s new with cross-references in v. 11?

Cross-reference granularity in prior versions of Flare could be too coarse. For example, a cross-reference might point to a target that wound up on the same page as the link. The result? A reference that said ‘See “Grinder” on page 45’ when the original link was also on page 45. In v.11, the cross-references are more sensitive to the context of the target. For example, if the target is on the same page as the link, the cross-reference wording is ‘See “Grinder” above” or ‘See “Grinder” below’, depending on the target’s position. If the target is on the previous or next page, the wording is ‘See “Grinder” on previous page’. And if the target if further away, the wording is ‘See “Grinder” on page 45’. The result is more realistic.

YouTube and Vimeo Movie Insertion Through the Flare Interface

Flare makes it easy to insert multimedia, such as Flash or HTML5 movies, into topics, but the assumption has usually been that the movies are part of the project. However, more authors use YouTube or Vimeo as movie distribution mechanisms or just want to link to movies from those sites, and v.11 makes it easy to add movie links directly from the web. Authors can either embed a movie in a topic using the Insert > Multimedia > YouTube/Vimeo option, in which case authors can set options like automatically starting a movie when a reader opens the topic, or linking to a movie using the Insert > Hyperlink option, in which case the reader must physically start the movie.

Interesting, Intriguing, and Sometimes Unexpected New Features

In no particular order (they’re all interesting)…

TopNav HTML5 Output

In 1989, starting a help system opened a single pane window that showed the topic. No navigation pane displayed until readers clicked a “Help Topics” button on the “button bar”. That opened the navigation pane in a separate window. Together, the two windows looked like this, navigation on the left, topic on the right:

In 1995, the release of WinHelp 4 introduced connected navigation and content panes that looked like this example (from Microsoft’s HTML Help) and was called the “tri-pane” window.

So the familiar tri-pane has been with us for 20 years. In recent years, however, Flare authors have been asking for a more web-like look. Some authors created it by hand by working directly in the code. In response, MadCap introduced the TopNav HTML5 output. TopNav has many options but the basic effect is to replace the tri-pane with something like this:

TopNav takes the table of contents and places it horizontally along the top of the window. Some layout elements have also been made individually selectable, so authors can create interfaces like this:

The introduction of the TopNav output has several ramifications. Three immediate one are:
  • TopNav looks cool but may not work for projects that have many level 1 TOC headings because too many headings will visually clutter the TopNav output.
  • TopNav adds many skin options. Using those options calls for more deliberate planning than the traditional tri-pane.
  • By breaking away from the traditional, documentation-related tri-pane look, TopNav may allow technical communicators to move into new publishing areas beyond traditional help.

By offering an immediate change in how we design online help and documentation, I consider TopNav to be one of the most meaningful new features in v.11.

Doc-to-Help Import

For some companies that create Word-based documentation and just need to put it online, Flare may be over-powered. In response, MadCap bought GrapeCity’s Doc-To_Help authoring tool in January. The idea was that authors who didn’t need Flare’s power could use Doc-To-Help instead. However, if those authors decide that they need more power, they can import the Doc-To-Help project into Flare.

U3D 3D Model Import

If your documentation contains engineering drawings, your engineers can save the drawings in Universal 3D (U3D) format. You can then insert the U3D files in browser-based and PDF outputs. Users can then click on the images and rotate them or zoom in and out. (To try it, go to page 173 of the What’s New Guide (http://docs.madcapsoftware.com/FlareV11/FlareWhatsNewGuide.pdf), click on the image in the example, and drag to rotate the image or use your mouse wheel to expand or shrink it.)

Augmented Reality

Finally, the unexpected – augmented reality. Unlike virtual reality, which takes users into a new reality like a game, augmented reality keeps users in this world but adds a functional layer when users view that world on a mobile device. Augmented reality seems to be most commonly thought of in terms of marketing. For example, Starbuck’s Cup Magic has let smartphone users scan specially imprinted cups that invoke an augmented reality layer atop the cup image. The image below, from www.interactivity.la, shows a Christmas cup that, when scanned, displays the singers on the smartphone screen.

Augmented reality goes beyond marketing. For example, the Theodolite app from Hunter Research and Technology (http://hunter.pairsite.com/theodolite/) superimposes compass, GPS, map, rangefinder, inclinometer, and other data onto a scene viewed on an iPhone screen, as shown below:

When would Flare authors use augmented reality? It’s hard to say. The idea is so new to tech comm that it allows functions we may never have thought of. One idea – field service information superimposed over the image of a machine being serviced.


And I haven’t discussed a whole range of other features such as:
  • Customizable keyboard shortcuts, a boon to accelerator key users.
  • Git integration, extending Flare’s version control system support.
  • Advanced page layout control, allowing very complex layouts for print output.
  • An image positioning feature that lets authors control how images fit within text without having to work with float properties in a CSS.
  • A global spelling dictionary that can be shared across multiple projects.
  • Building multiple targets in the background while continuing to work in the foreground.
  • And many more…

Between the extension of existing features and the inclusion of some unexpected new ones, Flare 11 is a major advance. I’m very impressed.

About the Author

Neil is an internationally known consultant, strategist, trainer, and developer for online content in forms ranging from online help to apps. He helps clients design content, select outputs, understand coding, and select and learn authoring tools. To do this, he brings decades of experience in tech comm, with 30 years in a wide range of online formats and tools. (He created the second and third commercial ebooks ever released, for MS-DOS 2.1 and Lotus 1-2-3 2.01 in 1987.) He also spent four years as an industry representative to the WorldWide Web Consortium in the 2000s.

Neil is certified by MadCap Software in Flare and Mimic, and by various other vendors. He is the author of “Advanced Features of MadCap Flare 10” (and earlier versions) and “Creating Mobile Apps Without Coding”, mobile app creation for non-programmers.

Neil writes columns and articles for various professional journals and is a popular speaker at professional conferences. In what passes for his spare time, he builds telescopes, cooks southern barbecue, and is using computer simulators to recreate a lost career as a US Navy fighter pilot. You can contact Neil at nperlin@nperlin.cnc.net or follow him on LinkedIn: https://www.linkedin.com/pub/neil-perlin, on Facebook at facebook.com/neil.perlin.7, and on Twitter at @NeilEric.

Monday, December 15, 2014

The Other Two CSS Books I Referenced in My STCTC Presentation on Dec. 9

Sorry for the delay in posting. I was doing a week of Flare consulting at a client in Houston and just got back to my office. Anyhow, the other two books that I suggested are:

  • The CSS Pocket Guide by Chris Casciano, Peachpit Press
  • Implementing Responsive Design by Chris Kadlec, New Riders

Wednesday, November 19, 2014

“Float” – CSS Feature and Symbol of Change

Ever since I started the Bleeding Edge session at the Society for Technical Communication Summit in 1999, I’m asked how quickly something new really emerges to affect technical communication. It doesn’t happen that often but it does happen – Microsoft’s introduction of HTML Help at the WinWriters conference in 1997 turned online help in a new direction in an hour. This column discusses another such example of change, the CSS “float” property. The float property’s impact won’t be as quick or dramatic as that of HTML Help but I think that what it symbolizes for tech comm is just as far-reaching.

The W3C introduced float in CSS1 in 1996. (See http://www.w3.org/TR/REC-CSS1/#floating-elements.) But it remained little known in technical communication until responsive design, promulgated in 2010, came to tech comm through help authoring tools in early 2014. In this column, I’ll briefly describe the float property’s function before turning to the larger issue of what I think it symbolizes for technical communication.

What’s “Float”

Float is a CSS property that lets us position elements on HTML pages. No big deal, you say. We’ve done that for years using simple inserts. True. What if we need multiple graphics side-by-side on a page? Again, no big deal. Create a table, hide its row and cell borders, and insert the graphics in adjacent cells in a row. Philosophically, using tables for page composition is wrong but it’s worked fine for years. Until responsive design arrived.

Responsive design lets us create one (the crucial word) online output that automatically reformats itself for the device on which it’s displayed. For example, say you have to create online help to run on large-screen devices like desktops and laptops and small screen devices like smartphones. You can create two outputs, each designed for its target device. But now add support for 10” tablets? That’s three outputs. Then 7” tablets? That’s four outputs. At some point, you won’t have enough resources to create and maintain all your different outputs. Responsive design solves this problem.

Responsive design lets you create one output that can detect the properties of the device on which it’s displayed and tailor itself accordingly. For example, three graphics laid out horizontally when displayed on a large screen automatically shift to a vertical format as the screen gets narrower. On the first screen below, I inserted the first group of three graphics in a table. I inserted each graphic in the second group normally – not in a table – but specified a left float for it. On a wide screen, there’s no difference.

As the screen narrows however, like shrinking to tablet size, the graphics in the table can’t shift because the table controls the layout. The result is the horizontal scroll bar. But the graphics in the second group, controlled by the float setting, automatically start shifting to a vertical format shown in the next image.

As the screen narrows further, to smartphone screen size, the graphics in the table still can’t shift but the second set of graphics, controlled by the float setting, automatically shift to a full vertical format as shown below.

Float also lets us move whole columns, change how text aligns next to images, and more. This is what lets us create the “fluid grids” that give responsive design much of its layout flexibility.

The float property can get very complex but it’s easy to understand and apply for most online help and documentation projects. For example, to get the graphics to behave as shown in the figures above, the code is simply this:

Your help authoring tool’s stylesheet editor lets you add the floats without getting into the actual code. You can start experimenting with it now.

What’s the Symbolic Importance of the “Float” Property?

Why spend an entire column on a little-known piece of CSS code? In my opinion, float symbolizes four shifts taking place within technical communication.

·         Online superseding print – If you only output print, float is irrelevant. But if you output print and online or online only, you should optimize your content for online. Some techniques for doing so have been available to technical communicators for years, like using relative size units (em, rem, or %) for text rather than the familiar points, or embedding index entries. Float is the latest such technique to reach us. The more you think “online” first, the more in tune you’ll be with changes in technical communication.

·         Growing interest in output to mobile – For years, computer screens were so large that we rarely had to worry about screen real estate. But growing interest in mobile as a single source output option makes it increasingly important to find automated ways to use the same content on different-sized screens. Programmatically-controlled layout modification techniques like float do that and let us adapt quickly as new output requirements appear.

·         HTML5 output – HTML5 output itself doesn’t need floated graphics. But one of HTML5’s benefits is responsive design, and you’ll want to look at using float to make the most effective use of responsive design.

·         Increased development rigor – Poor development practices like HTML tags with no end tags and tables created by using the tab key to create columns have largely vanished as our authoring tools and practices improved. Others, like local/inline formatting, are slowly vanishing as more authors use styles. The result is that improvements in programming practices are reaching increasingly esoteric areas like graphic positioning control. We’ll never totally eliminate bad practices and “hacks” but we’ll minimize them through techniques like float.


The symbolic effect of float is that it illustrates how web coding practices are increasingly available to the technical communication world. As technical communication moves away from “writing” and toward “content” and the lines between web development and technical communication continue to blur, techniques like “float” push technical communicators closer to web developers, letting us future-proof our material and our jobs and get into increasingly interesting work.

About the Author

Neil is president of Hyper/Word Services (www.hyperword.com) of Tewksbury, MA.  He has 35 years of experience in technical writing, with 29 in training, consulting, and developing for online formats and tools including WinHelp, HTML Help, JavaHelp, CE Help, XML, RoboHelp, Flare, and others now almost unknown.  Neil is MadCap-certified for Flare and Mimic, Adobe-certified for RoboHelp, and Viziapps-certified for the ViziApps mobile app development platform. He is an STC Fellow and the founder and manager of the Beyond the Bleeding Edge stem at the STC summit.  You can reach him at nperlin@nperlin.cnc.net.

Thanks to Allen Beebe, Cheryl Landes, and Deborah Sauer for their comments.

This post first appeared in the Society for Technical Communication's Intercom magazine (intercom.stc.org)

Tuesday, October 14, 2014

Book On Responsive Design

Per my presentation on responsive design at Lavacon on Monday, here are two books that I'd immediately recommend on responsive design and CSS.

- "Implementing Responsive Design" by Tim Kadlec, New Riders. Written more for programmers than help authors, but I'd recommend this book for the people at the presentation who were looking to go beyond what a help authoring tool can do through the GUI.

"The CSS Pocket Guide" by Chris Casciano, Peachpit Press. A easily digestible summary of the depths of the Cascading Style Sheet standard.

Sunday, July 20, 2014

Questions From My July 18 STC Webinar on CSS

Mary C: Does RoboHelp provide a basic CSS that one can adapt?
Yes. When you create a new RH project, RH automatically creates a basic CSS called default.css. You can use this CSS and modify its properties, or (my suggestion) copy it, save the copy with a name that ties it to the project or (better) your company (in order to be able to apply it to multiple projects), and modify its properties.

Ellen C: Is it possible to create unnumbered items in a numbered list in Word?
Yes, but there doesn’t seem to be a way to do that the way you would in HTML and CSS (or else I couldn’t find it). To do so manually, press Shift/Enter after a numbered item to add an unnumbered paragraph that keeps the indent and doesn’t change the sequence of the next number. Keep pressing Shift/Enter to add more unnumbered paragraphs. When you finish, press Enter to go back to regular numbering style.

David M: What application do you recommend to create a CSS?
It depends. Do you want to create a CSS for a project done in an authoring tool or do you want to create a CSS independently of any project or tool? Email me at nperlin@nperlin.cnc.net to let me know and we can discuss from there.

Suzanne S: I'm currently using RH10 and we will be upgrading to RH11 for responsive design. Fonts and margins are currently defined in point sizes. To make the output work, do we need to make modifications to the style sheet to use relative size units?
The more you use relative size units the better the responsive design will be.

Barbara: I took over a project with many tags with the style within each tag. I have changed this by adding classes like p class=BodyText" and so on. Is this not correct?
You’re correct. The fewer the sub-classes the better, but you definitely want to replace inline formatting with sub-classes.