Documentation
We would like to improve our documentation. What are you missing there, did you find any mistakes etc.?
-
create more and accurate documentation
The documentation is not extensive enough. Provide more code samples, descriptions of the input and output parameters and the exceptions.
75 votesstarted ·
Michal Neuwirth (Product Manager)
responded
We have already started to improve our documentation for version 6.0, including new API sample site and more.
-
Show documentation based on role.
If I am an admin I want hard core docs, if I am a new editor I want hand holding and links in my docs to my helpdesk or support channel, not kentico.
26 votesunder review ·Michal Neuwirth (Product Manager)
responded
Considering for next releases.
-
"save and publish" button when editing pages. 3 button clicks is tedious when updating many pages.
When making changes to large number of pages, clicking 3 button is tedious. If current user has publishing rights, add "save and publish" button which would save and publish/approve the page in one step.
13 votes -
better documentation
i think best refrence about any documantation could be MSDN.i as developer can find any thing such as samples,methode description,code snipet and atc.
you can do it as MSDN like documentation as documentation is one of very important to customers.without it any product is useless.kind regards
12 votesstarted ·Michal Neuwirth (Product Manager)
responded
Started for version 6.0 and will continue in next releases.
-
Document all the configuration settings.
I know there are a lot of "undocumented" configuration settings available for things like 301 redirects. It would be nice if there was a list of these in one of the manuals or documentation.
9 votesstarted ·Michal Neuwirth (Product Manager)
responded
We have started improvement of our documentation. If you will find something missing please post your suggestion here on Uservoice.
-
Provide kentico partners with internal build status updates
If we are communicating new features that are on the roadmap to clients, it would be nice to have insight into your production releases. Currently, their is no ONGOING progress information for releases. Something like percent complete, and current anticipated date. Information on page can emphasis that it is only an estimation.
6 votes -
Javadoc or sandcastle-style source code documentation
For those of us using ASPX templates, we need better documentation of the sourcecode. Even using a utility like Sancastle (http://www.codeproject.com/KB/dotnet/ccnetsandcastle.aspx) to generate MSDN-style HTML pages would be a great help.
I don't know about everyone else, but I can't count on using Visual Studio with Intellisense to do my editing, so often I don't even know what properties are avaliable within ASPx controls and the object APIs.Spending the time to create some thorough source code documentation with explanations or code samples would be essential to increasing our productivity.
4 votesstarted ·Michal Neuwirth (Product Manager)
responded
Working on for version 6.0
-
Redisign the online documentation needed
Please redisign the online help pages. Current design is so 2000s. At least remove the horizontal lines from TOC :) . As a developer I think it is important to have cleanly and inteligently designed help pages (considering the interface and the content).
1 votestarted ·
AdminMichal Vrana
(Admin, Kentico CMS)
responded
Hi. We are aware of this fact and we have good news for you. We are currently finalizing a new documentation skin and all on-line documentation at Kentico DevNet will be updated in near future. The same new skin will also be used for the built-in Context Help in Kentico CMS 7.
