Bootstrap documentation
For the HTML pages and Bootstrap assets in the package root.
- Bootstrap 5.3.8 and Bootstrap Icons
- 49 template pages with local vendor assets
- Ready-to-use HTML; optional source generator
Start with your edition. Bootstrap, Tailwind, and Next.js share the Adminova design and page areas, while each keeps its own styles, source files, and development workflow.
For the HTML pages and Bootstrap assets in the package root.
For the independent HTML + Tailwind edition inside tailwind/.
For the React + TypeScript + Tailwind edition inside nextjs/.
Serve all three editions from the package root so the landing pages, documentation, and cross-edition links share one origin.
node scripts/serve-package.mjs
# Open http://127.0.0.1:8080/landing/
# Documentation: http://127.0.0.1:8080/documentation/Node.js 20 or newer runs this preview server. No package installation is needed to view the included HTML and compiled styles. Open index.html for Bootstrap or tailwind/index.html for Tailwind.
adminova/
├── landing/index.html Shared product landing
├── landing/bootstrap/index.html Bootstrap overview
├── landing/preview.html Layout/theme preview launcher
├── documentation/index.html This documentation hub
├── documentation/bootstrap/ Bootstrap guide
├── documentation/tailwind/ Tailwind guide
├── documentation/nextjs/ Next.js guide
├── nextjs/ Next.js source and exported preview
├── landing/nextjs/ Next.js overview
├── index.html + assets/ Bootstrap dashboard and assets
├── tailwind/
│ ├── index.html + assets/ Tailwind dashboard and assets
│ ├── landing/index.html Tailwind overview
│ ├── src/ Editable templates and styles
│ └── package.json Tailwind build commands
├── scripts/ Package and Bootstrap helpers
└── PACKAGE-GUIDE.md Maintainer organization guideInstall dependencies inside nextjs/ using npm ci. Run npm run dev for development, npm run build for the production static export, and npm run check for route, asset, and TypeScript checks. The HTML editions remain ready to preview without a build.
The root netlify.toml builds Next.js and assembles all editions into dist/. See the Next.js setup and deployment guide.
| Task | Bootstrap HTML | Tailwind HTML | Next.js + React |
|---|---|---|---|
| Open the dashboard | Bootstrap preview | Tailwind preview | Next.js preview |
| Read the guide | Bootstrap guide | Tailwind guide | Next.js guide |
| Preview workflow | Included HTML and runtime assets | Included HTML and compiled CSS | Install and build; export includes HTML, CSS, and JS |
| Page source | Root HTML and generator | tailwind/src/templates/ | nextjs/src/screens/ and React components |
| Style source | assets/css/refinement.css | tailwind/src/css/ | nextjs/src/styles/ |
| Build command | node scripts/build-adminova.js --assets-only | Inside tailwind/: npm run build | Inside nextjs/: npm run build |
The product landing links directly to all three dashboards. Layout, dark, and RTL links use the preview launcher to apply preferences for the selected edition, then open its dashboard. No account or preview iframe is required.
Use an HTTP server for saved product workflows and preview presets. Browser storage can be limited for directly opened file: pages. Each edition uses separate preference and product keys.
Keep the current folder structure when uploading the full showcase. Use landing/index.html as the public product entry, and link the help or documentation action to documentation/index.html. Bootstrap stays at index.html; Tailwind stays at tailwind/index.html; Next.js is available at nextjs/ after building.
After changing Tailwind templates, run its build. For the complete showcase, build Next.js and run node scripts/build-showcase.mjs, then publish dist/. The static host needs generated HTML and runtime assets, but does not need node_modules/ or source scripts.
npm ci --prefix nextjs
npm run build --prefix nextjs
npm run check --prefix nextjs
node scripts/check-package.mjs
cd tailwind
npm run build
npm run checkThe package checker covers all three editions, shared landing pages, documentation, local assets, and in-page anchors. The Tailwind checker also verifies compiled styles and JavaScript syntax.
The previews are frontend templates with illustrative records. Forms, authentication, billing, email delivery, API keys, and real store operations need your own backend. Local product demos save data in the browser; they do not connect to a live store.