Content reuse – a productivity booster or a vicious circle?
Single-source publishing is a powerful must-have feature that is normally among the top three competitive advantages for any professional help authoring solution – and for good reason. Single-sourcing reusable content lets you: Maintain consistency throughout your documentation in terms of style, terminology, the level of detail, and so on. Avoid making multiple updates when a user interface or a workflow changes.Reduce the review and editing effort.Reduce the localization costs.Automate the routine – reproducing the same pieces of content repeatedly adds mundane work and duplicates yo
Using Local History to Restore Code Fragments or Deleted Files
Continuing our series on how2pro with IntelliJ IDEA, today we’d like to tell you more about a good old feature that can turn out to be a real lifesaver: Local History. Unlike version control systems, which only keep track of the differences made between commits, local history offers much more. It automatically records your project’s revisions triggered by various events as you edit code, run tests, deploy applications, and so on. Acting as your personal version control system, local history lets you restore deleted files, bring back separate changes, or roll back to any state of a file even i
Managing Code Style on a Directory Level with EditorConfig
As we announced a short while ago, in the upcoming version 2019.2, IntelliJ IDEA and other IntelliJ-based IDEs are extending EditorConfig support, thus allowing you to manage all code style settings for each set of files individually. All you need to do is place an .editorconfig file in the root directory containing the files whose code style you want to define. You can have as many .editorconfig files within a project as needed, so you can specify different code styles for different modules. All options from the .editorconfig file are applied to the directory where it resides as well as all o