Azul Docs

Documentation skeleton

Primary feature

Replace this sentence with a direct description of what the feature does and when a user should enable it.

Placeholder content

This page demonstrates the final hierarchy. Feature names, descriptions, requirements, and behavior can be replaced later.

Requirements

List anything the user must install, enable, configure, or understand before using this feature.

Availability Describe access level
Dependency Describe required feature
Default state Enabled or disabled

How it works

Explain the feature's behavior in plain language. Include what it changes, when it runs, and what the user should expect to see.

  1. Enable the parent feature Explain where the control appears and what must already be active.
  2. Choose its behavior Describe the available modes without repeating every nested option.
  3. Configure nested functions Link users to the detailed controls that become available.

Configuration

Document every control with its accepted values, default behavior, and any interaction with another feature.

setting_name

Explain what this setting changes and when it is useful.

Value type
mode

List available modes and explain the difference between them.

Selection

Nested functions

Use expandable entries when one feature unlocks several related controls. Each entry can also link to its own full page.

Nested function one Core behavior

Describe what this function adds, which parent feature it requires, and how its settings affect the result.

View configuration
Nested function two Optional behavior

Explain the optional behavior, common use case, limitations, and conflicts with other functions.

View configuration
Nested function three Advanced behavior

Reserve this entry for advanced behavior that needs more context than a short setting description.

View configuration

Troubleshooting

The feature does not appear

List required access, dependencies, supported versions, and steps to refresh the interface.

The feature does not activate

List known conflicts, required state, and the information users should include in a support ticket.