Customization Guide

Change brand and design

Edit CSS variables at the top of assets/css/style.css for color palette, typography and surface tones.
Edit header and footer elements in each standalone HTML page. For site-wide changes, use search-and-replace or migrate into templating components.
Edit assets/img/logo.svg, assets/img/favicon.svg, and assets/img/hero-learning.svg in any vector editor.

Update assets/js/catalog.js (window.MENTORA_COURSES). Each course has an id, title, tag, level, hours, lessons, price, old, mentor, role, desc, skills, modules, outcomes, and audience.
For titles/descriptions shown in original static HTML pages, update the associated course-<id>.html file as well. Catalog cards are generated dynamically on the directory/saved pages.
Change lesson paragraphs in assets/js/app.js under the lessonContent object. Lesson progress remains client-side.
When changing IDs, update the corresponding course-<id>.html and learn-<id>.html files, graphics filenames, and navigation links. Old saved browser progress may not carry over.

Browser storage keys have the mentora:v1: prefix. For production, move student data behind secure authentication and a server.
Contact form uses an email-app draft or copy; replace the placeholder recipient, or integrate your own protected server endpoint.
Pricing toggle is sample UI only; integrate payments only after appropriate backend checks and secure billing provider setup.

Replace sample legal pages before launch.
Update title/description tags in each HTML file, and set actual absolute og:image and canonical URLs.
Add your own sitemap and robots policy depending on which pages you want indexed. The SellOnBay marketplace sitemap limits do NOT apply to a buyer's Mentora website template.
For real academy production, consider removing public learn-*.html if lessons should be behind authentication.

This documentation accompanies an editable frontend demo, not a production learning management system.