> [!NOTE] Note > These are a set of notes that will be updated, everything is rough draft These are a set of notes as I develop the Quick Cost Planner App (qcp). I am writing this app using Sveltekit. I am not a web developer and am using this project to teach myself the fundementals. **Main TODO** - [ ] delete project to staff entries in the project_staff table when a project is deleted - [ ] write the details for how - [ ] diagram out the home page - [ ] diagram out the different way budget will be allocated ## Wednesday, August 14th 2024 What i want to work out today is the basic concept of the budget for a project. So here is what I am thinking, user creates a project by filling the details required, basic info needed for a project is just: - name - client - budget - start/end date - staff (rates) - initial budget layout (uniform ...) I think this initial set up should be ## Tuesday, August 13th 2024 Ok starting today I am going to keep track of things with a running todo list, I really dont want to have this on list on github so I will place at the top of this doc, and just have these notes below it. #### Diagram for QCP Budgets ![[Pasted image 20240813231550.png]] ## Sunday, August 11th 2024 Alright its technically a new day but its just late Saturday night now. The last thing I want to get ## Saturday, August 10th 2024 Today the focus is the projects page, here is what I have so far. ![[Pasted image 20240810010634.png]] I want to flesh out the create project route of the application. Currently it allows you to create a new project with the following data: - Name - Client - Budget total - Description - Start Date - End Date I want to start having a way for the budget to be useful. The initial thing I want to implement is just a few templates on how to distribute the budget across the span of the project's lifetime (end_date - start_date). For now the templates will reflect the ones that are useful to me at my current job. - even burn - distribute the budget uniformly across the entire lifespan of the project - upfront burn - burn through budget more heavily early and taper off towards the end - tailend burn - start with low spending and have this increase towards the end of the project. The purpose of these is that they give me a starting point and I don't have to tweak a bunch just to get to a point where I feel comfortable. Before I can start this I need to introduce the concept of **staff**. Here is the basic model I will be using: ```sql CREATE TABLE "users" ( "id" INTEGER, "name" TEXT NOT NULL, "position" TEXT NOT NULL, "rate" NUMERIC, PRIMARY KEY("id")) ``` ok done, its very basic and pretty much just looks like the projects page: ![[Pasted image 20240811005840.png]]