How akveo/blur-admin works
1. This repository is a front-end admin template built on AngularJS 1.x with Bootstrap, Sass, jQuery, and a Gulp-based build pipeline. Its main output is a browser-loaded SPA-style admin UI, not a backend service.
2. The application code lives under src/app and is split into two major layers: pages for feature screens and theme for reusable layout/UI infrastructure. That separation is the key architectural boundary in the repo.
3. src/app/pages contains the actual admin sections: dashboard, charts, forms, maps, tables, UI widgets, profile, mail, and components like timeline/tree. Each area is grouped as its own module and view set, which makes the feature boundaries clear for routing and lazy-ish organization within the Angular app.
4. src/app/theme provides the shared shell and cross-cutting UI behavior. It includes layout components such as sidebar, top bar, content header, widgets container, back-to-top, modal helpers, wizard, and message center, plus common directives, filters, services, and configuration. This layer is what gives the app its admin-panel chrome and reusable interaction patterns.
5. The theme layer also contains custom UI plumbing: directives for file input, focus, scroll tracking, width tracking, auto-expand, animations, and slider integration; services for utilities, file reading, intervals, progress modals, and preloading; and filters for image/text formatting. These are shared dependencies used across multiple page modules.
6. Feature pages are mostly view/controller pairs with some directive-based subcomponents. For example, dashboard widgets are broken into smaller self-contained pieces like weather, traffic chart, todo, map, calendar, and pie/line chart blocks, which are then composed into the dashboard page.
7. Charting and map integrations are first-class subsystems. Charts are grouped by library under pages/charts with amCharts, Chart.js, Chartist, and Morris variants; maps are grouped under pages/maps with Google Maps, Leaflet, bubbles, and line overlays. These are integration-heavy areas where external visualization libraries are wrapped in Angular modules and directives.
8. Forms and controls are organized as a dedicated subsystem under pages/form, with inputs, layouts, and wizard flows. It includes specialized widgets like date pickers, select pickers, switches, tags input, and validation examples, which shows the project is as much a UI component showcase as an application shell.
9. Styling is centralized in src/sass, with shared theme variables/mixins, component SCSS, page-specific SCSS, color-scheme variants, and Bootstrap overrides. The “blur” and “mint” theme variants are implemented primarily through Sass structure and configuration rather than separate app codebases.
10. Static assets live in src/assets and are treated as part of the UI bundle: fonts, icons, images, skin thumbnails, profile/todo/feed artwork, and theme icons. These assets support the visual identity of the demo/admin shell.
11. The root src/index.html, plus src/auth.html, src/reg.html, and src/404.html, indicate multiple top-level entry pages beyond the main app. The auth and registration pages are separate from the authenticated dashboard shell, while the 404 page is a standalone fallback view.
12. Build and release are managed through Gulp tasks in the gulp directory, with scripts for styles, scripts, images, injection, server, docs, marketplace, and build/release flows. This means the architecture includes a pre-processing pipeline that compiles Sass, bundles Angular code, and assembles distributable assets.
13. The docs folder is a separate documentation site with its own package and templates, not part of the runtime app. It contains tutorial articles and generated documentation assets, so the repo supports both the product UI and a companion docs portal.
14. Overall, the runtime architecture is a client-side admin shell: Angular modules route to page modules, page modules consume shared theme services/components, and all of it is packaged by Gulp from src plus Sass/assets into the final browser deliverable.
Main entry points: pages.module.js Pages layer · theme.module.js Theme layer · gulpfile.js Gulp build · app.js App bootstrap
Components 25
Runtime app
AngularJS SPA and entry pages
- Main entry · Primary browser entry for the admin SPA
src/index.html - Auth page · Standalone login/auth entry
src/auth.html - Register page · Standalone registration entry
src/reg.html - Fallback page · Standalone 404 view
src/404.html - App bootstrap · Top-level AngularJS application wiring
src/app/app.js - Pages layer · Feature-screen modules for the admin app
src/app/pages/pages.module.js - Theme layer · Reusable chrome, UI plumbing, and cross-cutting services
src/app/theme/theme.module.js - Dashboard · Widget-heavy landing dashboard
src/app/pages/dashboard/dashboard.module.js - Charts · Visualization pages wrapping chart libraries
src/app/pages/charts/charts.module.js - Maps · Map integrations and overlays
src/app/pages/maps/maps.module.js - Forms · Inputs, layouts, and wizard flows
src/app/pages/form/form.module.js - UI kit · Alerts, buttons, icons, modals, progress, tabs, and more
src/app/pages/ui/ui.module.js - Tables · Basic and smart table demonstrations
src/app/pages/tables/tables.module.js - Profile · Profile screen and modal flow
src/app/pages/profile/profile.module.js - Components · Mail, timeline, and tree showcase pages
src/app/pages/components/components.module.js - Theme components · Sidebar, panels, wizard, top bar, and reusable shell widgets
src/app/theme/components/components.module.js - Theme plumbing · Shared directives, filters, inputs, and utility services
src/app/theme/theme.service.js - Dashboard widgets · Weather, traffic, todo, map, calendar, and charts
src/app/pages/dashboard - Chart adapters · amCharts, Chart.js, Chartist, and Morris wrappers
src/app/pages/charts - Map adapters · Google Maps, Leaflet, and overlay variants
src/app/pages/maps - Form widgets · Date pickers, selects, switches, tags, and validation demos
src/app/pages/form/inputs/widgets - UI assets · Fonts, icons, images, skins, and artwork
src/assets
Styling
Sass theme and page styles
- Sass system · Centralized styling for theme, pages, and variants
src/sass
Tooling
Build pipeline and docs site
- Gulp build · Styles, scripts, images, injection, server, docs, and release tasks
gulpfile.js - Docs site · Separate documentation portal and content pipeline
docs
Connections 27
- Main entry → App bootstrap: loads · Main entry loads the Angular app
- App bootstrap → Pages layer: routes to · App bootstraps feature-page modules
- App bootstrap → Theme layer: uses · App bootstraps shared theme shell
- Pages layer → Dashboard: includes · Feature module set includes dashboard
- Pages layer → Charts: includes · Feature module set includes charts
- Pages layer → Maps: includes · Feature module set includes maps
- Pages layer → Forms: includes · Feature module set includes forms
- Pages layer → UI kit: includes · Feature module set includes UI showcase pages
- Pages layer → Tables: includes · Feature module set includes tables
- Pages layer → Profile: includes · Feature module set includes profile
- Pages layer → Components: includes · Feature module set includes shared components pages
- Dashboard → Dashboard widgets: composes · Dashboard page is assembled from smaller widgets
- Charts → Chart adapters: wraps · Charts page wraps multiple chart libraries
- Maps → Map adapters: wraps · Maps page wraps map libraries and overlays
- Forms → Form widgets: contains · Forms feature exposes specialized input widgets
- Theme layer → Theme components: provides · Shared shell components come from the theme layer
- Theme layer → Theme plumbing: provides · Shared directives, filters, inputs, and services come from the theme layer
- Theme layer → UI assets: consumes · Theme layer uses bundled UI assets
- Sass system → Theme layer: styles · Sass architecture skins the shared theme and UI chrome
- Sass system → Pages layer: styles · Sass architecture styles the feature pages
- Gulp build → Sass system: builds · Gulp compiles Sass into distributable styles
- Gulp build → App bootstrap: bundles · Gulp bundles Angular application scripts
- Gulp build → UI assets: packages · Gulp copies and optimizes static assets
- Gulp build → Docs site: generates · Gulp includes a separate docs build flow
- Auth page → Theme layer: shares · Auth page reuses shared theme assets and styling
- Register page → Theme layer: shares · Register page reuses shared theme assets and styling
- Fallback page → Sass system: styled by · Fallback page has dedicated Sass styling