Frontend and UI – Design System
The Frontend and UI Design System defines how styles and components are structured, customized, and applied across Blade templates. It leverages Bootstrap’s core framework and the OneUI theme to ensure a cohesive look, responsive layout, and consistent utility class usage.
Bootstrap Integration
Bootstrap provides the foundational grid, components, and utilities. OneUI builds on top of it by importing core Bootstrap files, then overriding or extending styles.
- Core imports: Bootstrap variables and mixins
- Components: Forms, buttons, navs, modals, etc.
- Overrides: OneUI-specific mixins and component styles
// resources/assets/sass/main.scss
// Bootstrap variables
@import 'bootstrap/variables';
@import 'bootstrap/mixins';
// Bootstrap components
@import 'bootstrap/reboot';
@import 'bootstrap/type';
@import 'bootstrap/forms';
@import 'bootstrap/buttons';
// …
// OneUI customizations
@import 'oneui/variables';
@import 'oneui/mixins';
@import 'oneui/layout';
@import 'oneui/block';
// …
// Themes and overrides
@import 'oneui/variables-themes';
@import 'oneui/layout-variations';
// …
// User styles
@import 'custom/main';
OneUI Theme
OneUI defines its own variable map, including default palettes and Prep Network brand colors. These drive component color, spacing, and z-index defaults.
| Variable Group | Purpose |
|---|---|
$theme-colors |
Base color shades (primary, info, etc.) |
$prep-girls-hoops |
Brand colors for event types |
$space-base |
Global gutter and padding units |
| Z-indices | Sidebar, overlays, blocks stacking order |
// resources/assets/sass/oneui/_variables.scss
$theme-colors: map-merge(("primary-light": lighten($primary,15%), …), $theme-colors);
$prep-girls-hoops: #01B7FF;
$prep-hoops: #F76517;
$space-base: 1.875rem !default;
$zindex-sidebar: $zindex-fixed + 2 !default;
// …
SCSS Architecture
OneUI’s SCSS is organized into clear layers:
- mixins/: Reusable patterns (alerts, buttons, content layouts)
- components/: Partial files for badges, blocks, forms, dropdowns
- themes/: Color-theme generators (
@include color-theme(...)) - utilities/: Helper classes and responsive tweaks
flowchart LR
subgraph Bootstrap
A[functions] --> B[variables]
B --> C[mixins]
C --> D[components]
end
subgraph OneUI
D --> E[variables]
E --> F[mixins]
F --> G[components]
G --> H[themes]
H --> I[custom/main]
end
{
"title": "Best Practice",
"content": "Use OneUI utility classes to maintain design consistency."
}
Blade Component Usage
Blade templates utilize OneUI’s classes for layout, navigation, and UI elements:
container-base: Consistent horizontal padding#page-container: Main wrapper for sidebar, header, contentblock,block-header,block-content: Card-like sectionsbtn,btn-dual,btn-rounded: Button variants
<!-- resources/views/layouts/backend.blade.php -->
<body>
<div id="page-container">
@include('dashboard.partials.flash-message')
<main id="main-container">
@yield('content')
</main>
</div>
@vite('resources/assets/js/oneui/app.js')
<script>
window.addEventListener('DOMContentLoaded', function() {
One.helpers(['select2', 'masked-inputs']);
});
</script>
</body>
JavaScript Helpers
OneUI ships with a small JS framework to initialize interactivity:
- Template class: Auto-initializes page, sidebar, overlay, header toggles
- Helpers: Tooltips, popovers, custom file inputs, scroll-to, ripple effects
// resources/assets/js/oneui/modules/template.js
export default class Template {
constructor() {
this._uiInit();
}
_uiInit() {
this._lPage = jQuery('#page-container');
this._lSidebar = jQuery('#sidebar');
// …
}
}
Custom Styling and Theming
You can extend or override OneUI via:
resources/assets/sass/custom/main.scss: Place project-specific overrides- Theme selection: Swap
@import 'oneui/themes/*.scss'to apply different palettes - Third-party plugins: Style overrides under
resources/assets/sass/vendor/…
This layered approach ensures updates to OneUI or Bootstrap do not break custom styles.