How vuegatti/vuegattifront works
Project type and purpose
• This is a single-page application (SPA) built with Vue.js 3, Vue Router and Pinia on the frontend, backed by a mock JSON Server (hosted on Glitch) via Axios.
File structure
• Top‐level folders:
• public / index.html – static assets and HTML entry point.
• src – your Vue app’s source code:
· components – reusable UI elements (buttons, sidebar, headers, pickers)
· views – page-level components (HomePage, CalendarView, SignInView, etc.)
· router – route definitions (src/router/index.js)
· stores – Pinia stores (account, history, calendar)
· utils – axios instance/HTTP client
· App.vue / main.js – the root component and app initialization.
• Config / build files:
• vite.config.js – Vite build config
• package.json / package-lock.json – dependencies
• eslint.config.js / .prettierrc.json – linting and formatting rules
README for additional insights
• Tech stack clearly calls out: Vue3, Vue Router, Pinia, CSS3, Chart.js, JSON Server, Axios, Glitch, Vercel.
• Features: calendar-based record keeping, category graphs, date-based notes, auth & profile.
Elements
• Labels for each component/module (e.g., “Pinia store: history.js”).
• Backend/API in another (e.g., orange)
• External services in a third (e.g., green)