DocGuy Training
  • Blog
  • Training and Consulting
    • DocGuy Training
    • DocGuy Consulting
    • MiniMad – Modularized MadCap Flare Training
      • MiniMad A – Creating a Flare Project and Adding Content
      • Minimad B – Importing Content
      • MiniMad C – Templates and Master Project Linking
      • MiniMad D – Single Sourcing
      • MiniMad E – Everything You Need to Know About Printed Output
      • MiniMad F – Everything You Need To Know About Online Output
      • MiniMad G – Multimedia and Collaboration
      • MiniMad H – Source Control
  • Contact Me

Adding a custom logo to HTML 5 output

Home » Blog » MadCap Flare » Adding a custom logo to HTML 5 output
Adding a custom logo to HTML 5 output

Longtime Flare users may not find this post terribly interesting, but occasionally I get asked for help on adding a custom logo to HTML 5 output, so I decided to write a post on it to make it easier to reference in the future.

How do I add custom text or a custom logo to Flare’s HTML 5 webhelp output?

Adding custom text in the upper-left corner of Flare’s HTML 5 webhelp output isn’t easy. In fact, it isn’t supported (but it can be done). Instead of focusing on how to hack Flare to do this, I’ll suggest that you do this using a custom logo. This is pretty simple, if you have access to a semi-decent graphics program.

Step 1: Create the logo.

Instead of using regular text, go ahead and create a logo using your standard graphics program. Keep in mind the following considerations:

  • If any of your customers are using IE 6 or older, you want to save the image as a GIF file with a transparent background. If you try to use a PNG image, the “transparent” portion of your image will be rendered as black, which probably isn’t what you wanted.
  • If your customers are using IE 7 or newer, you can go ahead and save the image as a PNG file with a transparent background. Depending on your industry, you may be able to look at your software requirements to give you guidance here. If you sell some cloud or web-based software and your app requires IE 7 or newer, it’s safe to say your users will be using IE 7 or newer. (Some estimates say that about 10% of web traffic in 2011 was by users of IE6.)
  • If you want to use the standard HTML 5 skin, you’ll want your image to be about 60 pixels high. The width can be whatever you need.
  • If you use the HTML 5 DARK skin, you probably want to use white (or another light color) for the text, as it will display better against the dark background. If you use the HTML 5 LIGHT skin, you probably want to use black (or another dark color) for the text.
  • Save the image to a location in your project, generally in your Content/Images (or similar) folder. This makes it easy to find the image later, should you need it for something else.

Step 2: Edit the Skin file.

Now that you have an image created and in your project, you’re ready to actually add it to the skin file. The skin file is what determines the layout, colors, and functions of your HTML 5 output. If you want your help to look different than the standard HTML 5 output, the Skin Editor is where you want to spend some time.

In Flare*, open you project, and open the Project Organizer.

  1. In the Project > Skins folder, double-click the skin you want to edit.
  2. On the Styles tab, Select the Logo category, and in the Properties panel, expand the Background group.
  3. In the BackgroundImage property drop-down, select [Browse for Image].
    Adding Custom Logos in MadCap Flare for HTML 5 output
  4. In the Open dialog, browse to the logo image you want to use, and double-click it.
  5. Save the Skin.
Step 3: Publish the output.
With the skin updated, you are ready to publish the output to see the new logo in your output. If you have more than one skin in your project, make sure you have selected the correct skin in the Target you are publishing.

Did this post leave you with questions? Did you get the effect you wanted? Let me know in the comments, below.

—

* Steps in this blog post assume you are using Flare V8. You may need to adapt these steps if you are using a different version of MadCap Flare.

Share this:

  • Tweet
  • More
  • Print
  • Email

Like this:

Like Loading...

Related

May 31, 2017 Paul Pehrson

About the author

Paul Pehrson

Paul Pehrson is a senior information developer and certified MadCap Flare trainer. He is a MadCap MVP, and is a certified MadCap Advanced Developer. He has a degree in English with an emphasis in technical communication. Paul is an active member of the international tech comm community. Paul is the principal owner of DocGuy Training, a training and consulting firm specializing in MadCap's suite of authoring tools. If you are interested in MadCap Flare training, consulting, or contract work please fill out the contact form.

Related Posts

  • MadWorld 2018: Troubleshooting common problems in MadCap Flare
    MadWorld 2018: Troubleshooting common problems in MadCap FlareJune 3, 2018
  • MadWorld 2018: Setting up context-sensitive help
    MadWorld 2018: Setting up context-sensitive helpJune 3, 2018
  • MadWorld 2018: Go the distance with advanced Top Nav output
    MadWorld 2018: Go the distance with advanced Top Nav outputJune 3, 2018

Popular Posts

  • FTP in Internet Explorer 7.0
    FTP in Internet Explorer 7.0June 7, 2006
  • FTP in IE 7 revisited
    FTP in IE 7 revisitedNovember 20, 2006
  • MadCap Flare 4 Preview (aka Ten Things to Love about Flare 4)
    MadCap Flare 4 Preview (aka Ten Things to Love about Flare 4)September 2, 2008

Categories

  • Adobe Acrobat
  • Adobe FrameMaker
  • Adobe PhotoShop
  • Better Living
  • Books, Movies, Media
  • DocGuy Training
  • Featured
  • Flare Tip Tuesday
  • Friday Brainteaser
  • Fun
  • General
  • Grammar Corner
  • JavaScript
  • MadCap Capture
  • MadCap Flare
  • MadCap MadPak
  • MadWorld Conference
  • MiniMad
  • Opinion
  • PHP
  • Presentations
  • Programming
  • Software
  • STC
  • Technical Writing
  • Technology
  • Technology Trend Thursday
  • Themes
  • Tools
  • Uncategorized
  • Work

Tags

Blog browser Capture conference content reuse CSS CSS3 docguy training Flare Flare 8 Flare Certified Trainer Flare tip Flare Training Flare v8 HTML HTML5 Intermountain STC MadCap MadCap Capture MadCap Flare MadCap Flare Training MadCap Software MadCap training MadWorld MadWorld 2013 Madworld 2016 MadWorld conference MiniMad PDF review scripting snippets society for technical communication Software STC stcorg styles technical communication technical communication conference Technical Writing technical writing tools Technology tech writing Training webhelp

Subscribe to Blog via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 792 other subscribers

  • Privacy Policy
  • Copyright
  • Terms of Service & Privacy Policy
  • Paul Pehrson
  • Contact Me
loading Cancel
Post was not sent - check your email addresses!
Email check failed, please try again
Sorry, your blog cannot share posts by email.
%d bloggers like this: