🏙️ EcoPulse: The Smart City Demo (LDM Sample Assets)

Welcome to EcoPulse, a high-fidelity Liferay "Smart City" portal. This workspace is the source-of-truth for sample assets bundled with the Liferay Docker Manager (LDM).

🎯 The Purpose: Confidence-Driven Selling

For a Sales Engineer, "Demo Risk" is the enemy. EcoPulse is designed to prove that complex, data-driven Liferay environments can be:

1. Reset in minutes without manual configuration.
2. Version-controlled via a single source folder.
3. Identical across local laptops and cloud staging.

This repository builds the Client Extensions, Objects, and Fragments that LDM orchestrates into a "Perfect 10" demo.

---

🏗️ The Tech Stack (16 LDM Orchestrated Extensions)

🎨 Branding & UI

• ecopulse-theme: Shared foundational CSS and component logic (the "Engine").
• ecopulse-brand: Entity-specific themeCSS for the EcoPulse data/grid visual identity.
• veridian-brand: Entity-specific themeCSS for the City of Veridian civic identity.
• ecopulse-favicon: Professional SVG branding for the EcoPulse browser tab.
• veridian-favicon: Professional SVG branding for the City of Veridian browser tab.
• ecopulse-spritemap: Custom SVG iconography (leaf, bolt, map-marker).
• ecopulse-custom-element-vanilla: A lightweight, frontend-only custom element.

📊 Intelligence & Logic

• ecopulse-grid-map: A React-based Energy Grid Monitor with live status pulses and Headless API integration.
• ecopulse-impact-calculator: A React widget calculating real-time CO2 savings from GreenInitiative data.
• ecopulse-object-action: A Node.js backend that validates and enriches sustainability data.
• ecopulse-workflow-action: Handles automated city approval steps via "Machine Approver" logic.
• ecopulse-microservice: A Node.js service providing "Advanced Metrics" (Efficiency, Carbon Intensity) to the grid.
• ecopulse-headless-auth: Demonstrates secure Headless API communication via OAuth2.

🚀 Data & Site Provisioning

• ecopulse-batch: Deploys localized GreenInitiative and EnergySector schemas with multi-language seed data.
• ecopulse-site-initializer: Orchestrates the "EcoPulse Smart City" initiative site.
• veridian-site-initializer: Orchestrates the "City of Veridian" municipal portal (applied to the default L_GUEST site).

---

📐 Implementation Standards

To ensure demo reliability, all assets follow strict Liferay 7.4 conventions:

• Site Initializer: Uses versioned externalReferenceCode paths and standardized group/ folder structures for fragments and documents.
• Brand Separation: Entities (Veridian, EcoPulse) share the ecopulse-theme core but use dedicated themeCSS extensions to control their unique branding via SASS variable overrides.
• Metadata: Unified ERC and Article ID management to prevent collision-based deployment failures.

---

🧩 Meridian Low-Code Framework

The project utilizes the Liferay Meridian pattern for site orchestration and fragment development:

• Site Initializer: Modular recursive structure in site-initializer/ for Fragments, Documents, and Style Books.
• Fragments: Standardized group collections using Clay CSS for a native Liferay UI.
• Dynamic Wiring: Content assets are linked via ERC tokens, ensuring zero-configuration deployment across environments.

🛠️ LCP & Docker Configuration

All extensions include a full LCP.json compliant with Liferay Cloud standards:

• Jobs (Batch, Initializer): Optimized to 50MB.
• Deployments (Theme, React Apps): Configured with targetPort: 80 and explicit ports array mapping (external: true).
• Backend Nodes: Configured with targetPort: 3001-3004 and explicit ports array mapping (external: true).

---

Built with ❤️ for Sales Engineers and the Liferay Docker Manager.