Appearance
lt-strapi
needs verificationPurpose
lt-strapi is the content management system (CMS) for published research and editorial content. It owns content models and editorial publication state. lt-core retains authority over LT Work business rules.
What it does
| Group | Content types |
|---|---|
| Research | Publication Plus, Publication, Profile Video, Basic Video, researcher, institution, work, topic, field, Sustainable Development Goal, playlist and LT Work tag |
| Editorial | Blog, news item, news tag, organization, book, book genre, book recommendation and basic page |
| Site-wide single entries | Homepage, menu, footer and config |
These are implemented content schemas. Most support drafts and publishing; topic and field do not. Homepage and basic-page blocks compose pages. Editors curate content, relations, covers and subtitles using the admin interface, subject to their assigned permissions.
The comma-separated values (CSV) plugin supports selected import/export workflows. Meilisearch indexing is configured for Publication Plus, researchers and institutions. This is not evidence that every content type is searchable.
For maintainers: technology
Strapi 5.31.2, PostgreSQL, an upload provider compatible with the Simple Storage Service (S3) interface and the Meilisearch plugin.
How it connects
lt-web reads CMS content when Hugo builds the website. The machine identity named hugo-build can read content and content-type metadata; it cannot edit content.
The core-to-CMS publishing handoff remains an integration target requiring verification. Legacy identifiers explain older names: several schemas retain drupalNid, and Profile Video also retains laravelId. These are migration links, not new domain entities.
Who can do what
Yes means available to that persona. No means no dedicated CMS access through that persona. Partial means permissions must be confirmed in the deployed admin interface. A core Administrator is not automatically a Strapi Super Admin.
| Action | Anonymous | Researcher | Coordinator | Administrator | Editor |
|---|---|---|---|---|---|
| Read the public CMS interface directly | Partial | Partial | Partial | Partial | Partial |
| Curate content and media | No | No | No | Partial | Partial |
| Publish and unpublish eligible types | No | No | No | Partial | Partial |
| Import/export CSV or reindex search | No | No | No | Partial | Partial |
| Manage CMS accounts, API access and settings | No | No | No | Partial | No |
The expected Editor job is content curation. Strapi Super Admins additionally administer settings and permissions. The exact actions available to an Editor depend on the permissions assigned to that account. Ask the team lead for a staging account and confirmation of its role.
Environments and links
Local adminhttp://cms.lt.localhost/admin
Staging adminhttps://cms.stg.lt.org/adminInfrastructure target; older automation names cms-stg.lt.org.
Production adminhttps://cms.lt.org/admin
Where to read more
The public website, the website guide and Publication and Publication Plus.
Known gaps
Confirm the staging hostname, deployed role permissions and the core publishing handoff. Both Publication and Publication Plus have editable digital object identifier (DOI) fields; those fields do not prove automatic registration. See open questions.
For maintainers: source references
These references require repository access. Everything needed to understand this page is explained above.