To repeat the subject: How is the CKEditor documentation generated? I went over the source tree and didn't see any documentation build scripts, tasks etc. I'd be grateful to get pointers to the tool(s) and template(s) used for generating the docs.
To repeat the subject: How is the CKEditor documentation generated? I went over the source tree and didn't see any documentation build scripts, tasks etc. I'd be grateful to get pointers to the tool(s) and template(s) used for generating the docs.
We are using the JSDuck
We are using the JSDuck engine, but the process is a bit too customized so it is not public. What is it exactly that you need?
Documentation Manager, CKSource
See CKEditor 5 docs, CKEditor 4 docs, CKEditor 3 docs, CKFinder 3 docs, CKFinder 2 docs for help.
Visit the new CKEditor SDK for samples showcasing editor features to try out and download!
That was just the information
That was just the information I needed. I tried jsdoc but the result was very inferior to what I see in your docs. Just switched to jsduck, modified the docs a bit and got just what I wanted. Thanx.
Actually, we're using a
Actually, we're using a little bit customised build of JSDuck as Anna mentioned. The source code is here: https://github.com/Reinmar/jsduck, but it's not trivial to compile it. Original JSDuck will work too, but the result will differ here and there. Not a big difference though.
Piotrek (Reinmar) Koszuliński
CKEditor JavaScript Developer
--
CKSource - http://cksource.com
--
Follow CKEditor on: Twitter | Facebook | Google+