Just wanted to record a few more notes from or for the fracture project (adilas lite).

- Make a fun flyer and do some news and updates to show what we are doing.

- Make the plan at the 10,000 foot elevation first. This is pretty general and doesn't have any deep details. It's the overview level.

- Allow for both preset packages (sizes or configurations) and a la carte, pick and choose, features and functions for what people (our clients) can purchase.

- Training and maintenance need to be part of the plan. Those are two critical pieces that need to be part of the bigger picture.

- Recruit help - allow for all kinds of investment - time, money, ideas, networking, connections, sales, etc.

- Offer help to make an industry-specific skin. This could include personal visits to those companies. Get out among our clients and customers. Going along with industry-specific skins, this could be a master list of on/off switches, naming conventions, flow and processes, and other normal industry-specific things and needs.

- Going along with industry-specific skins, I really want to help people build their own virtual or real white labels (using and configuring our product as their own). We need to advertise this and encourage it. We could even offer to come visit them or their facilities to figure out an arrangement to help them build their dreams. Focus on what they want. Once we have the main core, the other parts and pieces shouldn't be that tough or hard (in theory).

- Don't be afraid to travel, as needed.

- Family history - I don't know how this fits in, but I was thinking about it. I'm not sure if we should build things out to allow digital journaling (similar to the developer's notebook or quick list of entries), tracking family history, or what. I was just thinking about it, so I thought that I would record the idea. Once again, I'm not sure how this plays in.

Zoom session with Kelly and Cory and Steve. We were looking at a cross corp data issue. Light clean-up on some backend database stuff for both Kelly and Cory. Jumped back on with Kelly, Cory, and John to look at a sales tax calculation issue. It was dealing with how the shopping cart figured out taxes based on customer types (including and excluding calculations). After the meeting, Cory and I chatted about other projects on the to do list.

Small side note, it was amazing watching Kelly navigate around with multiple tabs, quick search options, exports, pulling reports, and bouncing from page to page to get the data. We need to remember how hard some of these pages and functions get pushed on when we build out fracture. We need something that is stable enough to hold up the power users.

Meeting with John. Working on the SWOT analysis stuff. We were still working through some of the opportunities. At some point, I'd like to copy and paste some of that info into the developer's notebook. Some great stuff. Along with our meeting, we decided to shoot for a new group meeting on June 18th from 5-6 pm. This would be a team meeting for ship B and progress on where we are at.

As a note, I was thinking about the developer's notebook and other web based journals and blogs. I use it all the time. I'd really like to offer something like that for all of our customers. Maybe a possible addition and option for fracture or adilas lite.

Meeting with Alan and Aspen. Alan and I were talking about the pressures of getting all of the prototypes and new learning done that is needed. It's too much. You can feel the burnout starting to set in and that affects everything else. So crazy how quick it can set in.

We are trying to start organizing things. We feel like we have some great ideas, direction, and what not. It's all over the place, so our next major task is to start organizing things. Along those lines, we may have to find some middle ground. We know what we have (old or existing) and we have an idea of what we want (new and future). We may need a few steps in between instead of just jumping from old to new. That's a big jump.

We have tons of other notes that we were working on. See attached. We were looking into ideas about mission statements, plans, pros and cons of different technology stacks, as well as other general topics and discussions. The new notes are towards the bottom of the document.

Emails and watching videos from Bryan on scheduling and projects that have been released. See below for some links:

Ecommerce Rentals - 7 minutes

Ecommerce Unique Events - 4.5 minutes

Ecommerce Reoccurring Events - 5 minutes

Internal Employee Scheduling - 4 minutes

Just for fun, quote of the day - "And that's how it's done!" - Bryan Dayton

Looking at the developer's notebook summary. Trying to make the summary faster. It was taking quite a bit of time to display a summary of over 10,000+ entries. I ended up changing the SQL (database query stuff) and let the database format the dates on the fly vs trying to format the dates and run counts between start and end dates. It got way quicker. That's awesome!

Printing out elements of time (recorded notes from the developer's notebook) from September of 2016 up to March of 2017. Trying to get a back-up copy of some of the notes. Printer was having issues with one of the toner cartridges.

I was using this link to get the element of time - temp/print_elements_of_time.cfm

Started looking into TechSmith's Camtasia Studio for screen captures and video recording.

Decided to buy a copy of TechSmith's Camtasia Studio and TechSmith's SnagIt for screen captures. Going over videos on visual communications and ways to share information via graphics and visuals. Watched a number of videos, trying to get some skills on SnagIt.

To do list stuff. Emails, text messages, buying laser printer toner, etc. Small rework of the business zipper site. Used SnagIt to help with the images (setting a standard size). Re-pushed up code and new images. More emails.

Recording notes. More notes on the virtual obstacle course (using customers as the theme for the obstacle course). See elements of time # 10294 for more info. Also, recording notes for 6/30/23 and 7/2/23.

- Small review of what we have been working on

- Planning out the joint meeting on July 18 for the ship B - fracture and adilas lite team

- We spent a ton of time working on some other notes and brainstorming. See attached.

- We talked about using some of the graphics that show the mix of functions and players. See element of time 4989 for an idea of what we are talking about.

Went into Logan to meet with Aaron Hill. We went biking (off the clock) and then came back to his office and did a two-hour consulting session. As part of our session, I gave Aaron a small demo on what adilas can do. See attached for some notes.

- Aaron is able to help with the consulting and seeing things from the outside.

- I can't get bogged down in doing the smaller or bigger tasks. My current role is to help get the vision out there and get it all going.

- We'll meet every couple of weeks to report on progress.

- Investors are looking for the full package and lots of potential.

- The (this) education piece is huge.

- We need to keep someone on staff that has their thumb on education and knows what is going on there. It's a vital piece of the puzzle.

- We could start with some of our older stuff. Instead of reinventing the wheel, we could use some of the older training stuff and use that to train the trainers. We have tons of assets, either on our older YouTube channel or Brandon has the raw recordings on some external hard drives that we used when we were doing the original trainings. We just need someone who is willing to get in there and pull out or break out those pieces and/or gems. It's a big project. Not sure on the numbers, but I'll bet that it could be somewhere between $10-20K (ten to twenty thousand dollars). It's worth a lot.

- For me, check to see if Sean or Danny would like to help with this education project and virtually bank some hours (work with the idea of a later payoff).

- Task, find that person. Who will help and run with the education side of this thing?

Meeting with Bryan to push up 3 different code branches. Light refinements on some of the reports and pages. We worked on PO's, sub inventory, alternate logos for invoices, quotes, and statements. We also did some PDF export stuff and more sub inventory availability options on some of the reports. Pushed up code to specific servers for testing.

Meeting with Alan. Going over and reviewing my meeting this morning with Aaron and what we are learning and discovering. Alan was showing us (Aspen and I) some VueJS stuff (JavaScript framework). Lots of shortcuts. Mini caching of variables. Listeners and watchers. Two-way passing back and forth. Comparing VueJS to React JS stuff. Event handling and looking into options.

We switched gears and went over needs for training and outside training resources. We did some review of some older R&D stuff from Jonathan Wells. We talked about some new user's stories. I got some notes from Alan (see attached). Light ideas of what Alan wants to do with adilas lite and fracture. We then rolled into a small work session doing stuff with the jelly fish model. See elements of time # 2284 inside of adilas for verbiage there.

Paying bills and recording notes for work done on ship A (paid work).

Recording notes from 7/3/23 and 7/4/23. Adding in counters on the summary page for web visible elements of time (developer's notebook entries).

Multiple sessions. Working on the additional vehicle assignments for customers. Had to do some light research on a new horizontal form layout. Had to add some custom CSS and look in the project theme for some ideas. Built out the form and started working on the action page.

Meeting with Wayne over the GoToMeeting session. Wayne and I were going over the main login information and process. We looked at the auto login for the ecommerce site as well. Just gathering ideas. We talked about the adilas cafe options. Wayne is getting close to having some of that code done at a super entry level. He is going to work with John to get a small skin and good-looking interface put on it. Lastly, Wayne and I chatted about his brother and some possible involvement from there.

Meeting with Cory. She had a question about using the find and replace functionality for a client. We actually did the find and replace and it worked slick. It did a deep flip flop and full find and replace including histories, line items, sub inventory, etc.

Next, we spent some time looking at some data questions. Looking into a payment search question and then into employee timecards and timeclocks. We used some existing tools and also did some queries behind the scenes to look at raw data.

On the phone with Bryan to go over tables, joins, and options for pulling in sub inventory. It can get pretty deep, if you are starting from an existing query or even a brand new query.

Lunch meeting with Jonathan Johnson from Epic Enterprises. Jonathan is a business consultant here locally in the Cache Valley, Utah area. Great little meeting and he was asking some great questions and feelers to check out parts and pieces of my plan for ship B, fracture, or adilas lite. We talked about pieces of the business plan and how to plan things out and proceed.

- One of the main topics was dealing with talent and getting excellent talent to help run the business.

- Went over our rough plan and talked through steps of the plan. See elements of time # 10179 for more details.

1. Company Structure - Adilas Jelly Fish Model
2. Product Development - Adilas Value Add-On Core Model
3. Education & Training - Internal and External - Adilas University
4. Community & Outside 3rd Party Solutions - Adilas Marketplace
5. Social & Efficiency Options - Adilas Cafe & Community
6. Deeper Product Development - Adilas Lite - Fracture Project
7. Budgets, Finances, Marketing, & Sales - Other Business Plans

- Lots of talk about division, departments, and managing the entity and the projects. Defining those roles and what is needed. Once that is finished, we will put or assign/invite the who (people and talent) to the what.

- We talked a lot about inviting and enticing the talent. Not all of the talent will be hourly or employee level people. Some of the talent or high-end knowledge workers contribute in different ways. That was a small paradigm shift for me, thinking wise. More of projects and contributions vs hours and physical output.

- What needs to be done for the product development pieces - plans, marketing, sales, and roll outs.

- Talking about building out a pitch deck to help pitch the project and product (the whole package).

- 5 main personality types - There are five major roles that need to be fulfilled in a company. Instead of just roles, ideally, you actually have people in place who can carry each of these roles and own it. Otherwise, you just have a smaller number wearing multiple hats. The five people are: An organizer, a doer, a creative type, a consultant, and a salesman. The goal is to align talents with tasks. I grabbed this bullet point from entry # 5295 - another meeting with Jonathan Johnson (early on, back in 2019).

- Talking about the root words in authority (author or create), accountability (count or manage), and responsibility (respond or react). Who does what and how that all plays into the mix.

- See attached for a napkin with some notes on it - Here is what Jonathan wanted me to do - 4 steps he wants me to work on... 1. Define the division and structure of the company, 2. Invite the talent to fill the roles defined, 3. Product development MVP, and 4. Build the pitch deck. All of these need to be at least good enough. Shooting for an MVP level on all of them.

Meeting with Alan on defining roles and responsibilities for parts of the adilas jelly fish model. See element of time # 2284 inside of adilas for details. Not finished yet but some great discussions.

Master Adilas Plan - Jellyfish Model

- The adilas jellyfish model - covers almost all of the departments and sub sections of what we are trying to be as a company. It is not the main product, but more of our internal and external departments, areas, and general areas that we will keep refining and working on.

- Possible numbers for the jellyfish model. Going from top to bottom and from left to right.
1. adilas.biz
2. Admin
3. Monthly Reoccurring Service
4. Sales & Marketing
5. Setup & Training
6. Tech Support
7. Design
8. Custom Code
9. Consulting
10. R&D
11. Project Management
12. Internal Development & Maintenance
13. Adilas University
14. Adilas Marketplace
15. Adilas Cafe & Community - Adilas World
16. Databases, Networks, Servers, & IT

Tons more details and bullet points on element of time # 2284 inside of adilas.

Emails and tech support for ship A and merchant processing options.

Eric and I were looking at the auto deposit gift card payments update. Merged and pushed up new code. Ran the update on all servers. The new code will handle all auto deposits going forward.

Working with John. Helping him debug the cart to work with his discount engine. Light review of adilas financials.

Recording notes from yesterday and today (7/10/23 to 7/11/23).

Meeting with John to go over the SWOT analysis. Lots of talk about consistency and product feedback. Working on the opportunities section. Great conversations. At some point, I'd like to copy and paste some of those notes to make them more visible.

Planning with Aspen. Doing some brain mapping on a huge board with post-it notes. See attached for some pictures. Lots of high-level planning for adilas lite, fracture, and sub projects within our bigger vision. Once again, see attached. We also got Aspen paid for her work.

Quick breakdown of the different projects:

#1 - Company Structure - Jellyfish Model - Knowlege workers vs hourly workers, define divisions, departments, the who (talent), combine areas as needed, optimize structure, overtime, and compensation. We also want to deal with the different personality types - organizer, doer, creative, consultant, and the salesperson (someone who does sales).

#2 - Product Development - Value Add-On Core - Players, features, each summarized (possibly in a video or multiple videos). Define the current core. Figure out industry specific skins. White labeling options. On the industry specific skins, go minimal for the start. Custom code - data driven, not code driven. BI (business intelligence) level - Model needs to be fully planned out because it doesn't exist as a standalone layer at this time. It is built into the system as a whole. We need to extract those pieces and make a better plan for those numbers, values, and pieces of BI. Enterprise - define it and prep the database to make the jump eventually.

#3 - Education and Training - Adilas University - Internal and external training needs - video clips, organize them (library of sorts), tracking education, SOP's (standard operating procedures) per industry, in general, and company specific options. Make all of this data driven. Easier interactions, easier interface, all dealing with settings (show/hide, rename, aliases, sort order, defaults, etc.). Once again, both internal and external training needs. Online and in person trainings. Minimize the need for education by building out a better interface (fracture and adilas lite). Dynamic content and settings. Program education directly into the interface. Be able to turn the education mode or help mode on/off based on needs and per person.

#4 - Community and 3rd Party Solutions - Adilas Marketplace - Access from the adilas cafe or as a standalone app. Adilas creates tons of byproducts (both products and services). This could be things like consulting, design, custom code, data entry, bank reconciliation, accounting needs, etc. We want to offer ways to both buy and sell both products and services through a controlled interface. Think of a mini Amazon or mini eBay type marketplace. We need a spot to send, organize, and direct 3rd party solutions. Advertising and marketing efforts. More white labeling options (in the marketplace). This section could be further explored and has lots of potential.

#5 - Social and Efficiency Options - Adilas Cafe & Community - White labeling, standardized portal, single login, single sign on, able to jump to any corporation on any server where permissions have been granted. Options for work, play, buy, sell, train, social, and participate. User profile page. Interface with other corporations, get assigned, hub type environment. Mini marketplace for adilas based products and services. Sales and creation of new accounts (automated setup options). Tired pricing. News and updates, this wouldn't be forced on anybody but would be more available. We could allow them to customize their news and update feed. Dynamic billing and making payments for our (adilas) clients.

#6 - Deeper Product Development - Adilas Lite or Fracture - Customize everything. Setup wizard, question to help with setup, industry specific settings and presets, sizes, features, and options to customize as needed. Show/hide almost everything. Other settings such as toggle on/off features, columns, reports, navigation, etc. Everything is configurable to some extent. Sort orders and the ability to move things around (vertically, horizontally, and free form). Settings and making all of these decisions data driven.

Inside of fracture (code name before we got adilas lite) we want to make some server changes, code changes, frontend and backend changes by using frameworks and different languages (code stuff). Entirely composed of API sockets. This will make everything more portable and will also allow other outside developers options to build custom pages, features, and interfaces. Another advantage of using the API sockets for everything, it will standardize how everybody interfaces and interacts with the system or application. It will also let other developers play along without letting them see the underlying code. They just see documentation, examples, and final output from the API socket calls or API endpoints.

Fracture will include testing plans, sections for unit testing, integration testing, automated tests, and good coverage on testing in general. Everything will be modularized and broken into smaller mini components. We plan on using dynamic billing for usage, features, storage, etc. Entirely new interface with the ability to setup your own navigation and your own dashboards. We want lots of white labels and white labeling options. Tons of industry specific stuff as well.

Be able to turn on/off the education mode. We would love to capitalize on numerous lessons learned from 20+ years in the business. Lots of prototyping, new databases with good indexing and normalization. Directly program in teasers and marking. There has even been some talk of using AI (artificial intelligence) to help with suggestions for products and features that they might use or want.

Everything will be mobile ready and responsive. Client-side and server-side validation. We also want to prep things and have a maintenance plan in place as well. That is something that has been somewhat missing from past versions. Basically, take what we have and build from there - learning from the past and building for the future. Everything has a life cycle, prep for the next phase or part of that life cycle.

#7 - Budgets, Finances, Marketing, & Sales - Other business plans - interactive wireframing presentations, SWOT analysis, funding and repayment stuff, timelines, mission statement, profit sharing, budgets per section, per person, per product/feature. Writing business proposals, project scopes, sales pitches, standardization, and master table of contents. Lots of good marketing and campaigns for sales. Sources of profit and ROI (return on investment). Prototyping, testing, and market research.

#8 - Other - Networking and meetings as well as more research. Get in there and get it done!

Emails and tech support for High Valley Bike Shuttle for Drew, dealing with online scheduling. Light research on some of his settings and what not. Sent out an email to everybody about an update meeting for adilas lite or fracture.

Emails and printing off text copies of elements of time as a back-up.

Meeting with Cory on projects. Going over needs for new uploads, FlyHi API integration, and options to explore with Datacap. Cory wants me to help populate a sandbox with some data for the FlyHi guys. That way they can use that site as a demo for their product and integration. Getting some feedback from Cory on some of the forms and layouts that I'm working on.

Meeting with Eric to go over a time zone offset fix for a client. After we got that done, we switched over to a different project. We were talking about changes in the aggregates based on the line status values. Finding all of the places where things change (at the system or database level). Going over database trigger code and updates.

Emails and printing out paper back-up copies of elements of time for entries back in 2018.

Planning meeting with Alan. Light review and updates from each other. Working on the adilas jellyfish model. We came up with a mini jellyfish model. See element of time # 2284 inside of adilas. Working on an agenda and planning what we wanted to do for the group meeting to show progress. Talking about talent.

Emails and doing paper back-ups for elements of time in the shop. Basically, printing developer's notebook entries.

Emails and temp recording notes inside of adilas (had to get paid but didn't have all of the full entries done). Working on the agenda for the group meeting tonight. In between the different tasks, I was printing out paper copies of bulk elements of time.

SWOT analysis stuff with John. Working on the threats section. What are we going to do to fix some of these things? Wayne jumped on and reported on possible move to Spain (nothing adilas related, just chatting about life). Wayne was talking about cyberchef tools and security options. We talked about some advanced cyber stuff. High level mash-ups and dashboards. We also talked about professional level certifications. One of things that we get faced with, as developers, is stagnation of skills. We need to keep building on our skills and skillsets. Talking about serving others. John and I jumped back into the SWOT analysis and going the threats. Distractions, time to market, lack of funding, lack of structure, etc. Lots of great conversations.

Meeting with Alan and going over the agenda. Light look at the SWOT analysis and making plans. Alan was going to build out a quick PowerPoint slide show for tonight.

Printing out some elements of time as a back-up paper copy. Prep for a group meeting. Once the meeting started, we did some small intros. There were 10 of us on the meeting. We went over concepts of throwing stuff at the wall, seeing what sticks, organizing things, Alan gave a small PowerPoint presentation (see attached). We talked about exposing the peaks, mountains and ice berg (peaks) analogy, tiered versions, pricing matrix, features & who has access, prototyping with code models, frameworks, libraries, the jelly fish model, a new mini jelly fish model, and tons of other topics.

We got into topics of growth, retention, code development, IT/Servers, and Cafe/Marketplace options. Great discussion on R&D and how R&D plays on both the maintenance side (stabilizing and making the current product better) and the growth side (new stuff and pioneering).

Spent some time talking about the SWOT analysis, lessons learned, and mission statements. This is an idea from Hamid, on the mission statement - Mission: Adilas - Build Your Solutions. We got into some user stories, scenarios, and recruiting help from the guys/gals. We talked about who wants to help and what they could do. Overall, a good meeting. We recorded it, at least the first part (first 23 minutes). It stopped recording when we switched screens and switched presenters. Anyways, see attached for some other notes, the PowerPoint slides, and the link to the video recording.

Good group meeting with a progress report on the ship B, adilas lite stuff, and fracture.

Recording notes from the group meeting tonight. Uploaded the PowerPoint presentation, the video recording, and added some other notes and what not. See elements of time # 10329 for details.

Emails and flipping time templates for Sean. Replying to emails about a possible speaking engagement. Other emails. Hopped on with Bryan to look at a sort issue for a report.

Phone call with Eric going over database triggers, inventory snapshots, and aggregates. Those are all projects that Eric has been working on in the past few months. Light overview and touching base on where things are at. I'd say we have 75-90% done on all of them.

Digital storytelling research. Printing things out, reading, highlighting, and reviewing a number of different articles that I (we - Shannon and I) have written on the subject. Fun research project. I really enjoyed it, the deeper I went, the more everything was making sense.

Back on the research stuff for the digital storytelling talk. Reviewing some older docs and our old website. Talking lots of notes on paper.

If you want to see the notes, I put a copy of them on element of time # 10355 on 7/26/23.

Data import for a client. Combing data and reading through the upload file (code). Prep work and looking up id numbers.

Back on the data import for a client. Lots of combing and prepping the data. Doing the uploads and converting files to smaller CSV files. Over 2,400+ items with various parent attributes.

Emails and texts back and forth to John about the adilas cafe. Working with a document for Danny and YouTube training videos. I then met with Danny and we went over options for some of the videos and training assets that we both have and/or need. Danny and I were talking about things, and he was saying that he knows a company that doesn't even release the next changes until the training is ready, done, and up for viewing. See attached for a screencap of what we were talking about.

Here a couple of the links that I sent to Danny:

- Entries in the developer's notebook talking about YouTube videos - lots of good resources. Once it comes up, do a browser search for the term "YouTube" to help pinpoint some of the options.

- Entry in the developer's notebook talking about a thing called education mode.

As a side note, on 8/14/23, I added this little link to a video on the education mode.

Data import for a sandbox site. Copying vendors and part categories between corporations. Combing data and doing some prep work.

Phone call with Shari O. and fixing a stock/unit problem for I-35 Trailers out of Texas. ended up bouncing around and we altered some database records behind the scenes. It appears to have fixed all of the issues. Somehow, they were using a model id number that was tied to a non-trailer inventory type. Not sure how that happened.

Reading and making comments on some research that Danny was working on. Research on YouTube channels, videos, using blogs, etc. See attached for some screenshots of Danny's research. Watched a small movie from Bryan on his homemade time clock app and project management tool.

Here are a couple of links that I sent to Danny:

- List of over 13,000+ blog entries from the developer's notebook inside of adilas.

- Idea to reuse some of our existing content in a number of different spots or other outside blogs.

Lunch meeting with Alan. He was in town so we hooked up for lunch and to chat. Planning, talking about our team, roles, strengths and weaknesses, and industry specific skins. We talked about the jelly fish model, the value add-on core model, adilas university, adilas marketplace, and fracture (adilas lite) stuff. Fun little meeting. Both Alan and I are on the same page as far as vision. That's awesome!

Multiple different sessions working on ship A stuff. Recording times inside of adilas. Working on the sandbox upload for parent attributes for a client. Uploading the data and pushing up the parent attributes for the sandbox site.

Emails, research, and prep work on some digital storytelling talk outline stuff for an upcoming conference. As I was doing some of the research, we have a concept that we call "roll call accounting". It seems like AI accounting is another name or synonymous term with roll call accounting. Basically, asking the data questions based on dates, flags, checkpoints, states, and status. Fun little insight.

Great phone call with Steve. We were talking about what was going on with both ship A and ship B stuff. Steve recommended that we build a report to show what hours are being worked on ship B, per month, to help everybody see what is going on. Great idea.

We talked about working with some of our clients and offering free setup and training to get them up and going. Sometimes things don't start without a little push in the right direction. We also talked about AI (artificial intelligence) stuff. I'm going to look at some domain names to help with AI accounting. We chatted about some funding ideas and options. Great little call.

Cory and I on a Zoom meeting. Setting priorities and such. Talking about sub permissions, doing some light quoting on projects, and talking about 3rd party solutions. As part of the conversation, we ended up talking about API sockets and keeping things on different channels. We have at least four channels right now. They are the demo channel, the adilas universe level, the public channel, and the 3rd party solution channel.

After the meeting, I was doing some checking on some new domain names that Steve and I were talking about.

Code review with Bryan. Working on the advanced PO search and the advanced part/item searches. Fixed a merge conflict, pushed up code, and merged in a couple of small branches of code.

Talking with John about the adilas cafe and doing some mock-ups on that interface. We went over some of the older stuff from Jonathan Wells, see entry from back in 9/5/19 for more info. We went over some new mock-ups from John (see attached). After that, we spent the rest of the time going over the SWOT analysis. Today we were finishing up the threats section. See attached for some progress stuff. It is still rough and unfinished, but we are making great progress.

We also got into talking about budgets, making sure that we go mobile first for fracture (adilas lite), and we setup some other times to meet. We are excited to have the first pass done on the SWOT analysis (see attached).

Going over my notes. Talking with John earlier and we were talking about mobile first design and responsive web app. That has to be a required or a requirement for fracture and adilas lite. We want every page to be able to do both mobile and desktop. I added a post-it note to my board and took a new picture. See attached.

Reaching out to a client to setup a meeting and time to chat about requested changes.

Phone call with Sean about credit cards and rentals. We talked about new possible authorize.net API sockets and endpoints for holding customer payment information on the authorize.net site. We don't want any of that data (credit card stuff) on our servers. That gets into PCI compliance and makes a juicy target. We'll ship it all off or over to the gateway for storage. That's the best way.

Going over the adilas core concepts document. Prep for a talk on digital storytelling.

Reviewing notes for the Bear 100 changes that have been requested. Reading some notes from the Bear 100 race director. Quick phone call to touch base and go over the email. Cody did a great job summarizing things and listing out priorities. That is awesome!

Reading over some market research that Danny did for online accounting software packages. Good stuff.

Phone call with Sean to go over some custom code for charging a special credit card fee once an invoice goes over a certain amount. Spent time looking around to see if had anything like that. I found some similar stuff but noting exactly like that. Built out the page, did some testing, and pushed it up to the server. This special code is for a trailer dealership that does a lot of trailer rentals. They like to pass on the credit card processing fee to the clients. Anyways, the new code is up and live. Custom black box stuff on data 11 for corp 1501.

Recording notes from 7/24/23 to 7/25/23.

Recording notes. More prep for the digital storytelling talk for a conference. Getting to the heart of things - tracking objects and data over time. I've got to get this out to the world. I love it and I think that it could/would really help others who are exploring these concepts. Currently, this is our vision, but I'd love for other to catch ahold and run with the vision as well. Alone and in the dark, it will die without light and usage.

As I was reading though some of the documents and underlining things and marking things up, I kept thinking about Shannon (my sister) and all of her help. I'm so grateful for Shannon's help on getting some of this stuff prepped and put into writing. It doesn't do others any good if it is just stuck in my head.

It may be quite a bit, but I'd like to upload all of my notes, scans, and docs that I am working on. I've learned a ton by going over these things.

Small note added on 7/27/23 - If you want, here is a link to my notes. There are 40+ scanned pages of notes and brainstorming.

Title: Exploring Digital Storytelling - Benefits of going beyond the data

Description: Everything has a story to tell. What if you could help your data start talking back to you (nicely)? Wouldn't that be awesome! Imagine asking something like this: What's your story? Who created you? Where have you been? Where are you headed? Who are your buddies? Where do you belong? When did you finish? In this session, we will be exploring the 12 core concepts of digital storytelling. We'll discuss real world examples of how using these concepts can bring life, depth, and value to your data, apps, systems, and platforms.

Outline:

Here are the 12 core concepts of digital storytelling:

1. Capture & Record The Story
2. Groups, Players, Individuals, & Characters
3. Relationships
4. Trouble, Problems, Pain, Needs, & Goals
5. Decisions & Choices
6. Consequences (cause & effect)
7. Accountability
8. Permissions & Settings
9. Systems
10. Vision & Future Developments
11. Tech, Tools, & Maintenance
12. Tracking Objects & Data Over Time

Other things that I would like to cover:

• Systems thinking approach
• Success isn't a destination, it's a journey!
• Finding success along the way
• Everything has a story to tell
• All the W's - who, what, where, when, why, wHow :) - just being funny!
• World building
• Digital assembly line concepts
• Tying everything into the 12 core concepts of digital storytelling

References:

I've been studying and using some of these concepts for years. See attached for some of my notes. In my notes, I took pages and pages and boiled them down into a smaller list of key points. Each main point is numbered and underlined. For reference, the numbers look like this: #2.8 or #4.5, depending on which document the idea or point comes from. I may refine it further, but this is the rough draft.

Below are the links to the original docs in digital form (no mark-up, no numbers, no underlining on the originals).

Number #1 - Submission to speak at an Adobe ColdFusion conference - link

Numbers #2.0-#2.13 - Text from the business zipper website on the about us page - link

Numbers #3.1-#3.17 - Text from the old adilas.biz website. You may have to scroll down to see the text. - link

Numbers #4.1-#4.51 - Core concept document - taken from the adilas archives - still partially unfinished - link

We had a request from a client to add in some client-side validation to our forms and pages. They submit things and then get an error, when they click the back button, the form has removed their work and they have to do it again. That's the browser that does that, but we could help by having client-side validation to help prompt them even before they submit the page or the form. We really want full coverage of this (client-side validation and server-side validation) for the upcoming fracture or adilas lite project.

Sean got ahold of me and needed his custom credit card fee, that we did for a trailer rental client, to show up at the end of the invoice. The code adds the fee whenever the invoice or cart goes past a certain amount. Because it was just in memory (in the cart), it was hard to control where it would show up. It was just another line item. Anyways, we added some code that when it gets submitted and changes from the cart (memory) into a real invoice, we just flip that line and change the sort number to a higher value, making it show up later or at the bottom of the invoice. Small little tweak.

Added another quick black box page that alters the invoice and changes the line item sort value. Pushed up the new code.

Multiple sessions. Organizing my notes on digital storytelling into blocks. Tallying which core concept each note or sub note was tied to. I've been working on this prep work for a conference talk that I may be giving. I've been on and off this project for a few days now. Here is a link to element of time # 10355 to see all of the notes, scans, brainstorming, and organizing that I was trying to do. Fun little project.

Meeting with Bryan. We were working on some planning for the next level of online scheduling. We went over a few things that we are learning on rentals. Sean is onsite this week in Texas with a trailer rental store. We had to figure out some things with saving credit cards per person, incase other payments were needed the card was no longer present. We also had some funky special credit card fees that the client wanted to pass on to their customer. We then had to tweak that special fee to make it show up at the very bottom of the invoice line items, even if it was added in between other line items. Anyways, small review of what we are learning.

Bryan and I then shifted gears and went into our own prep stuff for online scheduling of appointments. We went over some of our ideas for the web availability and calendar layers that we had talked about previously. We did a bunch of drawing and planning for the next phase. Bryan asked me to record a small video. We used a different tool and we only got my side of the audio. That's my bad. Anyways, we did a quick 16 minute clip.

After that, we spent a little bit of time time talking about Bryan project management and timeclock tools. He is looking at ways of recording sub times in one corp and being able to auto add those same timeclock records to other corporations (where permissions were assigned). We talked about some time id matching and storing those cross-corp mappings. Light back and forth. Good meeting.

Recording notes form yesterday and today (7/26 to 7/27). I feel like I'm always behind.

Working on a title, small description, and outline for a possible talk for a conference. Sent an email out with details and a small proposal. See elements of time # 10355 for more information. The subject is exploring digital storytelling - benefits of going beyond the data.

Recording notes and printing out elements of time as a back-up. My printer was struggling. Ended up working on recording notes for back on 7/5/23.

Emails and recording notes. Fixed a few small typos on different entries. Reread a few of the older entries.

Working on the Bear 100 list of changes. Adding a new leader board page, tool tips, new nav links, and some CSS changes. Looked up some documents on using Bootstrap (not very good at that yet). Added counts to the aid station button on the public runner portal.

working on the Bear 100 mobile app. Added in some new code that Chuck sent to me for the top runners. Working on layout, logic, and making the page dynamic. Chuck's code was static (hardcoded - prep stuff). I was adding real data to it. See attached for a couple of screenshots. Sent an email to the race director to show him progress.

Meeting with Cory on projects. She had a pretty long list for today. Lots of different topics. We talked about clients and requests for more settings for printing invoices, being able to share item photos between corps by reference (new request), API socket feeds for outside websites, merchant processing needs such as tips, new hardware, customer tokens, saving card data for non-card present transactions, and which gateways to connect to. We spent some time talking about how hopefully an integration with DataCap could help some of those things (stopping all of the one-to-many maintenance requirements).

Another big topic for the day was what we were calling stacked taxes. I've never seen this before. This was basically, do a sub total, tax it one way, then subtotal all of the previous taxes and items and then tax that new subtotal again. Here's the kicker... the request was for at least three levels deep (tax of a tax of a tax). I imagine that we would need to make it open, in case it got deeper. Once again, I've never seen this before. This was the first time seeing subs break into sub of subs and super smaller pieces.

Cory and I did some light quoting and figuring out how much some of these projects would cost or what they would take to get that done. Towards the end, we covered a few other topics. One was a bulk tool request for building and populating PO's by vendors and by part categories. Almost a reverse cart or reverse shopping cart way of building a PO and adding bulk items at a time. We looked into a possible bug on PO payments. We'll have to dig a little deeper on this one. Also, we added a little bit of client-side validation on the add/edit elements of time page for the main title or caption field. Busy session.

Emails, chiming in on internal projects, and recording notes from this morning.

Prep work and making a few new pages for the Bear 100 mobile app. I had made a few placeholder pages the other day. Spent some time today filling them in and mocking up what they will look like. Working on the DNF page (did not finish) and the leader board (who is winning) pages. Pushed up code to bit bucket when finished. Not quite ready to be pushed up live yet.

Online meeting with Chuck. He was helping me with some CSS stuff and some Bootstrap stuff for the Bear 100 mobile app. We did some training and Chuck helped me make a few changes. He's a good frontend guy and has skills that I don't have. Good session. Pushed up new code to the repository when we finished.