Fredck: 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..."

2012-07-26T16:20:16Z

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..."

New page

{{#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 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 [[CKEditor_4.x/Skin_SDK/Introduction|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 <code>skins</code> 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 (<code>config.js</code>). For example: <code>config.skin=’myskin’;</code>

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

CKEditor 4.x/Skin SDK/Setup - Revision history

Fredck: 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..."