I see a need for (further) improving
- Documentation of installation - the documentation today is short and compact and partly hard to penetrate. Many questions asked around the web are the same and are actually answered in the install docs. Possibly split it into Short instructions" for the experienced and "Detailed instructions" for beginners or troubleshooting. (Documentation of usage is not as important - most users will just use it and never read the docs.)
- Configuration and integration with CMS:s - Today, several files may have to be edited when installing and configuring FCKeditor in a CMS environment (config files, php files may need to be changed, different files to change when using file browser or CKfinder. Plus that the CMS also has to be configured. A true plug-and-play solution where the CMS can be used to configure everything in FCKeditor is ideal. One file with settings for the editor that imports/exports settings to/from file browser, CKfinder or plugins. This file should also be able to import/export relevant settings from/to any CMS. The CMS administrator should not have to edit FCKeditor files to change local settings like directories.
The bottom line is that FCKeditor should be truly plug-and-play with any CMS (with some effort from the CMS developers of course).
FCKeditor plugins must be truly plug-and-play with FCKeditor.
- Documentation of installation - the documentation today is short and compact and partly hard to penetrate. Many questions asked around the web are the same and are actually answered in the install docs. Possibly split it into Short instructions" for the experienced and "Detailed instructions" for beginners or troubleshooting. (Documentation of usage is not as important - most users will just use it and never read the docs.)
- Configuration and integration with CMS:s - Today, several files may have to be edited when installing and configuring FCKeditor in a CMS environment (config files, php files may need to be changed, different files to change when using file browser or CKfinder. Plus that the CMS also has to be configured. A true plug-and-play solution where the CMS can be used to configure everything in FCKeditor is ideal. One file with settings for the editor that imports/exports settings to/from file browser, CKfinder or plugins. This file should also be able to import/export relevant settings from/to any CMS. The CMS administrator should not have to edit FCKeditor files to change local settings like directories.
The bottom line is that FCKeditor should be truly plug-and-play with any CMS (with some effort from the CMS developers of course).
FCKeditor plugins must be truly plug-and-play with FCKeditor.