openolat-frontend

Implement OpenOlat themes and debug CSS layout issues.

434|167|Updated Mar 29, 2018
One-click install
npx skills add https://github.com/OpenOLAT/OpenOLAT --skill openolat-frontend
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openolat-frontend
Source: https://github.com/OpenOLAT/OpenOLAT/tree/main/.claude/skills/openolat-frontend
Command: npx skills add https://github.com/OpenOLAT/OpenOLAT --skill openolat-frontend

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenOlat frontend theming and DOM conventions are complex, making consistent styling, layout debugging, and component rendering across themes challenging without centralized guidance.

Core Features & Use Cases

  • Provides architecture references for themes, CSS class conventions, DOM structure, and component renderers to accelerate theme creation and debugging.
  • Helps developers implement custom OpenOlat themes, ensure consistent UI across modules, and understand the frontend rendering pipeline.
  • Use Case: A developer creates a new theme for a course site and validates class names, breakpoints, and template rendering against the reference.

Quick Start

Review the OpenOlat frontend documentation and start a new theme by following the documented steps in the openolat-frontend guide.

Frequently Asked Questions about openolat-frontend

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a custom OpenOlat theme with the correct CSS architecture?

To create a custom OpenOlat theme, follow the documented steps in the frontend guide to apply the correct CSS class conventions, DOM structure, and component rendering patterns for consistent styling across modules.

What is the best way to debug layout issues in OpenOlat frontend components?

Debugging OpenOlat layout issues involves referencing the frontend architecture documentation to validate CSS class names, breakpoints, and template rendering patterns against the established component rendering conventions.

How does component rendering work across multiple OpenOlat deployments?

Component rendering across OpenOlat deployments relies on standardized DOM conventions and a centralized CSS architecture, ensuring consistent UI rendering pipelines and predictable module styling.

Can I use Bootstrap for OpenOlat theming and component styling?

Yes, OpenOlat frontend theming incorporates Bootstrap alongside its CSS architecture, allowing developers to leverage established class conventions and DOM structures for consistent component rendering.

Why does my OpenOlat course site display inconsistent styling across different modules?

Inconsistent OpenOlat styling usually occurs when custom themes deviate from standard CSS class conventions and DOM structures, requiring validation against the frontend architecture reference to ensure UI consistency.

Do I need to understand DOM conventions to build OpenOlat custom themes?

Yes, understanding OpenOlat DOM conventions and CSS architecture is required to build custom themes, as these conventions dictate how component renderers function and ensure consistent layout across deployments.