Plugin Store

For developers

Signing up and publishing plugins

Create a developer account on the Plugin Store, upload a .zip package, read the package check, submit for review, release new versions and upload from CI with an API token

5 min readLast updated

View as Markdown

On this page

Anyone can publish plugins on the Anasaki Plugin Store for free — once approved, every Anasaki Studio site can find and install them in one click. To build a package see JavaScript plugins and Package and WebAssembly plugins.

1. Create a developer account#

  1. Open storecms.anasaki.live → Sign in → Become a developer
  2. Enter a display name (the developer name), email and password (at least 8 characters)
  3. Accept the terms (the plugin is yours, contains no harmful code, and the team may suspend plugins that break the rules), then press Create account

2. Upload#

  1. Go to the Dashboard (developer dashboard) → the Upload tab
  2. Drop the .zip file — the package checker runs right away with the same rules Anasaki Studio uses at install:
    • A safe zip structure (no ../, symlinks or forbidden files) within the size limit
    • A valid manifest.json that declares a permission for every feature
    • The code part: files, code scopes, domains, paths and requires (or the service part and WebAssembly module)
    • A summary of things to watch, such as JavaScript on every page, sending data out or access to member data
  3. If it passes, press Publish (or Submit for review for plugins that need the team)
Plugin kindAfter upload
HTML/CSS only (templates without scripts)In the store right away
Runs code — JavaScript, WebAssembly / service, or templates with scriptsPending review until the team has read the code, permissions, domains and migrations and approved it

Follow the status on the My plugins tab: published · pending review · rejected (with the team's note). Pending or rejected versions can be deleted.

Important rules#

  • The id is yours — the account that first uploads an id owns it, and nobody else can release versions of it. If it says the id belongs to someone else, change id in manifest.json
  • A new version must always be higher (semver, e.g. 1.0.0 → 1.1.0), and every version that runs code is reviewed again
  • The ids of the official plugins (seo, forms, analytics, redirects, cookie-consent, maintenance, custom-code) and backup are reserved
  • A suspended plugin cannot get new versions — contact the store administrators

The plugin's page in the store#

Comes fromShown as
name, description, icon, category, tags in the manifestThe card and search
README.md at the package rootThe details tab
Images in the screenshots/ folder (png, jpg, gif, webp, svg)The screenshots tab
minCore, requires, optionalRequires"Requires Anasaki Studio X or later", "Requires plugins", "Works with"
permissions, code, serviceThe permissions the plugin uses and its server part

Write the README in both Thai and English: what the plugin does, where its settings are and why it asks for each permission — it speeds up review and gives site owners the confidence to install.

Uploading from a script or CI#

  1. Under Dashboard → Account, create an API token (for CI) — shown once, with the same rights as your account
  2. Upload with the X-Publish-Token header:
curl -X POST https://storecms.anasaki.live/api/v1/publish \
     -H "X-Publish-Token: <token>" \
     -F "[email protected]"

The answer is JSON {id, name, version, status}, where status is published or pending (awaiting review).

Next: Review, official badges and recommended plugins