Client Site Branding

You can customize the look and feel of Eagle Portal by using your client’s company logo, fonts, and color schemes for branding. Since customization is different for every client, the following sections describe some use cases and best practices to use as guidelines when customizing your Portal. You use the following files when working with branding and customization:

• Site.css

• Default.aspx

• Eagle.xml

• Web.config

Before you begin, review your client’s current Eagle Portal customizations. Also, make sure you have access to where Portal is installed, since the files you work with are located there. Always back up existing files before making any changes. A backup file allows you to revert back to Eagle Portal in its initial state if necessary. A good practice when backing up a file is to rename the original file to *.bakmmddyy and use the proper name for the copied file. For example, if you want to make changes to Default.aspx, make a copy of it and name it Default.aspxbakmmddyy. Name the new file you are working with Default.aspx. Do not give the new file a different name such as Default_edited.aspx,) because Eagle Portal requires correctly named files in order to work. Finally, document all the changes you are making for your client in a separate document.