LIS CMS White Paper

Content management architecture, secretary workflows, and LIS publishing controls

The administrative backbone for Sangguniang Bayan content, sessions, and document approval

This white paper describes the Legislative Information System CMS as the admin back-office for Municipality of Jones. It manages council content, SB Secretary workflows, session meetings, agendas, and minutes—publishing data to the public LIS portal via REST APIs.

Documentation for LGU stakeholders, implementers, and technical reviewers

Platform role
Admin back-office
Portals
Staff + secretary
Publishing
REST API to LIS
Sessions
Agenda, minutes, live

1. Platform overview

Role in municipal legislative administration

LIS CMS operates as the authoritative admin platform for Municipality of Jones, connecting staff content management, SB Secretary document review, session meeting administration, and public API feeds consumed by the Legislative Information System.

Core platform functions

  • CRUD for members, standing committees, district assignments, organization chart, and barangay officials.
  • Photo journals, galleries, and calendar events for public display on LIS.
  • SB Secretary module: document review, session meetings, agenda, minutes PDF, remarks, live session.
  • Public API routes under /api/* for LIS proxy and direct consumption.
  • User management with role-based access to modules.

2. System participants

Distinct roles in content and session administration

CMS administrators

Manage council master data, users, photo journals, organization structure, and general content modules.

SB Secretary

Review forwarded member documents, assign sessions, build agendas, generate minutes, and configure live sessions.

LIS (API consumer)

Public portal fetches CMS content via REST APIs and storage proxy for consistent delivery to citizens.

DMS integration

Published legislative documents are stored in DMS; LIS report pages consume DMS separately from CMS content APIs.

3. Content management lifecycle

From staff encoding to public API publication

Staff encoding Validation Storage API publish LIS display
1

Content creation

Authorized staff create or update members, committees, events, and media through admin modules.

2

Review and approval

Content is validated before being exposed via public API endpoints.

3

API availability

Routes such as /api/members, /api/photo-journals, and /api/calendar-event serve LIS.

4

Public visibility

LIS renders council information for citizens using CMS-sourced data.

4. Secretary workflow

Document review and session administration

Secretary routes under /secretary/* implement the operational core for council meetings:

  • Documents — review forwarded member documents (forwarded, approved states).
  • Session meetings — CRUD for session meetings with agenda and packet generation.
  • Agenda — reorder agenda items, attach documents to sessions.
  • Minutes — template, PDF generation, and review workflows.
  • Remarks — session document remarks for members viewing in LIS.
  • Live session — settings for live stream integration on the public portal.

5. Session and document framework

Data models linking members, documents, and sessions

MemberDocument

SB member submissions with status: draft, forwarded, approved.

SessionMeeting

Scheduled council sessions with metadata for agendas and minutes.

SessionDocument

Links documents to sessions with agenda ordering.

Session remarks

Annotations visible to members on session documents in LIS.

6. LIS integration

CORS, APIs, and cross-system connectivity

  • Public API routes expose members, committees, assignments, organization, photo journals, calendar, barangay officials, and galleries.
  • CORS headers configured for LIS origin (CORS_ALLOWED_ORIGIN).
  • LIS uses server-side proxy and cms_mysql connection for session data where applicable.

7. System architecture

Application and data structure

Presentation layer

Blade admin UI with Bootstrap, DataTables, and Vite-compiled assets for staff workflows.

Application layer

Laravel 11 controllers, DomPDF for minutes, secretary and content controllers, CORS middleware.

Data layer

MySQL tables for members, sessions, documents, users, roles, and media storage.

Members
Committees
Secretary
Sessions
Minutes PDF
Public API

8. Security and access controls

Governance and access integrity

  • Laravel UI authentication with registration disabled.
  • Auth middleware on all admin routes; secretary routes role-gated.
  • CSRF protection on web forms.
  • Public API routes intentionally unauthenticated for LIS consumption; scope limited to read-only feeds.

9. Risk management framework

Operational risk

Document approval queues and session status tracking reduce processing errors.

Access risk

Staff accounts with module-level responsibilities; secretary functions restricted to authorized roles.

Integration risk

LIS dependency on CMS APIs documented; CORS and URL configuration validated per deployment.

10. Operational resilience

CMS availability directly affects LIS public content and session visibility. Recovery procedures include database backups, application logs, and coordinated restoration with LIS proxy configuration.

11. Platform role summary

LIS CMS, in summary

  • Central admin platform for Sangguniang Bayan content and secretary operations.
  • Publishes council data to LIS via REST APIs.
  • Manages full session lifecycle from document intake to minutes.
  • White-label ready for municipal deployments (Jones, Buguey, and others).

Ready to evaluate LIS CMS for your LGU?

Prepare council structure, secretary workflows, and LIS integration requirements for a rollout design workshop.