JustDocs Documentation

What JustDocs is, how workspaces, sites and readers fit together, and what a site owner looks after.

PHP, database, web server, scheduler and HTTPS. No queue worker, no Node, no Redis needed.

Upload the package, point the domain at it, prepare the database and finish the web installer.

From a fresh install to a tested platform, in the order the pieces depend on each other.

Branding, email, the scheduler, storage, security, sign-in, payments and plans.

Ask AI, writing and translation on the platform's key or a workspace's own; built-in analytics without cookies.

Let customers serve their docs on their own domain, with HTTPS from your server, Caddy or Cloudflare.

Keep docs in a GitHub or GitLab repository: pushes become drafts, publishes become commits.

How customers run their workspaces: members and roles, sites, who can read what, versions and languages.

Blocks, imports and exports, releases and history, Customize, and what readers get in the published docs.

The admin panel: users, workspaces, sites, AI accounts and requests, plans and payments, backups.

Back up, update safely, and sort out the common installation and runtime problems.