AVKUL ERPDocs
MODULE GUIDE · 11 OCT 2026

School website CMS

Manage school themes, content pages and published website information from the ERP.

Try guided demo →Download guide ↓
School website CMS — illustrated workflow banner

What you can do

01

Themes

02

Theme activation

03

Page content

04

Draft and publish

05

Public school pages

06

Branding and contact

Access & setup

Intended access: Assigned account with the required permissions.

  • An assigned school account with the required permissions.
  • The academic, student or staff setup used by this workflow.
Required permission keys
website:viewwebsite:createwebsite:updatewebsite:delete

Use the public sample demo to learn this flow. Your assigned ERP account determines access to actual school records.

How the workflow works

  1. 01

    Review the school website theme and branding

    An assigned school account with the required permissions.

  2. 02

    Create or edit the intended content page

    Theme activation is part of the documented workflow.

  3. 03

    Preview and check the content and contact information

    Page content is part of the documented workflow.

  4. 04

    Publish the page and review the public school URL

    Review the result in the connected record or workspace before moving on.

Request fields to understand

Source-declared fields used by related operations; each operation has its own validation and scope.

FieldDeclared typeInput
namestringRequired by declaration
configJsonRecord<string, unknown>Optional
isActivebooleanOptional
slugstringRequired by declaration
titlestringRequired by declaration
typestringOptional
themeIdstringOptional
contentJsonRecord<string, unknown>Optional
seoJsonRecord<string, unknown>Optional
sortOrdernumberOptional
statusstringRequired by declaration

Rules & current limits

  • School website content is separate from the platform marketing Landing Page CMS. Publish controls use school ownership and permissions.

Source inventory checked on 11 October 2026. Guide availability confirms documentation publication, not certification of every external service or device flow.

Try school website cms

Open a guided sample workspace, try the available actions, then reset whenever you like. No login required.

Launch guided demo →

API & permissions reference

This is the module’s source-declared endpoint catalogue. Reading this reference does not execute any request.

12 source-declared operations
GET/api/v1/website/themes

List Themes

website:view
POST/api/v1/website/themes

Create Theme

website:create

Declared request fields: name (required), configJson (optional), isActive (optional).

PATCH/api/v1/website/themes/:id

Update Theme

website:update
POST/api/v1/website/themes/:id/activate

Activate Theme

website:update
DELETE/api/v1/website/themes/:id

Remove Theme

website:delete
GET/api/v1/website/pages

List Pages

website:view
POST/api/v1/website/pages

Create Page

website:create

Declared request fields: slug (required), title (required), type (optional), themeId (optional), contentJson (optional), seoJson (optional), sortOrder (optional).

PATCH/api/v1/website/pages/:id

Update Page

website:update
POST/api/v1/website/pages/:id/publish

Publish Page

website:update

Declared request fields: status (required).

DELETE/api/v1/website/pages/:id

Remove Page

website:delete
GET/api/v1/website/public/:schoolCode

Get Public Site

Public/capability access as implemented
GET/api/v1/website/public/:schoolCode/:slug

Get Public Page

Public/capability access as implemented

Open the actual application

ERP links use your assigned account. Record-specific pages start from the list so you can choose a real record.

Keep exploring