What are the steps to modify an existing portal skin?

It is recommended to use the following procedure when modifying the skin:

1. Make a backup of your skin package
2. Make modifications to skin files
3. Test skin in a test environment
4. Move skin package to public environment
5. Restart the portal server
6. Verify skin changes within the portal

1. Make a backup of your skin package

The first step in modifying your skin is to make a backup. Having a backup provides two important advantages. One, there will be a valid, working copy to fall back on in case modifications cause the skin to be corrupted in such a way that it cannot be (or is chosen not to be) recovered. Two, there will be valid, working files to use as a reference as changes and modifications are made.

2. Make modifications to skin files

Modification of the skin files will generally fall into one of two categories: CSS or image.

Modifying Cascading Style Sheets

• Reference: How do I modify the skin CSS in Academus 2.x?
• Reference: How do I modify the skin CSS in Academus 1.5?

Modifying graphic images

Reference: How do I change an image of my skin in Academus?

3. Test skin in a test environment

Utilize a private test environment that mimics a production environment to test skin changes within the portal. This will produce the most accurate testing conditions to verify that skin changes render and behave as expected. Test changes on all supported OS/browser/version combinations. Make adjustments as necessary.

In addition to testing for errors, test for usability. Changes to the skin may have positive or negative impacts on usability, and it is important to determine whether skin changes have made the user interface more or less usable.

Usability testing is done by putting designs in front of actual or representative users and getting their feedback. This feedback will represent how a larger user group will receive skin/user interface changes and quickly identify issues before changes are released to the public. Overall, simply be aware that making changes to the skin/user interface will impact usability.

4. Move skin package to public environment

Once testing has been completed and the skin is deemed satisfactory for public release, copy the skin package directory in its entirety over to the skin directory on the public server. The changed skin package files must overwrite the existing (previous version) files.

5. Restart the portal server

Some skin modifications will not require a restart of the portal server. As restarting the server will clear any files cached on the server, this is a recommended - but not required - step.

6. Verify skin changes within the portal

Make a final testing pass on the public environment to ensure that changes are present and are behaving as expected. If problems arise, revert the public environment to a backup copy of the skin, restart the portal, and troubleshoot skin changes in the test environment.