commit 1f61560f2e0503dfaf76a3b6cc19a22ceee34cef
parent 140bfa802c23c591a7401a6e2cc38238862b8900
Author: Brennen T. Mazur <brennen@madis.cool>
Date: Fri, 17 Feb 2023 10:57:52 -0700
cleaning up root dir and update README
Diffstat:
2 files changed, 4 insertions(+), 23 deletions(-)
diff --git a/README b/README
@@ -1,14 +1,13 @@
stc is a simple time card implementation for personal use or small to medium size businesses.
-The goal of this project is to create an extensible tool for time and other asset management.
+The goal of this project is to create an extensible tool for time and asset management.
-Current plans are to use mongoDB as the backend to a simplistic dashboard for accessing management interfaces, overseeing and managing lower role's clocked in status, and requesting reports for not only current/past pay periods sorted by employee, but also by project code
+Current plans are to use mongoDB as the backend to a simplistic dashboard for accessing management interfaces, overseeing and managing role's clocked in status, and requesting reports for not only current/past pay periods sorted by employee, but also by project code
Project has potential to be renamed to scms (simple content management system) based on potential end-goals of multiple clients.
-An option would be to create the base structure for the cms (as human resource management [ex. time tracking]) and allow patches to include additional functionality like equipment tracking etc. Allows no-nonsence approach to anti-bloat management software.
+An option would be to create the base structure for the cms (as human resource management [ex. time tracking]) and allow patches to include additional functionality like equipment tracking etc.
-db file will likely be /scms.db or whatever the appname resolves to
templates holds each "component" either a standalone file, or a directory for a index.html(full page route) and widget.html(dashboard interactable view)
-For organization specifics... it might be usefull to create diff files for specific additions etc? Possibly too costly to maintain over master version changes.
+For organization specifics... it might be usefull to create diff files for specific additions etc? Possibly too costly to maintain over master version changes. This needs to be determined and refined.
diff --git a/README.planfor b/README.planfor
@@ -1,18 +0,0 @@
-#Plan for getting appropriate modules
-
-on successfull auth -> base.html utilizes successfulAuth() -> ?validUSR?[user-name(str), accessable modules[array], server-connection(bool)]
- accessable modules and server-connection are used for navbar creation and to check if local-storage is necessary for temp operations
- user-name used for welcome "prompt"
-
-each route checkAuth() -> directs to login if false, else
- calls routeblock
-
-Routeblocks getRelevantData(not necessarily one fn, likely individual) -> relevantData[clocked-in,project,purdium,lunch]
- used to populate ?MACRO? for displayed widget/page
- should checkAuth() # We should be checking constantly for auth to verify and doubleverify before any exchange of data or operations
-#####
-I've overcomplicated this, the responses can be parsed as the raw JSON data returned from the db... Everything will request relatively small amounts of data until the reports which will likely need to make multiple calls? then return a txt/pdftex file
-
-#####
- This implies you have db.users.$user.permission[val1,val2,...]
- /admin.html should have 'preset' permissions per role and allow toggling individual level
