Install JotKite

Requirements

• PHP 7.4 or newer (8.x recommended) with pdo_sqlite, which is on by default at almost every host.
• Optional: gd for image resizing, mbstring, and intl or iconv for nicer URL slugs.
• Apache with mod_rewrite for clean URLs like /blog/my-post/. Without it, JotKite uses ?p=my-post URLs instead. On Nginx, see Nginx.

Option 1: Next to your existing site (/blog/)

1. Download JotKite from GitHub and put the files in a folder named blog in your web root:

   public_html/
   ├── index.html        ← your site
   └── blog/             ← JotKite

2. Make sure blog/data/ and blog/uploads/ are writable by PHP. They usually already are.
3. Open https://your-site.com/blog/admin/ and create the first admin account.
4. In Settings → General, click Add blog sitemap to robots.txt. Then add a "Blog" link to your site's menu.

Option 2: As a whole site on its own domain

Put the files directly in public_html/. The blog becomes your homepage, posts live at /post-slug/, and the admin is at /admin/. JotKite serves robots.txt and sitemap.xml for you. Create About, Contact and similar pages under Pages, and add them to the menu in Settings → Navigation.

Important on a public domain: set setup_key in config.php before you upload, so nobody else can claim the first-run setup screen. See Configuration.

Option 3: On a GeoRank site

In GeoRank (v1.90 or newer), go to Control Center → Upgrade → Blog → Install Blog.

• Every file is checksum-verified.
• Updates never touch your posts or images.
• The blog uses your site's own header, footer, menu and theme.
• GeoRank users are signed in automatically.

How uploading works

JotKite is plain files, so any upload method works: FTP, a zip in your hosting File Manager, or your hosting panel's Git deploy. The database is created automatically on the first visit.

JotKite also recreates its protective .htaccess files if they go missing during upload. Some uploaders and FTP clients silently skip files that start with a dot.

---

Next> JotKite Editor