How arieloss/home_control_updating works
Project Type and Purpose
• This is a purely front-end, multi-page UI/dashboard template delivered as static files (HTML, CSS, JS).
• There is no application backend or database code here—everything is delivered to and executed in the browser.
• The README (“coo”) does not add functional context, but the file‐tree shows an admin/dashboard interface built on third-party JS/CSS libraries (CKEditor5, FullCalendar, DataTables, ApexCharts, etc.).
File-Structure Analysis
• Top‐level HTML pages:
• interface.html, page.html, principale.html, register.html, TEST/INDICATIF.html
• Custom static assets:
• assets/css, assets/js/pages (per‐page init scripts), assets/js/app.js, assets/images, assets/fonts, assets/lang/*.json
• Vendor libraries (all under assets/libs):
• @ckeditor, @fullcalendar, Bootstrap, chart.js, apexcharts, select2, Dropzone, Leaflet, Swiper, SweetAlert, etc.
• No src/backend folder, no server config—this is a static‐hosted solution.