New plug-in brings back the concept of stylesheets and promises to replace three native InDesign palettes.
While younger designers may not recognize the difference between styles and stylesheets, old hands remember the days when every layout had both. Styles are the re-usable recordings of individual paragraph and character formatting attributes we all use daily in InDesign, QuarkXPress, Illustrator, and even Microsoft Word. Most recently, InDesign CS2 added object styles–the ability to apply non-text attributes such as frame colors and insets, text wrap settings, drop shadows, and so on to any type of object, including text frames. Styles are applied one at a time, to a single object or passage of text, at a time. For instance, a magazine feature article must employ separate paragraph styles for each of the article’s title, subtitle, kicker, byline, first paragraph, body copy, captions, subheads, pullquotes, jump lines, and so forth.
Stylesheets are collections of styles. All of those styles that go into formatting a typical article would be grouped together under a stylesheet that says, this is the complete definition of our magazine’s feature articles. Another stylesheet would hold the styles to be used on a department page, and others for the cover, the table of contents, an inbrief news section, and on and on until every section and page of the magazine had its own stylesheet containing all the styles necessary to layout a complete issue to spec. In workflows where that one magazine is not the only project created, all of the individual stylesheets would be grouped under a master stylesheet named after the publication. In this way, styles from different projects are kept separate, and production artists aren’t left wondering which “Body Copy” paragraph style is to be applied to the “Politics” page.
Way back when, stylesheets were printed on paper inside envelopes we called job jackets. When you were assigned to a project, you were handed the job jacket containing the typical output specs (deliverable format, trim size, required bleed, and so forth) and stylesheets that spelled out what styles you would employ. When layout went digital, we lost a large measure of control that is only now beginning to re-emerge in the form of Job Definition Format (JDF), Digital Asset Management (DAM), and advanced flow control systems like the InDesign- and InCopy-based K4 or Quark’s Quark Publishing System. Despite the other back to the future movements, stylesheets are still missing.
Yesterday (literally), we were limited to InDesign’s ability to name styles whatever you wanted, then to base styles to each other in a cascading effect–Heading 3 (or “HC”) was based on Heading 2 (“HB”), which was based on Heading 1 (“HA”)–and, with a little InDesign magic, all of those formats could be applied in order. Still, the three styles palettes–Paragraph, Character, and Object–often became long, unweildly lists of style names (see Figure 1). Should the “LT HA” style be applied to the “Letter from the Editor” page, or the “Letters to the Editor” page? Knowing which style to use often involved referencing a printed key that explained the shorthand. Talk about error-prone and inefficient!
Today (literally), we have a return to actual stylesheets in the form of a free plug-in from RogueSheep, Style Flocker.
Style Grouping = Stylesheets
RogueSheep doesn’t actually use the word stylesheet, but that’s what Style Flocker does: It groups styles together to enable the use of true stylesheets. In the single Style Flocker palette (see Figure 2) all of a document’s paragraph, character, and object styles may be placed into “flocks” or groups, to create logical grouping of related styles.
Continuing with the magazine example, all the required paragraph styles for a feature article can be placed into a “Feature” group. But not just the paragraph styles. Character styles, such as those typically created for italic or smallcap text, various underlines, figure references, dropcaps, and list bullet and number characters may be placed in the “Feature” group to keep them separate and distinguisable from similar styles created for other sections of the magazine. The one Style Flocker palette group can even hold needed object styles created for illos (illustrations), callouts, tables, anchored objects, sidebars, caption text frames, and the feature article’s main text frame with options such as number of columns and inset variables.
InDesign scatters these three types of styles throughout their respective palettes, which is a programmer’s way of organizing, separating kinds of objects. Style Flocker organizes styles to fit the way designers work by bringing all the styles together into one list. Designers must recognize and care about the differences between, say, a paragraph style and object style, but what types of objects they style is not as important to a designer or production artist as what portion of the content they will format and when. By putting all three kinds of style definitions into user-definable groups, Style Flocker enables creatives to finally organize their styles according to project, section, page, or area of content. And, because styles on the palette retain their unique identifying icons, designers can still instantly discern a paragraph style from a character or object style, retaining that secondary, but still important, level of organization.
Even better, flocks are nestable. One flock may contain another, which contains two others, each of which having their own sub-groups, and so on.
Next: The Good
Well, it’s all very nice having this article about the plugin, but does anyone know what happened to the Rogue Sheep web site? I’ve never yet been able to get any response out of it, less gain a copy of this legendary plugin.
Andrew
I apologize for troubles accessing the RogueSheep website. There are certain geographic locations that are blocked for reasons we have not yet determined. Please send an email to support at roguesheep dot com and we’ll help as best we can. Thanks, Jeff