What's included. What's changed.
Review your current package, understand its capabilities, and prepare your custom application for future updates.
Explore version 1.0.0About these release notes
A clear record of the package you are using
This page summarizes the current MetraUI package and explains how to review updates. Its version comes from package.json.
Version 1.0.0 is the first documented release of MetraUI. Future entries can be added below with their publication date, changes, and any steps needed to update a customized project.
Version 1.0.0
Initial release - HTML / Bootstrap 5
The first MetraUI release brings together a responsive Bootstrap 5 admin interface, a broad library of workflow pages, and the source tools needed to customize and build the template.
What's included
-
Dashboards for key business teams
Sales, ecommerce, CRM, finance, logistics, HR, projects, support, and AI dashboard examples, with matching workflow pages for common tasks.
-
Flexible navigation and appearance
Vertical and horizontal navigation, sidebar layout options, a live appearance customizer, color palettes, and light or dark theme modes.
-
Reusable interface and application pages
Bootstrap-based cards, forms, tables, calendars, authentication screens, chat and mail views, file management, invoices, and other admin workflows.
-
Interactive plugin examples
Chart integrations including ApexCharts, Chart.js, and ECharts; data tables; maps; calendars; file uploads; editors; and other interface plugins.
-
Editable source and local build workflow
HTML pages and shared template parts, SCSS, JavaScript, and assets under
src/. Runnpm installandnpm run devto compile the styles, assemble pages, copy dependencies, and preview the generateddist/output. -
Customer guidance
Setup and customization documentation, project FAQs, support contact details, and release notes to help customers get oriented.
Sample records and interface actions demonstrate the UI. Authentication, database storage, API connections, uploads, and server-side validation must be connected to your own application before production use.
Before installing an update
Protect your custom work
-
Back up your application.
Keep your existing source, configuration, and lockfile before replacing files.
-
Review the changed files.
Compare shared template parts, theme variables, page scripts, and dependency changes against your customizations. Avoid replacing the entire source folder without reviewing it.
-
Install and rebuild.
Run npm install, then npm run dev. The workflow recreates dist, so keep all changes in src.
-
Verify your application.
Check navigation, forms, charts, tables, light and dark modes, mobile layouts, and external API connections before deployment.
How to read future updates
Consistent release categories
| Category | Meaning |
|---|---|
| Added | New pages, components, or supported features. |
| Changed | Updates to existing behavior, design, or configuration. |
| Fixed | Corrections to a documented issue. |
| Removed | Features or files that are no longer included. |
| Migration notes | Steps customers need to apply when updating. |
For each future release, record its version, publication date, affected features, and any migration instructions. Keep earlier entries available so customers can compare versions.