How monsieurluge/later-on works
Project Type & Purpose
• This is a client-side, single-page TODO application built with Vue.js.
• It uses Vue Router for navigation, Pinia for state management, and persists data to browser localStorage.
• A plugin subsystem provides theming capabilities.
Main Components
a. Browser / User Agent (UI host)
b. Vue Application (SPA)
• Entry Point: main.js
• Core Framework: Vue.js
c. Router Layer
• vue-router (router.js / routes.js)
• Route targets: TasksPage.vue
d. UI Component Hierarchy
• App.vue
• Page: TasksPage.vue
• Reusable Components: AppHeader, TasksList, TaskItem, TaskAddForm, CollectionsNav, etc.
e. State Management
• Pinia Stores: appState.js, tasks.js
• Composables: piniaLocalStorage (persist), taskDropZone
f. Persistence
g. Plugins / Extensions
• theme-editor plugin (modules + processors + shared utilities)
• theme and themes plugins
h. Common Utilities
• src/common: taskSizes.js, utils.js
Relationships & Data Flows
• User interacts with UI components → events emit to components → components call Pinia store actions.
• Pinia actions update state → state is reactive → UI re-renders.
• piniaLocalStorage plugin hooks into store lifecycle → reads/writes state to localStorage.
• Router intercepts navigation events → loads the correct page component.
• theme-editor plugin provides a UI overlay (or editor) that manipulates CSS variables; its processors convert HSL/HEX and update DOM.
Important Patterns & Principles
• SPA architecture: clear separation of routing, UI, and state.
• Component-driven design: break UI into small, reusable Vue components.
• Unidirectional data flow via Pinia (similar to Vuex patterns).
• Local persistence plugin abstracts localStorage read/write.
• Plugin subsystem for extensibility (theme-editor).