Workflow: Creating content - NIAID-Data-Ecosystem/nde-strapi GitHub Wiki

This section describes the process of creating, updating, and publishing content using the Strapi CMS for the NIAID Data Ecosystem.

Requesting an account

To add/update the content, you will need to request an account from the NIAID Data Ecosystem team. Once approved you can access your admin account.

Create/Update Content

To create content, navigate to the content manager in the Strapi Dashboard.

Workflow Steps

  1. Create a new content item or select an existing one.
  2. Save as draft to preserve progress without publishing (see Publication States).
  3. Publish when the content is ready to appear live on the portal.

Publication states

Strapi supports two publication states for all content entries:

  1. Draft: Content is saved but not visible on production. Visible only in dev/staging.

  2. Published: Content is visible on the production portal.

Behavior by Environment

  • Development & Staging: These environments fetch both draft and published content from the Strapi API. This allows content editors to preview and test how updates will appear before going live.

  • Production: Only published content is displayed to end users. When the content is ready to be migrated to production, simply update the publication state from draft to publish.

Note that once something is published, you can return it to draft mode, if desired. This would be useful in the case that a user wants to retract an item from being displayed in production.

Deploying content to the portal

For most content types managed in Strapi, updates made through the CMS are reflected automatically in the portal without requiring code changes or manual deployment in the NIAID Data Ecosystem Portal repository.

🛠️ If a rebuild is necessary (e.g., after adding a new dynamic route), consult the Deployment Process for detailed steps.

📖 Relevant Strapi documentation