Site Opcode File Content

In case the opcode doesn't have any modulation and it has some associated opcode like on_loccN / on_hiccN, then using title is the right choice. Otherwise use opcode_name, so a modulation documentation file (a symlink to the opcode it modulates in source code) will use the correct references.

---
layout: "sfz/opcode"
title: "lovel / hivel"
---
(Here the auto-generated brief text description from syntax.yml db...)

This is just an example for an opcode extended description to be written in some
/opcodes/lovel.md markdown file.
This text is readable on any editor, with low or high resolutions.

## Examples

<!-- 3 backticks (```) here -->
lovel=value1
hivel=value2
<!-- 3 backticks (```) here -->

<!-- Here the auto-generated description table from syntax.yml db... -->

---
layout: "sfz/opcode"
opcode_name: "volume"
---
...

## Examples

<!-- 3 backticks (```) here -->
...
<!-- 3 backticks (```) here -->

<!-- Here the auto-generated description table from syntax.yml db... -->