As I’ve been creating custom Articulate skins I’ve come across some tips and insights that I thought I’d share. (This isn’t a tutorial on how to create a skin from scratch. Just a few pieces of knowledge.)
——–Warning: This post is for Articulate Development Geeks————-
Package xml file:
– The <content title> tag seems to be what drives the name of the skin on the installation window.
– Don’t forget to use the version number. It saves a bunch of confusion later on.
Presenter Template xml file:
– Name this file anything that you’d like. Just make sure you reference it in the package file.
– Use the <htmlBgColor> tag to control the html color behind your skin. This can come in handy to match a canvas bkg or “side” color that you add to a skin.
– The name of this file becomes the name of the Player in the publish drop-down in Articulate.
– <playerbar> This are contains true/false statements to control parts of the original Articulate skin. Remember that a custom skin just “covers up” the existing default Articulate skin. If the <playerbar> audio control, play control, seekbar aren’t disabled then you will still be able to click on them through your custom skin. They almost act like invisible buttons that are on top of your custom skin. (messes things up…set them to false.)
– Our skins work in “no sidebar” view mode. You need to make sure you design for one of the 3 modes and then default your skin to the correct mode. (<display modes>in the presenter template xml file)
– Let the users know not to change the view mode in the Slide Properties.
Custom Articulate skins can get a bit tricky. Don’t forget to also check out the Articulate forums for more assistance and discussions.
Here are a few custom Articulate Players that we’ve created: