FWM_ValPr (Update Widget)
We’re considering on updating the design and layout our current widgets for Fund Values and Prices. We’re not a web developer or web designer, and creating these widgets using solely on AI Prompting. For our first pass when building our API Workflow, we put all our widgets in one API URL. We’ve successfully created a new widget (FWM_Super), as a standalone API. We’ve determined that we can have one Project with several APIs, instead of needing to have one project: one API. Therefore, each API will be its own dedicated Widget in our Model.
// FWM_ValPr //
WBC-ValPr-Current-1 / WBC-ValPr-Current-2 / ValPr-Mockup
Notes on Design:
We need to make a few changes with Current 1 and 2. First, these are independent charts using chart.js. It works, and displays nicely, but it takes up a lot of space, so the ROI is not there based on the information provided. After brainstorming with AI, we’ve determined that we can combine these two charts, and create a right y-axis for Priees. We’ll keep the same 3 colored column model (TMV, PMV, Tar$), and each column will have its associated Price representing colored dots as Price indicators. AI hallucinated on image rendering, but it gives us a better idea on how we plan to prompt AI when coding for JS and HTML.
Notes on API:
Currently ValPr Widget is being shared with Categories Widget in the same API. We’re currently running low on our deploy project credits, so we’ll see if we can run this separately in the testing environment without using our publishing credits. We have one API, and we’ll need to create another API. This would also mean our current deployment would need to revise its existing HTML keeping one Active Widget, instead of 2. After that, we’ll need to rename ValPr Widget, then combined the 2 chart.js into one chart.js with right y-axis.
// FWM_Categories //
We’ll need to separate the ValPr Widgets and Categories Widget with its own API.
Once we update the design for ValPr, we’ll test to see which Widget would better off keeping the initial API and which Widget will have a new API. In addition, we’ll test with first week of OCT26 financials.
// FWM_Super //
Test Deploy is successfully implemented.
// Deploying Widgets //
We’ll hold off on publishing until we test first week of OCT26 financials, and whether or not we have sufficient deploy credits, otherwise will be a NOV26 event.
// Widgets //
FWM_ValPr
FWM_Categories
FWM_Super
TBD
