Documentation

Four readers, four doors

Most documentation sites are organised the way the product was built. This one is organised by who is asking — because an evaluator, an administrator, a developer and a compliance officer want four different first pages.

Evaluating

Start here

What GimCore is, what it is not, and how the 30-day evaluation runs on your own infrastructure. The claim register, in full, with the status of every figure.

Evaluation guide → Administering

Running an app

Screens, fields and their formats, relationships, workflows and post actions. How to change what a module does without changing code.

Administrator guides → Building

Extending the core

The metadata model, the field type reference, the post-action catalogue, and what a Tier 2 source licence actually hands you.

Developer guides → Assuring

Architecture & controls

Deployment topology, the three-tier audit trail, access model, and the control mapping your auditor will ask to see.

Architecture & security →

App guides

Every app documents itself

A guide is generated from the app's own definitions, so it describes the screens, fields, relationships and automations that actually exist — not the ones that existed when someone last wrote a manual.

  • Per screen — its purpose, its fields, and a read-only view of the real form
  • Relationships — one diagram of how the screens link, drawn from the definitions
  • Workflow — the states and transitions, as a diagram rather than a paragraph
  • Automation — what runs on save, in the words of the configuration

This is a direct consequence of the architecture: because behaviour is metadata, the documentation can be read out of the same place the application is.

A controlled document with classification and review status, a navigable document tree, and reviewer comments anchored in the text
Documentation is itself a module — versioned, reviewable, and commentable in place. The same Document Control that governs your procedures governs these.
A course catalogue with two courses, each showing its module count, duration and points
Courses, lessons, quizzes and completion tracking — the E-Learning module, used on GimCore itself.

Training

Onboarding your team runs on the platform

Administrator and end-user training is delivered as courses inside GimCore, so completion is a record rather than an assertion — which is the same thing your compliance officer wants for every other mandatory training.

Ask about enablement →

Reference

The things people look up twice a day

Release

What changed, and when

Release notes carry the same status labels the rest of this site uses, so a line that says in build in the notes says in build on the marketing pages too.

Not finding it

Ask a person

Documentation answers what we anticipated. An evaluation answers what you actually asked.

Talk to us