librelad f896df6006 refactor(admin): move bare css/ into admin/core/ for sub-system consistency
admin had sub-system folders (config/overview/system/ssh/peers) AND a bare
root css/ (admin.css) — inconsistent. A component's shared base belongs in a
core/ sub-folder once it has sub-systems (matching apps/core/), so admin.css
moves to admin/core/css/admin.css. Audit confirms all components are now
consistent: sub-system components (apps, admin) use core/ + sub-systems;
single-page components (backup/dashboard/tasks/updater) stay flat js/css/html
(no sub-systems, so no core/ needed).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Signed-off-by: librelad <librelad@digitalangels.vip>
2026-05-30 18:26:31 +01:00

129 lines
6.3 KiB
HTML
Executable File

<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>LibrePortal - Modern Docker Management</title>
<link rel="icon" type="image/svg+xml" href="/core/icons/libreportal.svg">
<link rel="icon" type="image/x-icon" href="/core/icons/favicon.ico" sizes="any">
<link rel="apple-touch-icon" href="/core/icons/libreportal.svg">
<!-- Styles -->
<!-- Base token layer (theme-agnostic): --font-mono, --page-* identity hues -->
<link rel="stylesheet" href="/core/css/tokens.css">
<link rel="stylesheet" href="/core/css/themes.css">
<link rel="stylesheet" href="/core/css/loading-screen.css">
<link rel="stylesheet" href="/core/css/setup-wizard.css">
<link rel="stylesheet" href="/core/css/style.css">
<link rel="stylesheet" href="/components/admin/config/css/ip-whitelist.css">
<link rel="stylesheet" href="/components/apps/port-manager/css/port-manager.css">
<link rel="stylesheet" href="/components/backup/css/backup.css">
<link rel="stylesheet" href="/components/admin/ssh/css/ssh.css">
<link rel="stylesheet" href="/components/admin/core/css/admin.css">
<link rel="stylesheet" href="/components/apps/services/css/services.css">
<link rel="stylesheet" href="/core/css/modal.css">
<link rel="stylesheet" href="/components/apps/tools/css/tools.css">
<link rel="stylesheet" href="/components/apps/routing/css/routing.css">
<link rel="stylesheet" href="/core/css/login.css">
<link rel="stylesheet" href="/core/css/aurora-background.css">
<link rel="stylesheet" href="/core/css/topbar.css">
<link rel="stylesheet" href="/core/css/sidebar.css">
<link rel="stylesheet" href="/components/apps/core/css/apps-layout.css">
<link rel="stylesheet" href="/components/apps/core/css/apps.css">
<link rel="stylesheet" href="/core/css/forms.css">
<link rel="stylesheet" href="/core/css/config.css">
<link rel="stylesheet" href="/components/apps/core/css/service-buttons.css">
<link rel="stylesheet" href="/components/dashboard/css/dashboard.css">
<link rel="stylesheet" href="/components/tasks/css/tasks.css">
<link rel="stylesheet" href="/components/updater/css/updater.css">
<link rel="stylesheet" href="/core/css/update-notifier.css">
<script>
// Inline data-theme bootstrap — runs before any rendering so the right
// palette tokens resolve on first paint. Synchronously injects a
// <link> to the saved theme's CSS (which lives at
// /themes/<name>/theme.css) so even the very first frame paints with
// the correct palette. ThemeRegistry below additionally <link>s every
// discovered theme so the dropdown can switch between them without
// another fetch.
(function () {
var legacy = localStorage.getItem('selectedTheme');
if (legacy && !localStorage.getItem('theme')) localStorage.setItem('theme', legacy);
if (legacy) localStorage.removeItem('selectedTheme');
var theme = localStorage.getItem('theme');
if (theme === 'dark' || theme === 'blue') theme = 'dark-blue';
if (!theme) theme = 'nebula';
localStorage.setItem('theme', theme);
document.documentElement.setAttribute('data-theme', theme);
// Synchronous <link> injection. Inserted via document.write so the
// parser blocks on this stylesheet — guarantees first paint has
// the palette tokens defined. Marked with data-theme-css="<name>"
// so ThemeRegistry can detect and skip duplicates.
document.write(
'<link rel="stylesheet" href="/themes/' + theme +
'/theme.css" data-theme-css="' + theme + '">'
);
})();
</script>
<script src="/core/boot/theme-registry.js"></script>
<script src="/core/boot/custom-select.js"></script>
<script src="/core/boot/custom-number.js"></script>
</head>
<body>
<!-- Topbar Container -->
<div id="topbar-container">
<!-- Topbar will be loaded here -->
</div>
<!-- Main Content Container -->
<main id="main-content" class="main">
<div id="app-content">
<!-- App content will be loaded here -->
</div>
</main>
<!-- Scripts -->
<!-- Auth must load first — gates all other initialization -->
<script src="/core/boot/auth-manager.js"></script>
<!-- Essential Bootstrap -->
<!-- LpUi runs first so body.lp-ui--advanced / lp-ui--dev are set
before any page/component renders → no FOUC of advanced sections. -->
<script src="/core/lib/lp-ui.js"></script>
<script src="/core/lib/dom-helpers.js"></script>
<script src="/core/lib/ui-helpers.js"></script>
<script src="/core/lib/router.js"></script>
<script src="/core/lib/data-loader.js"></script>
<script src="/core/lib/system-live.js"></script>
<script src="/core/lib/dismissible.js"></script>
<script src="/core/ui/eo-modal.js"></script>
<script src="/core/lib/task-refresh-coordinator.js"></script>
<script src="/components/dashboard/js/dashboard.js"></script>
<script src="/core/boot/system-loader.js"></script>
<script src="/core/boot/loading-ui.js"></script>
<script src="/core/boot/setup-detector.js"></script>
<script src="/core/boot/setup-wizard.js"></script>
<script src="/core/boot/setup-completion-watcher.js"></script>
<script src="/core/boot/system-orchestrator.js"></script>
<!-- Feature-module kernel. Currently passive: defines window.LP.features and
loads the page manifest; spa.js consults it for routing. See
docs/frontend-modularization.md. -->
<script src="/core/kernel/feature-registry.js"></script>
<script src="/core/kernel/services.js"></script>
<script src="/core/kernel/lifecycle.js"></script>
<!-- Component (page) modules are NOT listed here: the kernel loads each one's
self-registering index.js from the manifest (components/manifest.dev.json)
before routing. Adding a page = drop a components/<id>/ folder + a manifest
entry, no index.html edit. Heavy controllers stay lazy (loaded by mount). -->
<!--
Page-specific controllers are loaded on demand by spa.js / config-manager.js
when the user navigates to the relevant route. Keeping them out of the
initial <script> block trims ~200 KB raw (~50 KB gzipped) off the cold-load
cost AND avoids parsing them up front on the dashboard, which most users
land on. Each handler's loadScript() call is idempotent — subsequent
navigations to the same route are free.
-->
<script src="/core/kernel/spa.js"></script>
</body>
</html>