▪ Variables contain small text fragments that can be dynamically assigned during generation – for example, the product name, the version number, or similar. ▪ Templates and style overrides control the visual appearance of a generated document. You can control whether and how a particular piece of content appears in a generated document at multiple levels of granularity: ▪ Multiple designs : You can generate a document in any number of different designs, for example, if you sell the documented product as an OEM product. All documents generated from the source automatically inherit the new content and are equally up-to-date again. If anything changes in the next release of the software documented, you only have to change one place in the documentation source. Yet, you maintain all content in the same HelpNDoc project. Certain content may differ in these variants. For example, you can generate a documentation once as the documentation for the “Professional Edition” of a software and once as the documentation for the “Standard Edition” of the same software. ▪ Multiple variants : You can generate a document in different variants. ▪ Multiple output formats : You can generate different output formats from the same source: CHM, HTML (WebHelp), PDF, Word, EPUB, etc. HelpNDoc supports single source publishing at all levels: If required, the system also generates header files or equivalent files for various programming languages to enable context-sensitive help calls. ▪ Qt Help (a special format for the Qt framework) Hyperlinks to other topics or to external websites or files can be created with the help of a convenient dialog. via the ribbon or from the project library, and you can format the text by applying preset paragraph and character styles. Here you can edit the text, add tables, images, etc. Editing contentīasic editing essentially works like in any modern WYSIWYG editor. The menu has a typical Microsoft-inspired ribbon with a customizable quick access toolbar. ▪ Keywords : Here you can assign and manage the keywords for the alphabetical index.Īll window areas can be undocked, freely positioned, and docked again at any position as required. ▪ Topic properties : Here you can edit various properties of the open topic. These object can be used as often as needed. ▪ Library : Here you can select and manage all objects that are available in the project, such as images, videos, text variables, snippets, HTML code modules, etc. The main area of the program window is the editor. Furthermore, it is now easier than ever to clean a messy library holding old and obsolete media items.īut that’s not all, as the library item analyzer is powerful enough to find duplicate items and merge them! Your documentation project will reuse items and therefore use far less resources when viewed either online or offline by the end-user.As with most help authoring tools, by default there is a content tree on the left side of the program window to manage the document structure. You will never again provide a broken help or manual with missing media elements. That’s where the library item analyzer shines: each element in the library (picture, movie, document, HTML code and variable) is analyzed and a report is created to rapidly identify problematic items. It is also possible that a library item has been deleted even though it is still used within a topic, thus resulting in a broken media element in the final documentation. Over time, some unused library items might remain and will consume disk space while cluttering the library. While working on a documentation project, all media items are stored in the library for better re-usability and faster modification.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |