Skip to main content

Titles

Best used for section headers in your Aqualink documentation.

Subtitles

Best used for subsection headers like specific features or methods.
Each title and subtitle creates an anchor and also shows up on the table of contents on the right, making it easy for developers to navigate your Aqualink docs.

Text formatting

We support most markdown formatting. Simply add **, _, or ~ around text to format it. You can combine these. For example, write **_bold and italic_** to get bold and italic text. You need to use HTML to write superscript and subscript text. That is, add <sup> or <sub> around your text.

Linking to pages

You can add a link by wrapping text in [](). You would write [Discord.js Guide](https://discordjs.guide) to Discord.js Guide. Links to pages in your Aqualink docs need to be root-relative. Include the entire folder path. For example, [Player API](/api-reference/player) links to the Player API reference page.
Relative links like [Player API](../player) will open slower because we cannot optimize them as easily.

Code Examples

Since Aqualink is a code library, you’ll frequently need to show code examples:

Inline Code

Use backticks for inline code: client.aqua.createConnection() or player.play().

Code Blocks

Use triple backticks for code blocks with syntax highlighting:

Discord.js Integration Examples

For complete bot command examples, use this format:

Blockquotes

Single line

To create a blockquote, add a > in front of a paragraph.
The Aqualink library provides seamless integration with Discord.js for music bot development.

Multiline

Aqualink wraps the powerful Lavalink audio server to provide high-quality music streaming. It includes built-in queue management, audio filters, and failover support for production bots.

Music Bot Specific Formatting

Bot Commands

When documenting slash commands, use this format:

Configuration Examples

For configuration objects, use proper JSON formatting:

Event Documentation

Document events with clear formatting: Event: trackStart
Emitted: When a track begins playing
Parameters: track (Track object)
When documenting methods, always include both the method signature and a practical example showing how it would be used in a Discord bot.
Remember to mention any prerequisites like voice channel permissions or Lavalink server requirements in your documentation.
Use consistent formatting for all your API documentation to make it easy for developers to understand and implement Aqualink in their bots.