The user can fold sections and blocks using the small +/- symbols on the left of the editor. Folded sections and blocks show their first line except when this is block id (like [[id]]).

The structure of the file Alt+7 shows the hierarchy of sections and blocks with titles. This contains (if available) the first block attribute element (like \[source], \[quote] or \[verse]) and the title of the block or section. If an element like an image::[] references another file, it shows the icon of the file and the file’s name. If an include::[] references an AsciiDoc file, it includes the file as a sub-tree in the structure view. Clicking on either a referenced file or an element of a sub-tree opens the referenced file.

The search all view ShiftShift shows section titles and IDs of blocks.

The breadcrumbs view (bottom of the editor) shows the hierarchy leading to the current sections and blocks. It contains the same elements like in the structure view for the cursor position.

For include::[] and image::[] block macros the keys Ctrl+Click and Ctrl+B navigate to the referenced file.

For references (like <<id>>) the keys Ctrl+Click and Ctrl+B navigate to the reference (like [[id]]). This works similarly for attributes ({attrib} and :attrib:). “Find Usages” (Alt+F7) finds usages of references and attributes and allows navigation.

The user can show quick documentation for the element at the cursor’s position using Ctrl+Q. At the moments this works for attributes ({attrib} and :attrib:) both in the editor and when using autocomplete.

The plugin highlights matching braces including symmetric formatting for bold, italic and monospace. When the user selected some text and types a formatting character like _ or *, the selected text is formatted by adding the formatting at the beginning and end of the selected text. The plugin uses constrained/unconstrained formatting as necessary. If the selected text is already formatting with the chosen formatting, the plugin removes the formatting from the selected text.

The the plugin will expand the current selection when the user presses Ctrl+W and will contract the current selection when the user presses Ctrl+Shift+W.

IntelliJ’s built-in spell checker verifies all text areas of the document. It underlines unknown words with a green wavy line. With the context menu the user can change the spelling or to add the word to the project’s dictionary. To enable spell-checking support for other languages, the user can add a dictionary file via “Editor | Spelling”. Dictionaries are available online for example at http://www.winedt.org/dict.html. Word lists need to be in the UTF-8 format to work.

During rendering Asciidoctor might indicate problems in the file including a line number. The editor shows them as red and yellow annotations. Hover over the annotations to see the full warning or error message. The user can disable this feature in the settings. If it is disabled in the settings, errors show up in the event log.

When the text contains Markdown style headings (starting with #) or old style Asciidoc headings (titles underlined with string or characters matching the length or the heading), the editor highlights this in yellow and offers a quick fix to convert these to a new style Asciidoc heading.

The editor supports a default and dark theme. The user can change the colors of the theme in the IDE settings.

When using listings with [source,lang], the plugin triggers language injection to the following code block when the language is supported by the IDE (either by default, or by a language plugin). This allows syntax highlighting and code completion specific to the language of the code block. The user can disable this feature in the settings completely or for selected languages. For the user to re-format the code block, use “Edit Fragment” (Alt+Enter) and “Reformat Code” ( Ctrl+Shift+L).

All comments containing a TODO and FIXME and are indexed in the Todo-View (Alt+6). The user can configure the keywords in the IDE settings.

In the editor the user can select from a list of browsers that are showing in the upper right corner of the editor to preview the document. The user can also trigger this action from the context menu. To update the preview in the browser the user needs to refresh the contents by pressing F5 in the browser.

The user can open an AsciiDoc file in an external tool (like for example Google Chrome with the Asciidoctor Extension installed). To do this, add Chrome as an external Tool in the settings. Provide $FilePath$ as the argument so that Chrome knows where to find the file. The user can assign a shortcut to the external tool using “Help | Find action…​ | (type the name of external tool) | Alt+Enter | (type the shortcut of choice) | OK”.

When adding block attributes, the plugin supports statement completion (also known as “Smart Enter”) using the shortcut Shift+Ctrl+Enter. For example: a [source,java receives a closing bracket and two listing separator lines.

When the user opens a quote or a bracket, the plugin automatically adds a closing quote if it followed by whitespace or a closing bracket.

For references, attributes and images, and several macros like include, image and diagrams it provides auto-completion using Ctrl+Space. References and attributes support renaming within a project.

When auto-completing folder and file names in macros, the plugin tries to resolves attributes using their values specified in the current file or other files. For image macros it tries to find a declaration of the imagesDir attribute either in any of the Asciidoc files of the project.

There are several live templates included. Once the user starts typing ad, a list of templates appears. Continued typing of any character of the template name restricts the list. A Tab selects and entry.

The user can copy images from the clipboard into the document. To do that user selects “Paste image from clipboard” from the editor’s icon menu or from the context menu. If the clipboard contains a reference to an existing file, the user can choose to copy the file to the project or to just create a reference to the image in the AsciiDoc document. If the clipboard contains an image, the user can choose to create a JPEG or PNG file from the clipboard and add the reference to the document.

As a shortcut the user can also use Ctrl+C and Ctrl+V to add references to images from within the project to a document. This shortcut doesn’t work yet for copying contents from outside the project.

The editor runs inspections on the content. Once it finds for example Markdown-styled headings, Markdown-styled horizontal rules or Markdown-styled listings it highlights this as a warning. The user can use Ctrl+Enter to select a quick-fix to convert these to AsciiDoc syntax.

The user can extract and inline includes. This is available from the “Refactor” context menu and via context-sensitive intentions via Alt+Enter (“Inline Include Directive” and “Extract Include Directive”). Extract will extract either the currently selected text, the current block or the current section including subsections. Inline will inline the complete referenced file at the current include; optionally it can provide a preview, inline all occurrences of the file and delete the included file afterwards. All of these changes can be undone (Ctrl+Z).

The user can disable and enable intentions in “Settings…​ | Editor | Intentions | AsciiDoc”.

The user can reformat the source in the editor using “Reformat Code” (Ctrl+Alt+L). The user can disable formatting completely or configure parameters using “Settings…​ | Editor | Code Style | AsciiDoc”. Currently it adjusts empty lines around headings, lists and blocks. It also adjusts spaces around list items.

By default it re-format blocks to the one-sentence-per-line convention. The user can disable this in the code style settings.

To provide a common set of variables when rendering the preview, the plugin reads an .asciidoctorconfig configuration file. Use this to optimize the preview the project contains a document that is split out to multiple include files. See Wiki page for details

Asciidoctor Extensions can provide additional macros. To see the rendered result in the preview, the plugin can use extensions during rendering. See Wiki page for details