You can find the branding page in the Build Profile Editor. If you get stuck, use the search box at the top right of the app - you can search for "logo" or "branding" in there and it will take you to the right place. Let me know if you have any further problems.

I'm afraid that your post came through blank, and these forums are now closed - could you please repost in the new forums at http://support.innovasys.com/forums/21335913-general-question-answer

You can create a single Document! X project for all your assemblies if you want them documented together. You can either create that project from Visual Studio, or open up Document! X separately and add the assemblies to the project there. Let me know if you have any problems. 

If the assemblies in question are in the same directory as the one you are documenting (or the GAC) then this is normally a version issue - i.e. your assembly references version 1, but the assembly you have is version 2 - that kind of thing. If that doesn't help identify the problem, can you send through your project and assemblies to ...

As of today we are migrating our forums to a new service in order to provide enhanced functionality going forward, including voting, social network links, single sign in etc. You can navigate to the new forums using the Forums link on the website, or by visiting innovasys.userecho.com directly.

There is a slider at the bottom right of the HTML editor window that will change the zoom size. Alternatively you can hold down the Ctrl key and use your mouse wheel to change the zoom size.

We have focused on creating documentation for all of the various DXMETADATA element types in our 2012 release documentation, but we will now looking to further improve the configuration reference documentation by creating descriptions for the standard scraps in a future update. In the meantime, if there are specific scraps you want more ...

You can do this using the Filtering page in the Build Profile editor. Add a new Item Name Rule Condition, tick the Use RegEx checkbox and the Search in the fully qualified name checkbox. For your example, use the regular expression .*\.Legacy\.Tools.* as the Item Name *does not* match value. You could combine this Rule Condition ...

I believe that any existing Oracle database object descriptions will be used where available by Document! X. Are you not seeing them appear in the generated documentation? You can include comments in your Oracle procedure source code such that they will be used as a description by Document! X. Take a look at the Getting Started with Database ...

At present the order of stylesheets and script files will follow the order in which they were added to the project.