Help

Support

Use this checklist to help support requests receive a clear and efficient response.

Before requesting support

• Confirm the issue on an unmodified copy when possible.
• Run the documented install and build commands.
• Check browser console output and include relevant error details.

What support includes

What support does not include

Custom application development, hosting configuration, third-party service changes, and extensive design customization are normally separate services.

How to report a bug

1. Write a concise description of what happened and what you expected.
2. Include the page URL, browser, operating system, and relevant console errors.
3. Add clear steps that allow the issue to be reproduced.
4. Include screenshots or a short recording when useful.

Customization services

For bespoke screens, integrations, data connections, or brand implementation, define your own service channel and project scope.

Documentation maintenance

npm run docs:build
npm run docs:check

Edit vexui-documentation/pages.json, vexui-documentation/release.json, and vexui-documentation/template.html for guide changes. Both documentation folders are regenerated together. The generator reads routes, navigation, and package.json to keep inventory and dependency references aligned. CHANGELOG.md is regenerated from the same change entries.

Before upgrading

Back up customized files, compare source changes, inspect dependency changes, and verify your backend integrations and data migration requirements. Review the version 2.0.0 changelog and upgrade notes before updating.

Vexui customer documentation Version 2.0.0 Standalone HTML documentation