Skip to content
Subscribe

JotKit Themes and plugins

Themes and plugins

Addons change or extend JotKite without touching its core files, so updates never overwrite your work.

  • Themes control the whole public page. One is active at a time.
  • Plugins add behaviour through hooks. Any number can be active.

Using addons

Admins turn addons on in Settings → Addons, which also shows each addon's settings. For a theme to take effect, set Settings → General → Layout to JotKite theme (or Automatic on non-GeoRank sites).

To install an addon, upload its folder into addons/ by FTP, File Manager or Git. JotKite deliberately has no "upload a zip" button, because that would let anyone with an admin password run code on your server.

JotKite M1

The official theme, JotKite M1 ("Mobile One"), uses one layout for every device:

  • a 720px column with a 640px reading width,
  • a thumb-friendly header of three 100px blocks: logo, action and menu.

You choose the header, container, footer and outside colours, including the JotKite gradient.

Build your own

An addon is a folder with an addon.json manifest, plus theme.php (themes) or addon.php (plugins). Settings forms are generated from the manifest.

Plugins hook in with actions and filters, for example:

  • pb_head and pb_body_end to add tags and scripts,
  • pb_post_content to change a post's body,
  • pb_post_status_changed to react when a post is published.

The pb_ prefix is JotKite's original codename, kept so addons keep working.

Full developer guide: docs/ADDONS.md on GitHub. It covers the manifest fields, the theme $page data, every hook and a security checklist.

Share your addon: publish it on GitHub and open an issue to have it listed on jotkite.com. Addons you distribute must be AGPL-compatible, unless you hold a JotKite commercial license.