- A Bootstrap5 best practices setup
- Build-and-deploy automation
- Ca. 20 lightweight Razor components
- 5 already prepared Layouts (full-width, centered, etc.)
- MagicMenu Engine
- MagicClasses (TODO:)
- MagicSettings
- MagicLanguages
- ...
This is a Bootstrap5 best practices setup using
- SASS
- Typescript
- Webpack
It's optimized to run in both Visual Studio as well as VS Code
Every Oqtane Theme must be created / compiled using a unique namespace.
This is something like MyCompany.Oqt.Themes.MyCustomer.Client
.
To start, you'll need to rename/replace the template names everywhere in the project.
This is fully automated using npm run rename-project
.
TODO: ...nuget ...etc.
Designers work iteratively in many small steps.
This means a lot of small changes and a lot of reloading the page.
Since 95% of all work is done in SASS,
we've created a npm/webpack configuration which will
take -watch
all your changes, automatically build and copy to the Oqtane you're working on.
This works both for Oqtane installations on your PC as well as Oqtane servers in your network.
TODO: containing only minimal HTML to create just about any design you want - usually without recompiling Razor
- Default - Floating content on background, full-width sticky-header
- Fullscreen - Modules can use the full width to set backgrounds
- Centered - Content and Menu are max-width, background to right and left
- Centered-Submenu - Paged/floating content with submenu to the left
- Float-WideHeader - Paged/floating content with wide header
TODO: allowing you to define what is shown in what menu, allowing designers to quickly modify visible menu structures in header, sidebar, footer, mobile etc.
Todo:
TODO: -A configuration system which