Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/LMendoza70/SSA/llms.txt

Use this file to discover all available pages before exploring further.

The CMS module is the core domain of the SSA Health Platform. Every other module — the chatbot, social media publisher, public portal, and multimedia library — exists in service of this central capability: producing and distributing reliable, official health information. Built around a unified Content abstraction, the CMS gives administrators of the Jurisdicción Sanitaria de Huejutla de Reyes a single interface to author, review, publish, and archive all institutional content types, from breaking health news to disease prevention guides and official program documentation.

​
What the CMS Manages

News

Health news and press releases from the Jurisdicción and the Secretaría de Salud.

Diseases

Disease guides covering symptoms, transmission routes, and prevention measures.

Campaigns

Preventive health campaigns with target populations and defined date ranges.

Programs

Institutional health programs managed by the Jurisdicción, each with a responsible coordinator.

Events

Public health events such as vaccination days, workshops, and community outreach.

Announcements

Comunicados oficiales directed at the population or health personnel.

Notices

Avisos institucionales for short-term alerts and operational updates.

Infographics

Visual health education materials that simplify complex medical information.

Documents

Official documents and protocols such as manuals, reports, and forms in PDF format.

FAQs

Frequently asked questions organized by category to help the public find quick answers.

Institutional Info

About pages, mission, vision, and organizational information for the Jurisdicción.

​
Content Lifecycle

All content in the CMS follows a linear lifecycle from authoring to archival. Administrators move content through each stage explicitly, ensuring nothing reaches the public portal without intentional review and publication.
1

Create

An administrator creates content with status DRAFT using the Tiptap rich-text editor. At this stage the content is private and not accessible outside the admin interface.
2

Review

Draft content is reviewed internally for factual accuracy, language clarity, and alignment with institutional communication standards before advancing.
3

Publish

The administrator sets the status to PUBLISHED and optionally specifies a publishedAt date to schedule future availability. Once published, the content is visible on the public web portal.
4

Distribute

Published content becomes available on the public-facing portal, is indexed by the chatbot’s RAG pipeline, and can be queued for automatic publication to social media channels via the Social Media module.
5

Archive

Content that is no longer current or accurate is set to ARCHIVED. Archived content is removed from all public views but is retained in the database for institutional record-keeping and audit purposes.

​
Content Status Flow

Every content item transitions through a defined set of states. Reverting a published item back to draft is allowed to support corrections before re-publishing. 
DRAFT → PUBLISHED → ARCHIVED
  ↑__________|  (can revert to draft)
An item in ARCHIVED status cannot be directly re-published. It must first be reverted to DRAFT and then go through the review and publish steps again.

​
Rich Text Editor (Tiptap)

The CMS uses Tiptap as its rich-text editor, providing a modern, extensible authoring experience that produces structured JSON output stored in the body field. This JSON representation is portable, renderable on the frontend, and indexable by the chatbot. The following formatting features are supported in the editor:
  • Bold, italic, underline, strikethrough
  • Headings H1 through H6
  • Ordered and unordered lists
  • Tables (with resizable columns)
  • Image embedding from the Multimedia Module
  • Hyperlinks (internal and external)
  • YouTube and video embeds
  • Code blocks with syntax highlighting
Because body is stored as Tiptap JSON rather than raw HTML, the frontend renderer has full control over how each node is displayed, ensuring consistent styling and accessibility across the platform.

​
SEO Fields

Every content item carries a set of SEO fields so that public pages are optimally indexed by search engines and properly previewed on social media.
FieldDescription
seoTitleCustom meta title. Falls back to the content title if left blank.
seoDescriptionMeta description shown in search engine result snippets.
slugURL-friendly unique identifier, auto-generated from the title at creation time and editable by the administrator.
tagsArray of keyword tags used for filtering, related-content suggestions, and chatbot indexing.

​
API Summary

The CMS exposes a standard set of REST endpoints under /content. All mutation operations require an authenticated session with appropriate role permissions. 
GET    /content?type=news&page=1&limit=20
POST   /content
GET    /content/:id
PATCH  /content/:id
DELETE /content/:id
POST   /content/:id/publish
POST   /content/:id/archive
All CMS endpoints require authentication. Public-facing content is served through a separate read-only public API that exposes only PUBLISHED items and never reveals draft or archived records.

Build docs developers (and LLMs) love

Get started for freeTalk to us