Files

The Documents manager is Chinaski’s download center: any file a site offers to visitors (PDFs, reports, ZIP archives, catalogs), uploaded once, managed with its own metadata, and delivered by the CMS with tracking. Found under Documents in the admin area (admin-only).

Uploading files

From the Documents → New screen:

• Any file type up to 50 MB: PDF, ZIP, DOCX, images, archives; multiple files can be uploaded in one go.
• Each document carries a title, slug, and language, plus a description and folder; the slug becomes its public download URL (/documents/<slug>).
• Publishing: documents default to unpublished; publishing (or scheduling a publish window) makes the download live. Unpublished documents return 404 to visitors.
• Metadata captured per document: page count, creation date, dimensions and color mode (populated when extractable), author fields, tags (with an optional color-coded document-tag set), and descriptions, internal notes versus public descriptions.

Folders and organization

Documents belong to folders (a listing facet you filter by), and the listing view supports filters by language and by status (published/unpublished) as well as free search across titles, slugs, and descriptions. Sortable by name, slug, size, creation date, or download count. 50 items per page.

Replacing and duplicating

• Replace file: upload a new version in place of the current one: the slug and public URL stay exactly as they were, so links embedded in built pages continue to work after an update. Replacement files follow the same 50 MB cap.
• Duplicate: makes a fresh copy of the title/file/metadata under a new document, for cases where a similar file needs its own URL and lifecycle. Duplication is audited.
• Every save of a document (including file replacement) snapshots a revision; the versions panel shows each save.

Serving and tracking

• When published, a document is downloadable at /documents/<slug>; each download increments the document’s download counter (visible in the listing sort).
• Docs serve through the CMS: never on the static wire. Your reverse proxy or static host forwards /documents/* to the CMS (the shipped nginx/Caddy examples include this route; without it, every document URL 404s for visitors).
• The static site’s link comes from the document block type: put a document block in a page body ({{document:slug​}}) and the builder embeds the reference; replace the file later, and the built link keeps working because the slug never changes.

Housekeeping

• Delete moves a document to Trash; restore or permanently destroy from there.
• Bulk operations (delete/publish-state driven) run on selected documents.
• An export (including a CSV variant) and a JSON import exist for the documents list.
• The block editor has a document picker for dragging a doc into a page body.