![]() If that output is html you could match the target styles completely, or even reuse the stylesheets. The best practice is to align the display in the editor with the most common final output. ![]() So the visual design of your documents is very important for the overall look and feel. In the case of Content Editor, the document itself takes up the biggest part of the screen. If something looks good, it generally is more pleasurable to work with. The look and feel of any application has a big impact on the user experience. When you are using specializations it becomes even more important to look at how this is influencing the editing experience. ![]() Based on that you can tweak the experience using the methods described here. It will depend on your organization and your documentation what DITA elements are used and how they are used. Even though Knowledge Center comes with Content Editor preconfigured for the basic topic types, it is worthwhile to try to optimize the experience for people working with the editor.
0 Comments
Leave a Reply. |