HELPORA LTD · LONDON hello@helpora.uk

Line two of three

Portals that stay current after the book is fixed.

A printed index can only point at pages. A portal can filter, cross-reference and update. We design, build and operate the portal that carries the same record set the book was written from.

TAXONOMY All records Region Category — primary — secondary — tertiary Period Status Source portal · 12,480 records query Search region: UK period: 1900– + add facet 348 MATCHES updated subscribers only facets are the book's index, made queryable

What we build

Search and facets

Full-text search with typo tolerance, filters drawn from the taxonomy, saved queries and result exports.

Editorial workflow

Draft, review and publish states, revision history, scheduled release, and a per-record audit trail of who changed what.

Subscriber accounts

Paid and institutional access, seat management, IP-range authentication for libraries, and book-purchase redemption codes.

Directories and listings

Submission forms, moderation queues, claim-and-verify flows for listed organisations, and duplicate detection.

Hosting and operation

UK and EU hosting, backups with tested restores, uptime monitoring, security patching, and moderation cover if you need it.

Migration

Moving off a platform you have outgrown: content mapping, URL preservation, redirects, and a parallel run before cutover.

How a build runs

Twelve to sixteen weeks for a first release, then a monthly operating agreement or a documented handover to your team.

WK 1–3 Model the records and agree the taxonomy. Nothing is designed until this is settled.
WK 4–7 Interface design against real records, not placeholder text.
WK 8–13 Build, content migration, accessibility and load testing.
WK 14–16 Editor training, parallel run, cutover, and thirty days of close support.

Send us the content you are sitting on.

Scope a portal