Setting It Up to Start a Custom Skin

This website contains links to software which is either no longer maintained or will be supported only until the end of 2019 (CKFinder 2). For the latest documentation about current CKSource projects, including software like CKEditor 4/CKEditor 5, CKFinder 3, Cloud Services, Letters, Accessibility Checker, please visit the new documentation website.

If you look for an information about very old versions of CKEditor, FCKeditor and CKFinder check also the CKEditor forum, which was closed in 2015. If not, please head to StackOverflow for support.

(Created page with "{{#CUSTOMTITLE:Setting It Up to Start a Custom Skin}} The starting point of developing a skin is choosing an existing skin to base your work on. Starting a skin from scratch i...")
 
(No difference)

Latest revision as of 17:20, 26 July 2012

The starting point of developing a skin is choosing an existing skin to base your work on. Starting a skin from scratch is possible, but it is a lot of work. Actually, it is up to the skin developer to decide the road to take, but generally existing skins are good enough. We recommend the default Kama skin as the basis, because it is actively maintained and includes all possible features a skin can have.

You must have access to the "source files" of the selected skin. Distribution files are usually optimized for final use and are unreadable. Copy the source files in a folder inside the skins folder of a CKEditor installation. Give the folder name the name of your new skin (lower-cased, no spaces).

Now set the skin name in the CKEditor configuration file (config.js). For example: config.skin=’myskin’;

You're done, CKEditor will now start using your new skin files.

This page was last edited on 26 July 2012, at 17:20.