Skin Components and Proxies

Central Account

A Central Account proxy lets you create an account link drop-down, allowing users viewing private output to log out or edit their MadCap Central profile settings. By default, the account link is included automatically in the header of the regular skin. See Creating a Central Account Link.

After inserting a Central Account proxy, you can edit it. To do this, open the topic or master page where the proxy is inserted, right-click on it, and select Edit Central Account Proxy. You can also edit the look of the account link by editing the styles in the regular skin or the Central Account skin component that you used. See Headers in HTML5 Skins.

Favicons

Short for “favorite icons,” favicons are supported in Flare for HTML5 output. A favicon is the image that you sometimes see in a browser tab, address bar, bookmark, Windows tiles, etc. The Favicons skin component is the only one that is not associated with a proxy. Simply by adding and editing this type of skin component, your HTML5 output will include favicons in the appropriate locations. See Adding Favicons.

Menu

A Menu proxy lets you create a topic menu based on your TOC file, allowing users to navigate to other topics. This proxy can be especially useful if you are creating HTML5 Top Navigation or skinless output and you want a context-sensitive menu to display next to each topic. When you build the output, the proxy is replaced with the generated menu.

The Menu proxy and skin component allow users to access navigation unique to each topic, while the main navigation at the top of the page is typically limited to the first few levels of your TOC. This feature is not as common in Side Navigation or Tripane outputs, because those formats always include the full navigation on the side of topics.

When you insert a Menu proxy, the Menu Proxy dialog opens.

You can select the following options:

• Use TOC, Browse Sequence, or Headings If you have more than one TOC file in your project, you can select the one that the Menu proxy should use. It is most common to base a menu on a TOC, but you can also select a browse sequence.

  

  You also have the option of selecting “Headings,” which will display topic headings in the side menu instead. In other words, any headings or subheadings (e.g., h1, h2, h3, h4) that you’ve included in a topic will be shown in the side menu instead of other topics in the output.

  

  Also, when viewing a topic that is set up like this—and the menu is fixed in place (via the Setup tab of the Skin Editor)—each sub-heading section will be highlighted as you scroll down in the topic.

  

• Context sensitive Select this check box if you want the menu to show only closely related entries in the TOC. In Flare's Top Navigation project templates, this kind of proxy was inserted into a master page to create a side menu for most of the topics in the output.

  

  

  If you do not make the menu context-sensitive, it displays everything in the TOC (depending on the depth level you select).

• Include parent If you have selected the Context sensitive option, you can also select this check box to include the parent TOC item in the menu.

  

  

• Include siblings If you have selected the Context sensitive option, you can also select this check box to include TOC items in the menu that are on the same level as the open topic.

  

  

• Include children If you have selected the Context sensitive option, you can also select this check box to include TOC items in the menu that are children of the topic that is open.

  

  

• Levels to Show (Depth) This lets you choose how many levels of items deep in the TOC to include in the menu. If the Context sensitive option is disabled, this refers to the depth level overall for the TOC. If both the Context sensitive and the Include children options are enabled, it refers to the number of levels under the topic that is open.

• Skin File If you have added a Menu skin component to your project and want to use it to control the look of the menu, you can select it from this field. See Editing Skin Settings and HTML5 Skin Styles.

  If you do not select a Menu skin component in this field, Flare uses the first one it finds in your project (if one exists). Otherwise, Flare provides a default design.

Search Bar

A Search Bar proxy lets you create a field that can be used to perform searches in HTML5 output. When you build the output, the proxy is replaced with the generated search bar. If you insert a search bar using a proxy, you might also need to hide the search bar from some topics so that you do not have two search bars on a page.

When you insert a Search Bar proxy, the Search Bar Proxy dialog opens.

You can select the following:

• Skin File If you have added a search bar skin component to your project and want to use it to control the look of the search bar, you can select it from this field. See Editing Skin Settings and HTML5 Skin Styles.

  If you do not select a Search Bar skin component in this field, Flare uses the first one it finds in your project (if one exists). Otherwise, Flare provides a default design.

Search Results

A Search Results proxy works with the Search Bar proxy and lets you create a container that is used to display the results of end user searches in your output. When you build the output, the proxy is replaced with the generated search results.

When you insert this kind of proxy, the Search Results Proxy dialog opens.

You can select the following:

• Skin File A skin component lets you control the look of generated search results. If you have added multiple skin components to your project, you can use this field to select the one to associate with this proxy. You can then edit that skin component to change its appearance. See HTML5 Skin Styles.

Topic Toolbar

You can use the Topic Toolbar proxy to generate a toolbar anywhere in your topics. This is an alternative (or an additional option) to the web toolbar that can be included in some online outputs.

When you insert a Topic Toolbar proxy, the Topic Toolbar Proxy dialog opens.

Topic toolbars can be inserted into outputs other than HTML5. However, the Topic Toolbar skin component is supported in HTML5 only. Therefore, the Topic Toolbar Proxy dialog is split into two sections. The HTML5 Settings area pertains only to HTML5 output. The General Settings area pertains to all of the outputs that support topic toolbars, including HTML5. Anything that is set in the HTML5 Settings area overrides what is set in the General Settings area, including the buttons that are selected for the toolbar.

You can select the following options:

• Skin File If you have added an HTML5 Topic Toolbar skin component to your project and want to use it to control the look of the toolbar, you can select it from this field. From the Skin Editor, you can select the buttons to be included in the toolbar. Alternatively, you can select buttons from the Buttons field below. See Editing Skin Settings and HTML5 Skin Styles.

  If you do not select a Topic Toolbar component in this field, Flare uses the first one it finds in your project (if one exists). Otherwise, Flare provides a default design.

• Stylesheet class for proxy You can select a class to affect the look of the entire toolbar. This is an alternative, or supplement, to editing the skin component in the Skin Editor. However, for HTML5 output, using a skin component is the most common method for designing the look of the toolbar.

  You might create and use a proxy style class, for example, if you want to add a border around the toolbar. If you do not select a class from this field, the generated toolbar will use the style settings from the parent MadCap|topicToolbarProxy style. You have the option of creating a class for this proxy style in the Stylesheet Editor. To do this, select the MadCap|topicToolbarProxy style and in the local toolbar click Add Selector to create a class. The class will then be available from this field.

• Buttons You have the option of selecting buttons for a toolbar in the Skin Editor or by using this field. You can click Select buttons to open a dialog, then select the buttons to include in the toolbar. For HTML5 outputs, the Topic Toolbar proxy will use whatever settings are specified in a Topic Toolbar skin component (if you have added one to your project), overriding any buttons you may have selected directly in the proxy. If you have not associated a Topic Toolbar skin component with the proxy, Flare will just use the first one it finds in your project. However, for outputs using Standard and Mobile skins, the settings in the proxy take precedence over anything you may have set on the Toolbar tab in the Skin Editor. See Inserting and Editing a Topic Toolbar Proxy.