Phone call with Shari O. going over questions on merchant processing and custom email accounts. We really need a better or tighter company structure. Certain things are falling through the cracks. Sent an email out to Wayne, Cory, and Shari O. with information regarding the custom email addresses and accounts.

Working with Bryan. We looked at some code and made a few tweaks to some of his reports and pages. We then switched gears over to sub inventory with location filters. Once you add locations into the mix, it complicates things. It goes from a one-to-one relation to a one-to-many relation. That then requires grouping, dynamic filters, and dealing with scale. Lots of talk about dynamics, deeper groupings, and how to sub filter grouped results. We also talked about getting good data and small control set to make sure we are getting what we want (known data in order to get known output).

Working with Cory on projects. Went over some upcoming projects. Things like a redo on the quick clock in/outs, stacked taxes, some black box code for a client, bulk tools on expiring loyalty points, data imports, and some changes on merchant processing for a client.

For the record, the stacked taxes are a client request, and we don't currently have anything that does that. A stacked tax takes a subtotal and runs a tax on that value (normal). It then takes that new value or subtotal plus the first tax and then taxes that. That process (stacking) could be done a number of times. We have never done that and are checking about the liability and legality of even offering that type of a option.

We do a lot of back calculations on taxes and do what we call "with tax included" or out the door pricing but this other one is a new request.

Emails and recording notes.

Working with Bryan on layout and style guide stuff. Code sign-off, merged, and pushed up some code. As we were working, I noticed a few things that we could do better on...

- We need to make sure that we don't have polluted data, especially on the testing and demo sites. We use them for so many different things and don't finish all of the processes. We end up with polluted data or incorrect data.

- We need more histories on things like sub inventory, parent attributes, corp-wide settings, and other high-level places. We have tons of histories on invoices, customers, deposits, parts/items, etc. We just need to add those other histories to the list. This would be a good thing for the fracture project.

- If we have a big mess, say in a demo site, and it needs to be changed - it sure would be nice if we had some bulk clean-up tools or system admin tools that were super high level but could help clean-up or change data in bulk. We may not want these tools available for normal users (could be a problem).

- Full visibility and full searchability - everything needs search options, exports, reports, and histories.

After Bryan and I finished up on some of the code sign-off and reports that we were working on, we switched gears and started talking about some location-based grouping of data. We ran out of time, but I gave him some small things that will help, and he was going to go in and play with those suggestions.

Working with Alan on ship B, fracture, and adilas lite stuff. We were reporting on what we have been doing and who is doing what. Alan has been digging in deeper and checking out ColdBox, CommandBox, React, VueJS (vue), and other code frameworks. I took a few screenshots of his notes (see attached). Here are some other topics that we talked about:

- We would like to organize the features that we want to include and build out. Still on the wish list - to get this done and all organized

- Code style guides

- Features of CommandBox and ColdBox - products by Ortus Solutions - automation with Git (code repository stuff), sanitizing, formatting, and standardizing data and code.

- Alan is leaning towards VueJS vs React JS. We went over some pros and cons.

- Our current choice or pick for our tech stack is looking something like this: CommandBox, ColdBox, Lucee/ColdFusion, MSQL, Bootstrap 5, and VueJS.

- Lots of talk about routing, events, handlers, and MVC layers and levels (MVC = model view controller framework or methodology).

- Integrated testing for integration test and unit testing.

- Custom layouts

- Lots of white labeling options and data driven design and data driven settings.

- Nesting or sub architecture and modules - inheriting different things

- Little baby apps or configurable widgets

- Building out prototypes and playing with concepts, ideas, and options

- Layers and everything going through API sockets or API endpoints

- We would love to get into drag and drop widgets and options to create your own layouts. This would allow for either preset widgets or mini widgets that could be places, configured, and added to dashboards as needed. Super cool!

- Use of popup modals and one-pager type interfaces.

- We want tons of asynchronous type actions and transactions. Certain things need to flow step by step, but other things can be done asynchronously.

- To start out with, maybe a light mode and dark mode, to keep it simple. We may add more other custom look and feel options later on.

- Doing wireframes and then rolling over to actual mock-ups.

- We would like to look at some of our past R&D options from Jonathan Wells (designer and prototype guy).

Paying bills, updating my Adobe XD install to the newest version, and looking around on some older XD documents from Jonathan Wells. On a phone call with Steve to go over where we are both at on different projects and light catch-up. Reding notes on an XD document from Jonathan. He was really good at summing things up.

Looking over some older XD files from Jonathan Wells. I got into a couple of them and created two new small micro videos from the older mock-ups.

First round - Sample of getting into a demo site from the adilas cafe - Length 00:01:13

Second round - Sample navigation on the adilas cafe - Length 00:02:33