Skip to content
Kona

Language & editor support

Kona ships editor support for Crema templates so you can edit *.crema.html and *.crema.kt with highlighting, completion for directives, and warnings for unknown @names.

What you get

Section titled “What you get”
Piece Location Role
TextMate grammar ide-support/crema/ Shared scopes for VS Code / Cursor
Language server modules/lsp (org.konaframework:kona-lsp) Completions + diagnostics over LSP stdio
VS Code / Cursor extension ide-support/vscode-crema/ Language contribution + setup help
IntelliJ native plugin konaframework/kona-idea Crema file type, @/view/DB completion, tool window, Grind (no LSP)

Fastest path

Section titled “Fastest path”

IntelliJ IDEA

Section titled “IntelliJ IDEA”

Install the Kona Idea zip (Install Plugin from Disk…), restart, and open a *.crema.html view — language should read Crema. Details: IntelliJ.

VS Code / Cursor

Section titled “VS Code / Cursor”

  1. Open a Crema view with the VS Code extension (grammar from ide-support/crema/).

  2. Build the language server once:

    Terminal window
    ./gradlew :kona-lsp:jar

  3. Point the LSP client at:

    Terminal window
    java -jar modules/lsp/build/libs/kona-lsp-*.jar

From an application project you can also print the same reminder without starting a server:

Terminal window
./grind ide:lsp

Progressive guides

Section titled “Progressive guides”
  1. Crema grammar — what is highlighted and how to sync the TextMate files.
  2. Language server — protocol surface, Kotlin/Java usage in tests, running the jar.
  3. VS Code & Cursor — install the extension stub and wire crema.lsp.jarPath.
  4. IntelliJ — native Kona Idea plugin (no LSP; preferred for IntelliJ).

Crema template behavior itself (layouts, @foreach, stacks) is documented under Crema.