client/src/App.vue

@@ -4,9 +4,10 @@ import Header from './components/Header.vue'
 </script>
 
 <template>
-  <h1>Here is a child component!</h1>
+  <h1>straight up gargoyling it !</h1>
   <Header />
   <Header />
   <Header />
   <Header />
+  <h1>imagining what I could do with themes :o</h1>
 </template>

client/src/assets/mobus.txt

@@ -0,0 +1,3 @@
+
+// assets will contain common public resources
+// icons, fonts (if needed locally), images, whatever

client/src/components/Header.vue

@@ -1,4 +1,7 @@
 
+<!-- you know what components are :D -->
+<!-- though I do miss angular's support for separating the file ( though i guess its technically possible in vue but it gets disorganized fast ) -->
+
 <script setup lang="ts">
 import { ref } from 'vue'
 

client/src/composables/what.ts

@@ -0,0 +1,3 @@
+
+// idk really what composables are but I think its extra service code that can be used in components
+// I think they're useful for moving data from a data store to the component but I could just be trolling

client/src/models/User.ts

@@ -0,0 +1,2 @@
+
+// models are the data objects stored in the database. models defined here must match models defined in api/models 

client/src/pages/index.vue

@@ -0,0 +1,2 @@
+
+<!-- pages are the base instance for routes. an endpoint serves a page, and the page loads components -->

client/src/router/index.ts

@@ -1,3 +1,8 @@
+
+// generated by vue
+// the router creates front-end endpoints and serves pages to them
+
+
 import { createRouter, createWebHistory } from 'vue-router'
 
 const router = createRouter({

client/src/services/UsersService.ts

@@ -0,0 +1,4 @@
+
+// services are kinda whatever, but in general its a good idea for all api calls to be within a service (at least thats how angular handles it)
+// this user service will handle all to <-> from the server when handling user objects
+// should be injected with the http client (I think its axios ?)

client/src/stores/UsersStore.ts

@@ -0,0 +1,5 @@
+
+// stores are for component state management
+// Pinia (?) i kinda dont get it because in angular you just hook a component to a service and that's it,
+// though I guess the service handled the state management
+// sighh