diff --git a/docs/entity-types-server.md b/docs/entity-types-server.md
index c7eaa4394..8383b64d8 100644
--- a/docs/entity-types-server.md
+++ b/docs/entity-types-server.md
@@ -4,7 +4,7 @@ Module `@zenstackhq/runtime/types` contains type definitions of entities, filter
 
 Suppose a `User` model is defined in ZModel:
 
-```prisma
+```zmodel
 model User {
     id String @id @default(cuid())
     email String @unique @email
diff --git a/docs/entity-types.md b/docs/entity-types.md
index c7eaa4394..8383b64d8 100644
--- a/docs/entity-types.md
+++ b/docs/entity-types.md
@@ -4,7 +4,7 @@ Module `@zenstackhq/runtime/types` contains type definitions of entities, filter
 
 Suppose a `User` model is defined in ZModel:
 
-```prisma
+```zmodel
 model User {
     id String @id @default(cuid())
     email String @unique @email
diff --git a/docs/get-started/learning-the-zmodel-language.md b/docs/get-started/learning-the-zmodel-language.md
index 1850d3216..27b01032e 100644
--- a/docs/get-started/learning-the-zmodel-language.md
+++ b/docs/get-started/learning-the-zmodel-language.md
@@ -9,7 +9,7 @@ Every model needs to include exactly one `datasource` declaration, providing inf
 
 The recommended way is to load the connection string from an environment variable, like:
 
-```prisma
+```zmodel
 datasource db {
     provider = "postgresql"
     url = env("DATABASE_URL")
@@ -24,7 +24,7 @@ Data models define the shapes of entities in your application domain. They inclu
 
 Here's an example of a blog post model:
 
-```prisma
+```zmodel
 model Post {
     // the mandatory primary key of this model with a default UUID value
     id String @id @default(uuid())
@@ -59,7 +59,7 @@ Attributes attached to fields are prefixed with '@', and those to models are pre
 
 Here're some examples of commonly used attributes:
 
-```prisma
+```zmodel
 model Post {
     // @id is a field attribute, marking the field as a primary key
     // @default is another field attribute for specifying a default value for the field if it's not given at creation time
@@ -97,7 +97,7 @@ ZenStack inherits most attributes and functions from Prisma, and added a number
 
     You can override the default setting with the `saltLength` or `salt` named parameters, like:
 
-```prisma
+```zmodel
 model User {
     password String @password(saltLength: 16)
 }
@@ -115,7 +115,7 @@ If both `saltLength` and `salt` parameters are provided, `salt` is used.
 
     E.g.:
 
-```prisma
+```zmodel
 model User {
     password String @password @omit
 }
@@ -129,7 +129,7 @@ The special `@relation` attribute expresses relations between data models. Here'
 
 -   One-to-one
 
-```prisma
+```zmodel
 model User {
     id String @id
     profile Profile?
@@ -144,7 +144,7 @@ model Profile {
 
 -   One-to-many
 
-```prisma
+```zmodel
 model User {
     id String @id
     posts Post[]
@@ -159,7 +159,7 @@ model Post {
 
 -   Many-to-many
 
-```prisma
+```zmodel
 model Space {
     id String @id
     members Membership[]
@@ -194,7 +194,7 @@ This document serves as a quick overview for starting with the ZModel language.
 
 Access policies express authorization logic in a declarative way. They use `@@allow` and `@@deny` rules to specify the eligibility of an operation over a model entity. The signatures of the attributes are:
 
-```prisma
+```zmodel
 @@allow(operation, condition)
 @@deny(operation, condition)
 ```
@@ -216,26 +216,26 @@ You can use `auth()` to:
 
 -   Check if a user is logged in
 
-```prisma
+```zmodel
 @@deny('all', auth() == null)
 ```
 
 -   Access user's fields
 
-```prisma
+```zmodel
 @@allow('update', auth().role == 'ADMIN')
 ```
 
 -   Compare user identity
 
-```prisma
+```zmodel
 // owner is a relation field to User model
 @@allow('update', auth() == owner)
 ```
 
 ### A simple example with Post model
 
-```prisma
+```zmodel
 model Post {
     // reject all operations if user's not logged in
     @@deny('all', auth() == null)
@@ -250,7 +250,7 @@ model Post {
 
 ### A more complex example with multi-user spaces
 
-```prisma
+```zmodel
 model Space {
     id String @id
     members Membership[]
@@ -322,7 +322,7 @@ model User {
 
 As you've seen in the examples above, you can access fields from relations in policy expressions. For example, to express "a user can be read by any user sharing a space" in the `User` model, you can directly read into its `membership` field.
 
-```prisma
+```zmodel
     @@allow('read', membership?[space.members?[user == auth()]])
 ```
 
@@ -358,7 +358,7 @@ Collection predicate expressions are boolean expressions used to express conditi
 
 The `condition` expression has direct access to fields defined in the model of `collection`. E.g.:
 
-```prisma
+```zmodel
     @@allow('read', members?[user == auth()])
 ```
 
@@ -366,7 +366,7 @@ The `condition` expression has direct access to fields defined in the model of `
 
 Also, collection predicates can be nested to express complex conditions involving multi-level relation lookup. E.g.:
 
-```prisma
+```zmodel
     @@allow('read', membership?[space.members?[user == auth()]])
 ```
 
@@ -434,7 +434,7 @@ The following attributes can be used to attach field constraints:
 
 ### Sample usage
 
-```prisma
+```zmodel
 model User {
     id String @id
     handle String @regex("^[0-9a-zA-Z]{4,16}$")
diff --git a/docs/get-started/next-js.md b/docs/get-started/next-js.md
index a67201fb8..1387e9f5d 100644
--- a/docs/get-started/next-js.md
+++ b/docs/get-started/next-js.md
@@ -59,7 +59,7 @@ npm i @zenstackhq/runtime
 
     Here's an example of using a Postgres database with connection string specified in `DATABASE_URL` environment variable:
 
-```prisma
+```zmodel
 datasource db {
     provider = 'postgresql'
     url = env('DATABASE_URL')
diff --git a/docs/index.html b/docs/index.html
index 0b81d0098..c470e1a76 100644
--- a/docs/index.html
+++ b/docs/index.html
@@ -76,6 +76,7 @@
         <script src="//cdn.jsdelivr.net/npm/docsify/lib/plugins/ga.min.js"></script>
         <script src="https://cdn.jsdelivr.net/npm/prismjs@1.29.0/components/prism-typescript.min.js"></script>
         <script src="https://cdn.jsdelivr.net/npm/prismjs@1.29.0/components/prism-json.min.js"></script>
+        <script src="https://cdn.jsdelivr.net/npm/zenstack@dev/bundle/res/prism-zmodel.js"></script>
     </body>
 
     <style>
diff --git a/docs/integrating-authentication.md b/docs/integrating-authentication.md
index 1379b3c07..e81a069f1 100644
--- a/docs/integrating-authentication.md
+++ b/docs/integrating-authentication.md
@@ -58,7 +58,7 @@ export default NextAuth(authOptions);
 
 NextAuth is agnostic about the type of underlying database, but it requires certain table structures, depending on how you configure it. Your ZModel definitions should reflect these requirements. A sample `User` model is shown here (to be used with `CredentialsProvider`):
 
-```prisma
+```zmodel
 model User {
     id String @id @default(cuid())
     email String @unique @email
diff --git a/docs/modeling-your-app.md b/docs/modeling-your-app.md
index 46bd79974..af6a64d9b 100644
--- a/docs/modeling-your-app.md
+++ b/docs/modeling-your-app.md
@@ -10,7 +10,7 @@ The very first thing to do is to configure how to connect to your database.
 
 Here's an example for using a PosgreSQL with is connection string read from `DATABASE_URL` environment variable:
 
-```prisma
+```zmodel
 datasource db {
     provider = "postgresql"
     url = env("DATABASE_URL")
@@ -25,7 +25,7 @@ Data models define the shapes of business entities in your app. A data model con
 
 Here's an example of a blog post model:
 
-```prisma
+```zmodel
 model Post {
     // @id attribute marks a field as unique identifier,
     // mapped to database table's primary key
@@ -59,7 +59,7 @@ Here are some examples:
 
 -   One-to-one
 
-```prisma
+```zmodel
 model User {
     id String @id
     profile Profile?
@@ -74,7 +74,7 @@ model Profile {
 
 -   One-to-many
 
-```prisma
+```zmodel
 model User {
     id String @id
     posts Post[]
@@ -89,7 +89,7 @@ model Post {
 
 -   Many-to-many
 
-```prisma
+```zmodel
 model Space {
     id String @id
     members Membership[]
@@ -135,7 +135,7 @@ A few quick notes before diving into examples:
 
 Let's look at a few examples now:
 
-```prisma
+```zmodel
 model User {
     id String @id
     posts Post[]
diff --git a/docs/zmodel-access-policy.md b/docs/zmodel-access-policy.md
index 941c43ecd..9ecdcd83f 100644
--- a/docs/zmodel-access-policy.md
+++ b/docs/zmodel-access-policy.md
@@ -4,7 +4,7 @@ Access policies use `@@allow` and `@@deny` rules to specify the eligibility of a
 
 -   `@@allow`
 
-    ```prisma
+    ```zmodel
         attribute @@allow(_ operation: String, _ condition: Boolean)
     ```
 
@@ -17,7 +17,7 @@ Access policies use `@@allow` and `@@deny` rules to specify the eligibility of a
 
 -   `@@deny`
 
-    ```prisma
+    ```zmodel
         attribute @@deny(_ operation: String, _ condition: Boolean)
     ```
 
@@ -36,19 +36,19 @@ You can use `auth()` to:
 
 -   Check if a user is logged in
 
-    ```prisma
+    ```zmodel
     @@deny('all', auth() == null)
     ```
 
 -   Access user's fields
 
-    ```prisma
+    ```zmodel
     @@allow('update', auth().role == 'ADMIN')
     ```
 
 -   Compare user identity
 
-    ```prisma
+    ```zmodel
     // owner is a relation field to User model
     @@allow('update', auth() == owner)
     ```
@@ -57,7 +57,7 @@ You can use `auth()` to:
 
 As you've seen in the examples above, you can access fields from relations in policy expressions. For example, to express "a user can be read by any user sharing a space" in the `User` model, you can directly read into its `membership` field.
 
-```prisma
+```zmodel
     @@allow('read', membership?[space.members?[user == auth()]])
 ```
 
@@ -93,7 +93,7 @@ Collection predicate expressions are boolean expressions used to express conditi
 
 The `condition` expression has direct access to fields defined in the model of `collection`. E.g.:
 
-```prisma
+```zmodel
     @@allow('read', members?[user == auth()])
 ```
 
@@ -101,7 +101,7 @@ The `condition` expression has direct access to fields defined in the model of `
 
 Also, collection predicates can be nested to express complex conditions involving multi-level relation lookup. E.g.:
 
-```prisma
+```zmodel
     @@allow('read', membership?[space.members?[user == auth()]])
 ```
 
@@ -119,7 +119,7 @@ A data model can contain arbitrary number of policy rules. The logic of combinin
 
 ### A simple example with Post model
 
-```prisma
+```zmodel
 model Post {
     // reject all operations if user's not logged in
     @@deny('all', auth() == null)
@@ -134,7 +134,7 @@ model Post {
 
 ### A more complex example with multi-user spaces
 
-```prisma
+```zmodel
 model Space {
     id String @id
     members Membership[]
diff --git a/docs/zmodel-attribute.md b/docs/zmodel-attribute.md
index ca2395035..d93ad17b8 100644
--- a/docs/zmodel-attribute.md
+++ b/docs/zmodel-attribute.md
@@ -8,7 +8,7 @@ Attributes decorate fields and data models and attach extra behaviors or constra
 
 Field attribute name is prefixed by a single `@`. Its application takes the following form:
 
-```prisma
+```zmodel
 id String @[ATTR_NAME](ARGS)?
 ```
 
@@ -24,7 +24,7 @@ See [attribute arguments](#attribute-arguments).
 
 Field attribute name is prefixed double `@@`. Its application takes the following form:
 
-```prisma
+```zmodel
 model Model {
     @@[ATTR_NAME](ARGS)?
 }
@@ -44,17 +44,17 @@ Attribute can be declared with a list of parameters, and applied with an optiona
 
 Arguments are mapped to parameters by position or by name. For example, for the `@default` attribute declared as:
 
-```prisma
+```zmodel
 attribute @default(_ value: ContextType)
 ```
 
 , the following two ways of applying it are equivalent:
 
-```prisma
+```zmodel
 published Boolean @default(value: false)
 ```
 
-```prisma
+```zmodel
 published Boolean @default(false)
 ```
 
@@ -68,14 +68,14 @@ Attribute parameters are typed. The following types are supported:
 
     E.g., declaration:
 
-    ```prisma
+    ```zmodel
     attribute @password(saltLength: Int?, salt: String?)
 
     ```
 
     application:
 
-    ```prisma
+    ```zmodel
     password String @password(saltLength: 10)
     ```
 
@@ -85,13 +85,13 @@ Attribute parameters are typed. The following types are supported:
 
     E.g., declaration:
 
-    ```prisma
+    ```zmodel
     attribute @id(map: String?)
     ```
 
     application:
 
-    ```prisma
+    ```zmodel
     id String @id(map: "_id")
     ```
 
@@ -101,13 +101,13 @@ Attribute parameters are typed. The following types are supported:
 
     E.g., declaration:
 
-    ```prisma
+    ```zmodel
     attribute @@allow(_ operation: String, _ condition: Boolean)
     ```
 
     application:
 
-    ```prisma
+    ```zmodel
     @@allow("read", true)
     @@allow("update", auth() != null)
     ```
@@ -118,13 +118,13 @@ Attribute parameters are typed. The following types are supported:
 
     E.g., declaration:
 
-    ```prisma
+    ```zmodel
     attribute @default(_ value: ContextType)
     ```
 
     application:
 
-    ```prisma
+    ```zmodel
     f1 String @default("hello")
     f2 Int @default(1)
     ```
@@ -135,7 +135,7 @@ Attribute parameters are typed. The following types are supported:
 
     E.g., declaration:
 
-    ```prisma
+    ```zmodel
     attribute @relation(
         _ name: String?,
         fields: FieldReference[]?,
@@ -147,7 +147,7 @@ Attribute parameters are typed. The following types are supported:
 
     application:
 
-    ```prisma
+    ```zmodel
     model Model {
         ...
         // [ownerId] is a list of FieldReference
@@ -162,7 +162,7 @@ Attribute parameters are typed. The following types are supported:
 
     E.g., declaration:
 
-    ```prisma
+    ```zmodel
     attribute @relation(
         _ name: String?,
         fields: FieldReference[]?,
@@ -175,7 +175,7 @@ Attribute parameters are typed. The following types are supported:
 
     application:
 
-    ```prisma
+    ```zmodel
     model Model {
         // 'Cascade' is a predefined enum value
         owner Owner @relation(..., onDelete: Cascade)
@@ -184,7 +184,7 @@ Attribute parameters are typed. The following types are supported:
 
 An attribute parameter can be typed as any of the above type, a list of the above type, or an optional of the above type.
 
-```prisma
+```zmodel
     model Model {
         ...
         f1 String
@@ -198,7 +198,7 @@ An attribute parameter can be typed as any of the above type, a list of the abov
 
 Attribute functions are used for providing values for attribute arguments, e.g., current `DateTime`, an autoincrement `Int`, etc. They can be used in place of attribute argument, like:
 
-```prisma
+```zmodel
 model Model {
     ...
     serial Int @default(autoincrement())
@@ -214,7 +214,7 @@ You can find a list of predefined attribute functions [here](#predefined-attribu
 
 -   `@id`
 
-    ```prisma
+    ```zmodel
     attribute @id(map: String?)
     ```
 
@@ -228,7 +228,7 @@ You can find a list of predefined attribute functions [here](#predefined-attribu
 
 -   `@default`
 
-    ```prisma
+    ```zmodel
         attribute @default(_ value: ContextType)
     ```
 
@@ -242,7 +242,7 @@ You can find a list of predefined attribute functions [here](#predefined-attribu
 
 -   `@unique`
 
-    ```prisma
+    ```zmodel
         attribute @unique(map: String?)
     ```
 
@@ -256,7 +256,7 @@ You can find a list of predefined attribute functions [here](#predefined-attribu
 
 -   `@relation`
 
-    ```prisma
+    ```zmodel
         attribute @relation(_ name: String?, fields: FieldReference[]?, references: FieldReference[]?, onDelete: ReferentialAction?, onUpdate: ReferentialAction?, map: String?)
     ```
 
@@ -274,7 +274,7 @@ You can find a list of predefined attribute functions [here](#predefined-attribu
 
 -   `@map`
 
-    ```prisma
+    ```zmodel
         attribute @map(_ name: String)
     ```
 
@@ -288,7 +288,7 @@ You can find a list of predefined attribute functions [here](#predefined-attribu
 
 -   `@updatedAt`
 
-    ```prisma
+    ```zmodel
         attribute @updatedAt()
     ```
 
@@ -296,7 +296,7 @@ You can find a list of predefined attribute functions [here](#predefined-attribu
 
 -   `@password`
 
-    ```prisma
+    ```zmodel
         attribute @password(saltLength: Int?, salt: String?)
     ```
 
@@ -313,7 +313,7 @@ You can find a list of predefined attribute functions [here](#predefined-attribu
 
 -   `@omit`
 
-    ```prisma
+    ```zmodel
         attribute @omit()
     ```
 
@@ -323,7 +323,7 @@ You can find a list of predefined attribute functions [here](#predefined-attribu
 
 -   `@@unique`
 
-    ```prisma
+    ```zmodel
         attribute @@unique(_ fields: FieldReference[], name: String?, map: String?)
     ```
 
@@ -339,7 +339,7 @@ You can find a list of predefined attribute functions [here](#predefined-attribu
 
 -   `@@index`
 
-    ```prisma
+    ```zmodel
         attribute @@index(_ fields: FieldReference[], map: String?)
     ```
 
@@ -354,7 +354,7 @@ You can find a list of predefined attribute functions [here](#predefined-attribu
 
 -   `@@map`
 
-    ```prisma
+    ```zmodel
         attribute @@map(_ name: String)
     ```
 
@@ -368,7 +368,7 @@ You can find a list of predefined attribute functions [here](#predefined-attribu
 
 -   `@@allow`
 
-    ```prisma
+    ```zmodel
         attribute @@allow(_ operation: String, _ condition: Boolean)
     ```
 
@@ -383,7 +383,7 @@ You can find a list of predefined attribute functions [here](#predefined-attribu
 
 -   `@@deny`
 
-    ```prisma
+    ```zmodel
         attribute @@deny(_ operation: String, _ condition: Boolean)
     ```
 
@@ -400,7 +400,7 @@ You can find a list of predefined attribute functions [here](#predefined-attribu
 
 -   `uuid`
 
-    ```prisma
+    ```zmodel
         function uuid(): String {}
     ```
 
@@ -408,7 +408,7 @@ You can find a list of predefined attribute functions [here](#predefined-attribu
 
 -   `cuid`
 
-    ```prisma
+    ```zmodel
         function cuid(): String {}
     ```
 
@@ -416,7 +416,7 @@ You can find a list of predefined attribute functions [here](#predefined-attribu
 
 -   `now`
 
-    ```prisma
+    ```zmodel
         function now(): DateTime {}
     ```
 
@@ -424,7 +424,7 @@ You can find a list of predefined attribute functions [here](#predefined-attribu
 
 -   `autoincrement`
 
-    ```prisma
+    ```zmodel
         function autoincrement(): Int {}
     ```
 
@@ -433,7 +433,7 @@ You can find a list of predefined attribute functions [here](#predefined-attribu
 
 -   `dbgenerated`
 
-    ```prisma
+    ```zmodel
         function dbgenerated(expr: String): Any {}
     ```
 
@@ -441,7 +441,7 @@ You can find a list of predefined attribute functions [here](#predefined-attribu
 
 -   `auth`
 
-    ```prisma
+    ```zmodel
         function auth(): User {}
     ```
 
@@ -451,7 +451,7 @@ You can find a list of predefined attribute functions [here](#predefined-attribu
 
 Here're some examples on using field and model attributes:
 
-```prisma
+```zmodel
 model User {
     // unique id field with a default UUID value
     id String @id @default(uuid())
diff --git a/docs/zmodel-data-model.md b/docs/zmodel-data-model.md
index eeb0c4a60..b93d3aa62 100644
--- a/docs/zmodel-data-model.md
+++ b/docs/zmodel-data-model.md
@@ -6,7 +6,7 @@ Data models represent business entities of your application.
 
 A data model declaration takes the following form:
 
-```prisma
+```zmodel
 model [NAME] {
     [FIELD]*
 }
@@ -28,7 +28,7 @@ See [here](zmodel-attribute.md) for more details about attributes.
 
 ## Example
 
-```prisma
+```zmodel
 model User {
     id String @id
 }
diff --git a/docs/zmodel-data-source.md b/docs/zmodel-data-source.md
index 9521c844c..ec4f95935 100644
--- a/docs/zmodel-data-source.md
+++ b/docs/zmodel-data-source.md
@@ -6,7 +6,7 @@ Every model needs to include exactly one `datasource` declaration, providing inf
 
 A data source declaration takes the following form:
 
-```prisma
+```zmodel
 datasource [NAME] {
     provider = [PROVIDER]
     url = [DB_URL]
@@ -33,7 +33,7 @@ datasource [NAME] {
 
 ## Examples
 
-```prisma
+```zmodel
 datasource db {
     provider = "postgresql"
     url = "postgresql://postgres:abc123@localhost:5432/todo?schema=public"
@@ -42,7 +42,7 @@ datasource db {
 
 It's highly recommended that you don't commit sensitive database connection string into source control. Alternatively, you can load it from an environment variable:
 
-```prisma
+```zmodel
 datasource db {
     provider = "postgresql"
     url = env("DATABASE_URL")
diff --git a/docs/zmodel-enum.md b/docs/zmodel-enum.md
index 7b4b21bf8..56a2428c9 100644
--- a/docs/zmodel-enum.md
+++ b/docs/zmodel-enum.md
@@ -22,7 +22,7 @@ enum [ENUM_NAME] {
 
 ## Example
 
-```prisma
+```zmodel
 enum UserRole {
     USER
     ADMIN
diff --git a/docs/zmodel-field-constraint.md b/docs/zmodel-field-constraint.md
index 20d0814ac..bcc416a73 100644
--- a/docs/zmodel-field-constraint.md
+++ b/docs/zmodel-field-constraint.md
@@ -60,7 +60,7 @@ The following attributes can be used to attach field constraints:
 
 ## Example
 
-```prisma
+```zmodel
 model User {
     id String @id
     handle String @regex("^[0-9a-zA-Z]{4,16}$")
diff --git a/docs/zmodel-field.md b/docs/zmodel-field.md
index e0f128288..a989228b5 100644
--- a/docs/zmodel-field.md
+++ b/docs/zmodel-field.md
@@ -6,7 +6,7 @@ Fields are typed members of data models.
 
 A field declaration takes the following form:
 
-```prisma
+```zmodel
 model Model {
     [FIELD_NAME] [FIELD_TYPE] (FIELD_ATTRIBUTES)?
 }
@@ -39,7 +39,7 @@ model Model {
 
 ## Example
 
-```prisma
+```zmodel
 model Post {
     // "id" field is a mandatory unique identifier of this model
     id String @id @default(uuid())
diff --git a/docs/zmodel-referential-action.md b/docs/zmodel-referential-action.md
index 303df97b1..30cec3ada 100644
--- a/docs/zmodel-referential-action.md
+++ b/docs/zmodel-referential-action.md
@@ -4,7 +4,7 @@
 
 When defining a relation, you can use referential action to control what happens when one side of a relation is updated or deleted, by setting the `onDelete` and `onUpdate` parameters in the `@relation` attribute.
 
-```prisma
+```zmodel
     attribute @relation(
         _ name: String?,
         fields: FieldReference[]?,
@@ -16,7 +16,7 @@ When defining a relation, you can use referential action to control what happens
 
 The `ReferentialAction` enum is defined as:
 
-```prisma
+```zmodel
 enum ReferentialAction {
     Cascade
     Restrict
@@ -54,7 +54,7 @@ enum ReferentialAction {
 
 ## Example
 
-```prisma
+```zmodel
 model User {
     id String @id
     profile Profile?
diff --git a/docs/zmodel-relation.md b/docs/zmodel-relation.md
index 2eb21af68..02ca4e274 100644
--- a/docs/zmodel-relation.md
+++ b/docs/zmodel-relation.md
@@ -14,7 +14,7 @@ The _owner_ side of the relation declares an optional field typed as the data mo
 
 On the _owned_ side, a reference field is declared with `@relation` attribute, together with an **foreign key** field storing the id of the owner entity.
 
-```prisma
+```zmodel
 model User {
     id String @id
     profile Profile?
@@ -33,7 +33,7 @@ The _owner_ side of the relation declares a list field typed as the data model o
 
 On the _owned_ side, a reference field is declared with `@relation` attribute, together with an **foreign key** field storing the id of the owner entity.
 
-```prisma
+```zmodel
 model User {
     id String @id
     posts Post[]
@@ -52,7 +52,7 @@ A _join model_ is declared to connect the two sides of the relation, using two o
 
 Each side of the relation then establishes a one-to-many relation with the _join model_.
 
-```prisma
+```zmodel
 model Space {
     id String @id
     // one-to-many with the "join-model"
diff --git a/package.json b/package.json
index 2cf8af8e9..a794e9ef4 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
 {
     "name": "zenstack-monorepo",
-    "version": "0.3.17",
+    "version": "0.3.18",
     "description": "",
     "scripts": {
         "build": "pnpm -r build",
diff --git a/packages/runtime/package.json b/packages/runtime/package.json
index b3509f408..9c31ba36a 100644
--- a/packages/runtime/package.json
+++ b/packages/runtime/package.json
@@ -1,7 +1,7 @@
 {
     "name": "@zenstackhq/runtime",
     "displayName": "ZenStack Runtime Library",
-    "version": "0.3.17",
+    "version": "0.3.18",
     "description": "Runtime of ZenStack for both client-side and server-side environments.",
     "repository": {
         "type": "git",
diff --git a/packages/schema/package.json b/packages/schema/package.json
index b0db20b0b..a7e4101a3 100644
--- a/packages/schema/package.json
+++ b/packages/schema/package.json
@@ -3,7 +3,7 @@
     "publisher": "zenstack",
     "displayName": "ZenStack Language Tools",
     "description": "A toolkit for modeling data and access policies in full-stack development with Next.js and Typescript",
-    "version": "0.3.17",
+    "version": "0.3.18",
     "author": {
         "name": "ZenStack Team"
     },
diff --git a/packages/schema/src/res/prism-zmodel.js b/packages/schema/src/res/prism-zmodel.js
new file mode 100644
index 000000000..dd7c30d5a
--- /dev/null
+++ b/packages/schema/src/res/prism-zmodel.js
@@ -0,0 +1,22 @@
+// based on: https://github.com/prisma/docs/blob/c72eb087fcf57f3c00d153f86c549ef28b3d0f44/src/components/customMdx/prism/prism-prisma.js
+
+(function (Prism) {
+    Prism.languages.zmodel = Prism.languages.extend('clike', {
+        keyword:
+            /\b(?:datasource|enum|generator|model|attribute|function|null|this)\b/,
+        'type-class-name': /(\b()\s+)[\w.\\]+/,
+    });
+
+    Prism.languages.javascript['class-name'][0].pattern =
+        /(\b(?:model|datasource|enum|generator)\s+)[\w.\\]+/;
+
+    Prism.languages.insertBefore('zmodel', 'function', {
+        annotation: {
+            pattern: /(^|[^.])@+\w+/,
+            lookbehind: true,
+            alias: 'punctuation',
+        },
+    });
+
+    Prism.languages.json5 = Prism.languages.js;
+})(Prism);
diff --git a/samples/todo/package.json b/samples/todo/package.json
index 8d28d8f50..ac10904ae 100644
--- a/samples/todo/package.json
+++ b/samples/todo/package.json
@@ -1,6 +1,6 @@
 {
     "name": "todo",
-    "version": "0.3.17",
+    "version": "0.3.18",
     "private": true,
     "scripts": {
         "dev": "next dev",