-If we watch people use the system without any other information it may help us find the holes and pitfalls. That takes quite a bit of time, but if you don't have to explain everything, it actually saves you time in the long run.
-Maybe soften some of the error messages. Help to guide and virtually hold the users hand a bit more. Show them the goal and then how to do that.

Notes About Teachers & Educators - & How They Could Use Adilas:

-This morning I have been thinking about teachers and educators. I really think adilas could be beneficial to teachers at all levels.
-I was thinking about a guy who has been helping with adilas and having him spearhead this little project. I really want to get this product out to educators and people who are teaching the next generation. It could really help them out.
-We could sell a single teacher license for $10 a month. What a benefit to the teachers at that price! We could do a whole school from $17 to $187 (whatever) based on number of teachers and students. We could do districts at a different level and even dedicated servers at another level. Tons of options.
-We could do public schools, K-12, preschools, private schools, charter schools, alternative schools, technical colleges & schools, colleges, universities, etc. No limits! Hey, even Sunday Schools... :)
-We could make a number of other interfaces that fit styles and different age groups.
-We could set a flat rate of $50/hour for custom work. That is much easier to swallow than $100/hour or higher.
-We could offer custom interfaces, custom documents, custom reports, and custom training. These are all part of the system and great potential revenue streams and profit centers.

-A CRM (Customer Relationship Management) system for teachers and students.
-Teachers could use – CRM, scheduling, photo management, documentation management per calendar event or per student, custom fields for tracking data, backend login (eCommerce) for parents, personal expense tracking, etc. Tons of options!
-We could approach schools at the state and district levels. We could approach teachers at a private or personal level. It is just a tool! They could use it at school, at home, over the summer, even while on field trips and bus rides. All they need is a hotspot or Internet connection.
-The application can be used on ipads, tablets, PC's, Mac's, phones, laptops, desktops, etc. Piece of cake and super small bandwidth and footprint.
-No contract. Month to month or annual plans. Free updates. Freedom and organization of their data.
-Cloud based, hosted solution.
-Privacy of data in multi-teacher environments.
-The power of a full business software system – catered to help teachers, educators, and students! A teacher's business is their classroom and their students. We can help with that!

Random note: I saw an interesting phrase in an email this morning... It said “disposing of digital debris”. I find that interesting as one of our current thought patterns deals with waste and being able to remove sludge and unneeded digital debris. All of nature has a way of getting rid of waste. We need to build those features in our data projects.

More notes on adilas for teachers & educators:
-School lunch program. They could pay and load cards from backend eCommerce. This is kind of like a gift card type interface or options. We could have an easy my cart favorites menu to bill out lunches and charge the cards accordingly. It could be super simple.
-Schools may need small online stores for yearbooks, t-shirts, game tickets, plays, donations, etc. This could be more eCommerce school funds cards. Pretty cool.
-Schools need email and text messaging between teachers and students and teachers and parents. We could use Full Circle IM as a 3rd party vendor for that. Piece of cake.

-Simple pricing structure of $10 per month per teacher. Any of the reps could get 20% of that as the rep and/or consultant. This same commission structure exists for all reps. This deals with accounts, not teachers (unless they are their own mini account).
Level 1 – 0 to 25 clients (accounts) – 20%
Level 2 – 26-50 clients (accounts) – 25%
Level 3 – 51-75 clients (accounts) – 30%
Level 4 – 76-100 clients (accounts) – 35%
Level 5 – Over 100 clients (accounts) – 40%

-Boy, it would be awesome to have a specific website that had teacher specific stuff on it. Ideas, tutorials, consultants, developers, manuals, and other resources. This could be really cool if they could even purchase or setup an account right from there. We could figure out referrals, promotion codes, etc. Just an idea! :)
-On schools and reports, dates are very important. We just barely added some custom date ranges to the school specific settings. This is an admin feature, but the dates could be set by school year, semesters, quarters, trimesters, year-round, etc. You get to set the active date range. All of the older data still exists, but the active date range helps to keep things current and fresh. In a way, it is like getting rid of waste and rubbish without actually towing it away.
-Objects and data wrapped in time... Think of what happens in a school year, a quarter, a semester, a trimester. What if all of that could be wrapped up together. Relationships, characters, players, problems, trouble, decisions, and consequences. Each chapter in the book (school year or timeframe) needs to play out as it happens. Catch the story at the source (teacher/student) and then go from there.
-Mini world building – a teacher, his/her students, their school, their community, their district, their region, their state, their world.

-More ideas and possible needs for an eCommerce and/or point of sale piece of software or solution... Event registration, community events and calendars, book stores, class fees, dances, housing, parking, food, labs, supplies, tuition, clubs, fund raisers, donations, extra curricular activities, field trips, exchanges, trips, etc. Tons of things, at a school, deal with money.
-This might be further down the line, but what about teaching adilas classes to students. Teach them how to run a business, sell things, track things, do accounting, even how to dream! Teach them... You dream it up, we'll help you wire it up!
-What about different accounts per students. Say they put some money on a card or an account, wouldn't it be cool if you could sub divide the money into different areas... For example: food, recreation, fees, book store, clubs, activities, etc.
-What if someone wanted to design a whole new interface that talks with an adilas backend? They could use any programming language and an adilas backend engine or API connection socket. The interface could be 100% specific to teachers and educators.
-I need to get back to my other projects... I'm having a hard time turning off the ideas... :) Good stuff and it could help great people! That's exciting!

Other notes:
-On customer logs (meaning the main customer information page), it might be nice to add all subs of time. Maybe also the invoice number of the main element of time to show what has and has not been invoiced. Then again, maybe just a link instead of showing all of the data. Or maybe wait until we do the roll call page and then link from there.

//////////////////////////

As a side note, we added a Word Document on 10/30/2019. Original date of the entry above is 9/10/2014. The new Word Document came from Chuck Swann, an adilas designer/developer. It was listing out some additional needs for schools. See this link for more info on that doc.
Web link - Word doc file

8/20/21: 2.19

6/18/21: 7.6
6/9: 22.37

5/27/21: JM=30.11

As of 5/12/21: $7031

5/12/21: JM=17.75

Internal project helping adilas developers to standardize their processes. Many hours have been spent. Actual adilas docs section and pages have been uploaded. This may be ongoing as we add little bits here and there.

As a side note, this Word doc was passed off to Chuck who started making it into a standards page for all adilas developers. This project may end up being used for internal documentation and standardization type stuff. This includes naming conventions, standard practices, code sign-off rules, expectations, CSS and style guides, etc.

Reached out to a new developer named Chuck. My brother Russell recommended that we touch base and get some talks going. We setup a meeting for next Monday afternoon. Chuck does a lot of frontend development work (working on the look and feel and user interface type aspects).

Working on the cross corp invoice to PO action page. We had an error reported that we needed to look in on. It ended up being that a part category name was being passed when it should have been a part category id number. Small fix.

Also, by way of a note, one of our tech support ladies called today and said that they are getting major pressure for the standard loyalty points and reward tracking system from Adilas. We have a number of clients that have custom rewards systems but are getting more and more demands for the standard tools to be released. Those files ,that project and/or code branch, have been turned over to me for code review but we haven't been able to get to it yet. There is definitely some heat and pressure starting to mount on that frontier.

Had an online meeting with Chuck. He is the department head for a local web/ecommerce department. He does a lot of stuff with WordPress and frontend layout. We talked a bit and went over a little bit of history. We are going to have him start helping us with some campground stuff. This is a small experiment and trying to expand into some different business verticals. We currently already have a number of campgrounds using adilas, we just want to put a little bit more icing on some of the flow and presentation. Anyways, Chuck's first assignment is to get with Russell and see if he can find out more about what we do and who we are. Basically, a small research project of sorts.

Chuck and I had a meeting to go over some progress. Chuck is a new frontend developer and is going to be helping us with graphics, layout, WordPress stuff, and other frontend development. Today, we reviewed what he has been learning and got him setup on his own new system. We set him up as an Adilas user, bridged him to Adilas, created a new world for him called Swan Haven, LLC. and setup him up in that corporation.

We did some light training and I helped him invoice me and setup some time tracking pieces in elements of time for his projects. I gave him some new assignments and he will be checking in towards the end of next week. Good start.

Met with Chuck over a GoToMeeting session. Chuck is working on some dashboards for the campground industry. He is a graphics guy and we are trying a new approach. First we are doing some graphic mock-ups and then moving into dummy data with HTML and CSS (normal web interactions). Once we get it that far, we will move to full on backend development to make it come to life. Just playing with options. Good meeting. Currently, we are just passing the initial static graphic phase.

1/10/24 Bryan Dayton sent an email to Marisa Shaw, who was originally working on this project. He was asking if she would be willing to switch over to using adilas as her RV/Campground park management tool. As a note, we were working on this project from 2019 into first part of 2020. The project got paused due to budgets and timing. This email was sent in January of 2024. Marisa emailed the following evaluation of needs for Adilas. Her response was brutally honest, but is loaded with tons of great information. See below.

To be honest, no, we would not be ready to move over. Adilas has quite a ways to go to be ready for the hospitality industry, especially for campgrounds/parks of our size. I would say if you wanted to look at your biggest competitor it would be RezExpert. That is the only software that we seriously thought about switching to but ultimately decided to stick with what we have due to price. Our only cost at this time using Campground Master is $100/year for any upgrades and customer service. 

Graphical User Interface for Campground owners.  

Link to xd share https://xd.adobe.com/view/5c903c5b-0451-4fca-5613-5ed795812d1e-2aa1/ 

We have had a number of meetings on this project, here are some other resources and meeting notes. Many of the different notes have screenshots to show the development of the project and where it is at and/or going. See below for more details.

Meeting on 10/10/19 - click to see meeting notes and screenshots - research and ideas

Meeting on 10/15/19 - click for notes and screenshots - concept art and mock-ups

Meeting on 10/29/19 - click for notes and screenshots - more mock-ups

Meeting on 10/31/19 - click for notes and screenshots - mock-ups of the revenue and expenses sections

Meeting on 11/7/19 - click for notes and screenshots - first full mock-up - multiple pages and topics

Meeting on 11/12/19 - click for notes and screenshots - full mock-up plus some mobile screenshots

Meeting on 11/19/19 - click for notes and screenshots - mock-ups for mobile

Meeting on 11/21/19 - click for notes and screenshots - more mock-ups for mobile

Meeting on 11/26/19 - click for notes and screenshots and a video of the meeting (virtual tour of the app to date) - full mock-ups and mobile mock-ups

Meeting on 12/3/19 - click for a couple of screenshots - moving from graphic concept into first round of coding.

Meeting on 12/5/19 - click for notes and screenshots - mock-ups from graphics to code

Meeting on 12/10/19 - click for notes and screenshots - more mock-ups from graphics to code

Meeting on 12/12/19 - click for notes and screenshots - code mock-ups - playing with different backgrounds

Meeting on 12/17/19 - click for notes and screenshots - code mock-ups

Meeting on 12/19/19 - click for notes and screenshots - code mock-ups and browser testing

Meeting on 1/23/20 - click for notes and screenshots - starting into the customer side - new website mock-up for WanderWays

Demo video 1/28/20 - click to view demo (youtube) - 3 minute video to showcase the product to date - marketing efforts

Meeting on 2/12/20 - click for notes and screenshots - new website almost done and interactions between designer and backend code writers

Meeting on 2/19/20 - click for notes and screenshots - new color pickers and settings for look and feel

Promo video provided by Marisa on 2/26/20 - youtube video - 3 minute promo

Meeting on 2/26/20 - click for notes and screenshots - working through settings and starting into project management

Meeting on 3/21/20 - click for notes and screenshots - Working on settings, color pickers, site admin, roles & permissions

There was a small break in the project and we had to set it by the side, dealing with funding, and availability. There were a few small meetings and progress, but nothing major to report.

Meeting on 7/22/20 - click for notes - Meeting to get the project back on track and moving forward.

Meeting on 9/2/20 - click for notes and screenshots and a new mock-up - Reporting on the customer frontend pages and application.

We had a meeting with Chuck and he was showing some new progress with the campground stuff. We are code naming it camp-adilas just for fun. That was Marisa's idea. We had Danny Shuford, Marisa Shaw, Chuck, Steve, Alan, and myself on the meeting. Steve and I were lightly distracted, due to a server issue. We had two servers down and we were part in the meeting and part trying to make sure that things were being taken care of. Interesting.

Anyways, here are some notes from our meeting.

- Visual services and access to add-on services when selling and booking a campground site

- Color coded helpers to help with states, statuses, and color coding helpers

- Be able to show available, occupied, and services available to each site

- Marisa was talking about a synced reservation and a non-synced reservation. This deals with who is booking the site. Is it grandma and grandpa who put their card down to reserve 4 different sites for their family (synced or all together) or is it just a single family booking a site (non-synced or self pay). She was saying that we need to be able to do both and allow those groups to expand, contract, and break apart if needed. All of this deals with billing and reservations.

- It is really important to be able to show just the open sites for a specific date range.

- The sites themselves need different status levels. For example: pending, confirmed, checked in, checked out, reserved, etc.

- They talked about a "do not move" lock on certain site. This deals with a state or status that keeps the person locked in for some reason. It could be VIP treatment, special needs, special group considerations, or some other circumstance.

- We need to be able to add notes to any site and/or reservation.

- Block a site through a date range. Also being able to block the same site with a possible extension date range (not for sure, but a maybe or possible extended stay).

- Lots of needs for discounts and campaign tracking. This is already built in, but we wanted to note it anyways.

- Waiting lists would be nice. Able to sort and move people around on the waiting list as needed. They even talked about different queue type options.

- Lots of color coding and legends

- Being able to move reservations from the waiting list to some other available site

- Lots of talk about treating the waiting list like a queue of sort sort. The queue would be, by default, first come first server, but it would also have ways of tweaking it based off of needs, special circumstances, and/or add-on services (being able to manually move things around if needed).

- Currently, the campgrounds are doing tons of little hand-written notes and post-it notes to keep track of things. That gets crazy as things get busier.

- Danny was talking about using the priority fields on the elements of time to help sort certain reservations and/or waiting list persons. Just an idea.

- My biggest take away from the meeting was Marisa's comment - "I can sell this!" - Chuck is making the system sellable due to the ideas of the intuitive graphical user interface and what the possibilities could be. That was my favorite comment. Good stuff. We need to make this thing sellable.

- Sent an email to both Chuck and Russell to have them look into some of the stuff that we have been doing with Jonathan Wells, the designer from Rexburg, ID area. Here is the link: Web link - developers notebook - q=meeting%20with%20jonathan

Steve and I got on a phone call to talk about options and moving forward. We got an email back from Chuck that said that he was wanting to work full time for adilas and even give his two week notice at his other job to do so. We were talking about options and how we could possibly structure our team to help make things happen and function better. We talked about markets and vertical white labels of our own product. We talked about re-skinning and re-designing some of our existing functionality to make it look custom per business vertical. We also talked about developer, designers, project managers, and reps and how each could possibly play into the mix. Super fun conversation and lots of vision and direction. I really enjoyed the call. Good things are happening.

On the morning meeting with Steve and Dustin. We mostly just did our own thing today. Steve and I chatted about a few things but mostly I was working through small to do list stuff, emails, recording notes, paying bills, and what not. Steve was doing the same thing.

I did put up some notes from a meeting with Chuck the other day. He is working on some mock-ups for the campground industry. Here is the link to our notes from that meeting.

Web link - time_web_gallery.cfm?corp=748&id=5012

Shannon and I touched base and I showed her some of the new graphics and stuff that both Chuck and Jonathan have been working on. That was fun and she enjoyed it. I enjoy sharing and showing progress and vision. After that we worked on the online glossary. We were on J's, K's, and S's. See the link below.

Web link - time_web_gallery.cfm?corp=371&id=4030 - online glossary of terms

- Talking about scheduling and reservations. We could do campgrounds, hotels, rafting companies, ski areas, etc.

- Getting into job costing and project tracking.

- Small talks about insurance and how independents deal with insurance. Small talks on individuals as well as companies and working for your own company. Being able to write off certain things based on your own business stuff.

- Light training

- Frontend and backend tools. Light talks about the how that would work.

- New icons on the side, new pages, being able to split reservations (group reservations and being able to split into individual reservations).

- Maps - a user could upload a map (just a base image). We could also allow for settings and bookings, using that map. We could really tweak things out here... when you click on a location, it could pop-up a modal window and show existing availability, reservations, stats, options, and booking values. Maybe have the users send us a map and then we build it out into a functional piece with nav, JavaScript, pop-ups, etc.

- We also talked about building to the dream vs just building what you know. If you only build to what you know, you limit yourself based on tech and get stuck on the how are we going to do this and that. Build to the dream and try to match the tech as needed. That can come later if needed. Build the dream.

On the morning meeting with Dustin, Steve, and Alan. We were touching base on all of the things going on. Steve needed a merge into master for his current code branch. We did that and both Alan and Steve have plans to take some of the pages a little bit further. Most of the meeting was just touching base on different projects and who is doing what.

I spent quite a bit of time working on emails and doing some follow-ups with different people.

One of the follow-ups was with Russell. I called him and we chatted and then jumped online for a 2 hour meeting with both Steve and I. Great meeting. See below for a number of ideas, concepts, direction, and notes from our meeting:

- Need to focus on Snow Owl theme settings (overall look and feel of adilas pages, reports, headers, footers, and data tables).

- On the data tables (fancy tables that allow exports, sub filtering and sub searching, and sorting of columns) - we talked about the need to get a better handle on these data tables, make them more standard, and deal with the possible weaknesses and/or bottle necks with going with these new fancy table structures. By way of a note, we have a number of these data tables throughout the entire system. We need more of them and we also need to refine some of them to make things faster and smoother.

- We talked about what would be involved with the process if we created our own data tables, specific for adilas, and our client's needs. We talked about creating our own custom tags, our own we components, and then using that throughout the whole system.

- We spent a good amount of time talking about how the need to show aggregated data could remove some of the existing load from showing transactional data with the data tables. Those data tables are really good at showing smaller number of records vs tables with thousands and thousands of records. They really work better for things in the hundreds of records vs the thousands of records (and up). Aggregated data would be things like quick counts, totals, sums, averages, maxes, mins, groups, and other overview type data and numbers. That would also be great if we could show that data in charts, graphs, quick numbers, easy to use mini dashboards, and even graphical sub homepages or graphical homepages per section (system main player groups and/or subsets of specific tools and features).

- If we start showing graphical homepage and aggregated data, it would virtually allow us to pull back a level and push the transactional data deeper. It still needs to exist, but it may be a better option if we could get them quick details and data and then allow for drill-downs as needed. Quick, easy, simple, and then more details as needed.

- On the data tables, do we know what people/users are using and wanting? Is it the exporting, the sub searching, filtering, sortable columns, or quick pagination?

- Maybe work on and do some concepting and proof of concept on the adilas data tables. Take it to the fracture level.

- Russell is going to get with Brandon to do some training on the existing and current data tables. We plan on recording the training session. The goal is to start standardizing the implementation of those tools and features (data tables) in the system.

- We (Steve and I) are really trying to focus on better project management, planning, and helping everybody get small victories. Some of this may involve virtually protecting our guys so that they don't get pulled in every direction.

- Lots of talk about MVP's (minimal viable product) and shooting for that type of approach.

- Breaking things (projects and processes) into smaller projects and pieces.

- Asynchronous data loading for big record sets.

- API sockets and loading in bite sized pieces, data, and logic as the application backbone (main source of both raw and formatted data).

- Russell was talking about a need for more developer training, requirements, snippets, CSS and code samples, standards, validation, and other dev tools.

- Steve and I would like Russell to lead the way and lead out on what is new and what is going on. Nothing too huge, but basically, what is the next logical step?

- Having Russell and Chuck work together. More coordination and small teams. Getting involved with all of the other players and pieces. Different talks about teams and collaborating with each other.

- Easy, pretty, simple, and powerful

- White labeling our own product on a per business vertical type model.

- Russell would really like something that he could be involved with and have some kind of stake, claim, and or ownership. We talked about both adilas and adilas fracture type options.

- Steve would like to come up with a new business type model - who owns what, a perpetual trust type entity, open invitations, rules, regulations, standards and options. Reformatting our existing business structure.

- The concept of how "fracture" keeps happening. The deeper we look, the deeper it goes. Everything is sub dividing and splitting into smaller and smaller pieces or subs. Along with that, where are we headed? Ok, then let's build that.

- The whole thing keeps unwinding and new ideas keep coming and falling into place. We just keep taking the next logical step forward.

- We are seeing more and more needs and wants to be mobile ready, responsive, and modern design needs. This could be mobile apps, phone ready options, different screen sizes, multiple screens at the same time, virtual environments, and where are things headed? Keep pushing forward. Skate to where the puck is going to be (proactive approach).

- We are really wanting to jump into some other verticals (business entities and business categories).

- Steve used to look for a single rep or consultant. Not marital status, but size wise (just one person at a time). Now, he is trying harder and harder to find super consultants who want a group of like clients, outsourced compliance, oversite, over viewers, and other vertical specific services. He would love to tie into different CPA firms or groups. The goal there is to turn over the training, setup, oversite, and support to these super consultant groups or white label entities. They run with the needs per business vertical.

- Reoccurring revenue models and how to work with it and mange it along the way. SaaS (software as a service) and what and where is that headed? Good stuff.

- Let's make it happen. We can check off the checkboxes. Let's do it.

- We even want to move our leads over to the correct white label suppliers. We will act as the industry specific point of contact until a suitable entity and/or third party white labeler is in place and/or available.

- Let others focus on each vertical, we will focus on the core and our software package and the offerings.

- Even the core keeps fracturing. That sounds bad, but we are really excited about it. This is the new direction, small, multi pointed, configurable, flexible, software options and packages.

Chuck and I met and did a little bit of internal training. We added some notes, sub dates and times, photos, and media/content to a project (element of time) that he was working on. We also went over some billing and invoicing questions. I showed him how we search expenses, add expenses, pay bills, document things, and write checks out. Mostly just a Q and A session to get oriented. We also setup some meeting times for the next couple of weeks.

Meeting with Chuck to get an update on Camp Adilas. We started out reviewing some other new graphics that are being presented and worked on. We then jumped into schools and how adilas could help out schools. Kind of a fun start to the meeting.

- Schools and options of supporting schools and education needs. Say like Bridgerland Tech College - They have 25 different departments, they sell all kinds of things, they have a book store, class fees, special events, tracking profit per department, café - lunchroom, catering, etc.

- Being able to configure the tools and features to fill the needs of the different companies and/or departments within a bigger organization.

- Here is a link that deals with options for schools, some older brainstorming - Web link - time_web_gallery.cfm?corp=371&id=2844

- As we were talking, Chuck said that he sees himself as being able to be the bridge between the tech side and the people side. He likes that kind of stuff.

After the first part of the meeting, we got back into some campground and camp adilas stuff. See attached for a number of screenshots and an overview of where we are headed. Here are some notes from that part of the meeting:

- We talked about tons of options on different flags and tags. These could be things like notes, red flags, warnings, etc.

- Options for simple reservations and options for advanced reservations.

- Being able to collect vehicle information, customer information (counts and types), payment information, etc. There is some basic information and potentially, some more advanced or one-to-many detail information that may need to be gathered. Lots of moving parts and pieces.

- We talked about primary reservations, secondary reservations, and being able to stack and unstack those reservations and payments or deposits on the reservations.

- On the payments, be able to apply discounts to all reservations or just certain tickets.

- Be able to send out emails to help collect other information to help fill in the gaps and speed up the process.

- We got into some details on the different screenshots. Detailed site overviews, handicap accessible (wheelchair icon), color coding, using flags and tags, etc. On the color coding, we even talked about allowing the color codes to be setup using settings. We would set some defaults, but allow each company to change or alter those settings. Say something like yellow for partial paid, red for need to pay, and green for good to go (already fully paid).

- Chuck showed us some map options. He had actually used a drone to capture an aerial view of a campsite. We talked about all kinds of map and map overlay options. We talked about mixing maps, photos, icons, services, options, site photos, descriptions, filters, add to cart, set or choose date ranges, etc. All of these options, right from the map. Kinda fun. One of the cool ideas was using the icons on the map to help filter and show sites that matched your filtered search.

- We got into some of the other sub screens and talked about a customer info screen with flags and payment options.

- Lots of options for settings on a per section or per page level. That is awesome and we would encourage the development to be build off of settings.

- Be able to build your own reports and then be able to save those reports with the settings and configuration values needed. We already do this in places inside of adilas. Keep going along those lines.

- Showing reports on earning and services sold. Be able to see sales based on tents, RV's, cabins, firewood, power, and swimming. Whatever the services and/or options might be.

- As we build this business vertical out, it will open up new options for other companies that need scheduling and reservations. Good stuff.

- One of the last things that we talked about was using all of the different kinds of resources such as other developers, trainers, code, google, other team members, reps/consultants, etc. No specific rules there, just use what you need and play well with others. We want to keep it pretty open, but still make the resources available that are needed and wanted.

Steve and I were talking after our meeting with Chuck. Here are a few notes about what we were talking about.

- Using what we have and cleaning up these servers that we already have.

- Keep moving the servers up to ColdFusion 2018. Keep moving down the road.

- We want to use elements of time on our own project management. We've got it, let's use it.

- Having the guys check in once a week to make sure we are on task.

- Steve would like to use Tuesdays and Thursdays as developer check-in days.

- We really want to help our developers get some wins and some victories. This may end up happening by helping them break their projects into smaller chucks, phases, steps, and milestones.

- Steve made a comment that it will be interesting as we get more involved with Designers. Instead of from code up to the view... we will be going from the view down into the code. That will be somewhat of a paradigm shift for us. Exciting.

Adding screenshots to elements of time, research, recording notes, and cross tying different resources together.

See attached for a new document from Chuck Swann. It deals with needs that schools and educational institutions need and want. That same document was also attached to an older element of time in the adilas university site that had ideas about using adilas for schools and education. See this element for those other ideas and details.

Web link - time_web_gallery.cfm?corp=371&id=2844 - ideas of how adilas could help out schools and educational facilities

//////////

I was also trying to gather some graphic resources for Shay (adilas graphic designer and logo/setup wizard). Here is an email that I sent to Shay with some links to different graphic resources.

Good evening. We have tons of graphic assets… the only problem is that they are not super organized. Here are a couple of links:

Web link - time_web_gallery.cfm?corp=748&id=4933 – tons and tons of images (including some new ones), you may need to click on the links within the document text and then save the images to your local drive.

Web link - help.cfm?id=393&pwd=map – there are tons of graphic links just below the map on this help file

Web link - photo_gallery_full.cfm - tons of fun teaching tool graphics, if you need any originals, I can get them for you.

Web link - Item shop page – tons of pdf links and image links. See the other teasers tab

Anyways, I hope that helps. Enjoy!

///////////

The other thing that I was trying to do was sign some documents for Wells Fargo and small business banking changes. Somewhat of a random afternoon.

Met up with Chuck to go over some camp adilas stuff. He is making great progress on the interface layout. Good stuff. Here are some of the notes from the day. Also see attached for some screenshots and some notes from another follow-up meeting with Marisa - campground rep.

- Alan, Steve, Chuck, and I were on the meeting. We introduced Chuck and Alan.

- We talked a lot about going mobile. We talked about native mobile apps and responsive web apps. We are leaning more towards responsive web. There were some talks about using phone gap to convert from web to native mobile (Adobe product). We know that some of the camp host staff may be mobile from time to time (going around their campsites and such).

- Light talks about some design elements such as titles, slide outs vs modals, buttons, colors, preset color themes, etc.

- The next round is deeper prototyping in Adobe XD and making it more clickable like a virtual sales demo.

- Steve brought up a point about deleting inside of adilas. We often show/hide and make things active or inactive to accomplish the same thing as deleting, but we really never delete the data. It just gets hidden. That way we don't create any holes in the data.

- KISS - Keep it simple silly - trying to keep things in that simple model.

See attached for some screenshots.

Update on Camp Adilas progress. We postponed this due to the demo today. Both Chuck and I went and met at Bridgerland for the demo.

Bryan had some new Expo code to push up to the servers. It was dealing with invoice rounding for ecommerce. This was not done as core (currently), meaning the adilas code core. It was special code just done on the Expo payment solution side of the equation. Anyways, we pushed up some new code. We then went through a number of questions. One was dealing with custom spreadsheets, using existing spreadsheet templates, usage of API sockets, play at the wall - type mentality, and also a project dealing with adding additional salespersons (employee/payee) to invoices and quotes. This project would not tie into payroll, but it would be tied to invoices, quotes, stock/units, etc. Very similar to the existing additional customer tie-in options. We went over ideas and light direction on those projects.

Just for fun, I also showed Bryan a couple of screenshots from both Jonathan and Chuck (adilas designers) to let him see where we are headed. Fun meeting.

Steve and I met with Chuck. We started out talking about a prior demo that Chuck and I did. We then rolled into an update on the camp adilas project. Here are some of our notes:

- On the demo that I did, I opened it up too much and it ended up going all over the place. Not very focused.

- Create canned versions of what we can do and how we answer some of their needs. Almost the elevator type pitch (30 second or 2 minute overview).

- Maybe a concept map (like a site map)

- What can we do?
>> - Say something like - point of sale... walk through the steps
>> - Say taxes... walk through the steps

- Idea - create a simple web page and show some sort of nested titles (see Chuck's report page for his camping site and then be able to nest sub sections under those tiles).

- Protoype in Adobe XD for now, then maybe switch to WordPress or some other thing.

- Have Brandon create a list or outline and then have Chuck help put things together.

- From Steve - grateful for Chuck being able to bridge the gap between the look and feel and the sales side.
>> - Helping to get into the marketing groove.

- Start building out some specialized industry flyers. We need a general one and then some that are specific to industries that we cater to.
>> - Icons and helping to drill-down into the deeper specifics

- Chuck would like to see - testimonials and customer endorsements, backing, recommendations, and validation.

- How are we going about our building process? From the look (look and feel) down to the code vs code up to look (what is our approach?).

- Getting some of us out in the field really helps build and refine the system. As we sit through training and demos, we will have ideas and see things that need to be cleaned-up. Great use of time and resources.

- Reduce the learning curve - that will help get people more into the product.

- Being able to link out to specific screenshots as part of a presentation and/or demo.

- The power of the quick search inside of adilas - go anywhere - that is awesome.

- Any choice that the user has to make (over and over again), usually makes a good settings.

- Designing both levels normal web (desktop/computer) and mobile (responsive).

See attached for a number of new screenshots from the camp adilas or campground interface project.

Recording notes and pushing up tons of new screenshots from meetings last Thursday. We had a great meeting with Chuck and with Jonathan. Over 10 screenshots from each meeting. Here are some links to those pages.

https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=748&id=5085 - meeting with Chuck - future demo ideas and camp adilas update.

https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=748&id=5153 - meeting with Jonathan - general system navigation and reporting options.

Reviewing some mock-up video walk throughs from Chuck and the camp adilas project. See the links below. The password is camping.

https://vimeo.com/372499060 - 17 minute walkthrough of the camp adilas project

https://vimeo.com/372500075 - 6 minute walkthrough on advanced reservations
 
These are private videos. The password is "camping".

Making phone calls and chatting with our guys. Made calls to both Chuck and Eric and chatted for a bit and answered some questions.

Meeting with Chuck, Steve, and I. We went over some of the new screenshots and I took a number of new screen clips. We talked about the videos that Chuck had created. He will re-render them later, once he gets a full version of the software studio that he is using for capture. Steve suggested that Chuck look at some of his brighter colors and help soften and/or tone them down a bit. Just a suggestion. We also talked about more settings and getting a sign-off from Marisa on the flow and functionality. That is our next major stepping stone. We will keep refining things until we get that sign-off. From there, we will start moving to actual code.

If you want to see the mock-up videos for the camp adilas project, click here.

We also spent some time talking about the upcoming Bridgerland demo and what we wanted to do there. I proposed a few ideas, we drew some loose sketches, and setup a new time to work on the project. Leaning towards a configurable presentation gallery vs a perfectly straight in-line presentation. Lots of fun ideas and concepts.

See attached for a number of new screenshots.

////////////////////////////////////////////////////////////////////

Notes from Chuck - sent via email on 11/13/19. I thought that they would go good here.

I had a meeting with Marisa and Danny today at 11-12.

Here are my notes from the meeting.

Overall they are very impressed and happy with the new colors and setup of the current layout
 
Updates that I need to do:
- Marisa is going to think on a better verbiage for the split sites setting.
- Need to add a setting for a waitlist for those who have already created a reservation but want a different site if it comes available.  For example if they are currently in a site with only electricity but would also like one with water and sewer hookups if it comes available
- A way to merge duplicate records (in case there was as misspelling on a record) - this isn't an essential launch feature but would be nice to have
- Add (FT) behind RV icons on sites to be more specific
- When the check in or out button on sites is clicked it will launch an invoice so the user can see if the customer has a balance and needs to pay in which case it will go to a payment option, or if the customer is paid in full the user can look over the invoice and then email or print an final invoice for the customer.
- I want to redo the layout for the user setting as it's confusing
 
At the end of the meeting Marisa was asking a time table for completion as she is excited to sell it!  I told her "maybe spring, and that I really didn't know".  - hope I wasn't overstepping on that :)  she is really excited to get it out.

We started to build out a visual tile board based on the adilas formula flyer. Here is a link to the older flyer...

Web link - adilas_formula.pdf - adilas formula flyer

We had a small discussion about world building and how it sometimes confuses people - almost too bold and too abstract. We talked about ways of softening that. For example: Say the different stores in a mini mall or different departments in a big organization. In a way, those smaller pieces or entities are building their own world.

What if we approached it by saying... currently you need a POS, an ecommerce package, a CRM, an ERP system, accounting, etc. Inside of adilas we allow you to pull those things all together under one umbrella. This becomes the virtual universe for that company. Show them how we can pull all of these things into one system. We are also really flexible, configurable, and nimble.

Results is one of the main four topics (results, business functions, application players, & core concepts). The results (what you are looking for) are huge. This side plays more on the emotions and wants of our users.

Link to a fun Ted Talk by Simon Sinek - Web link Ted Talk

Here are a few notes from the Ted talk:

- Why - Share the why

- The golden circle - 3 levels - innermost level Why, middle level How, outer level What

- Help people learn from and be driven (of their own free will) from the inside out (why, how, what)

- People buy why you do it, not what you do

- Attraction of people - people who believe what you believe

- Driven by a cause - willing to put in and work with blood, sweat, and tears

- Prove what you believe by why you do it

- Helping to take and push a cause further - Once again, because they want to...

//////////////

Going back to the sales document that we were working on (notes from above), Chuck sent me an updated link. Click below to see the Adobe XD layout. Pretty cool.

Web link Adobe XD File

Emails, reviewing some new stuff from Chuck (sales flyer stuff), and recording notes.

Went into Bridgerland for a 2nd demo. We were in the main admin boardroom. We had about 10 people. Some of them were the same and some of them were different than last time. The whole demo felt smoother and on a better level. The first one we were fighting against a time constraint and we had multiple people who wanted to see different things. By way of a note, I used Chuck's new sales flyer graphic to help show some of the options that were available. See the link below for a sample (not the actual graphics but at least a taste).

https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=748&id=5211 - some new sales flyer sample graphics done by Chuck

We spent about 3 hours in the demo and covered a number of different topics. I felt like it went much better. Both Chuck and I were there at the live demo. Afterwards, the main college President came and chatted with Chuck and I. He is a great guy and I've known him for years and years. He has always been a great supporter of me and my family. Awesome stuff.

Danny, Dustin, Steve, and I were on the morning meeting. Danny had some Git (code repository stuff) questions. Steve and Dustin were working on some bug tracking. We also showed the guys some of Chuck's new layouts for sales. We had a bunch of fun ideas. Some of the ideas were being able to change the backgound images, changing the main presentation settings, and even being able to click on a link and have it automatically switch background images, verbiage, and settings. A simple little URL switch and all of a sudden, you have a customized presentation. Super cool idea.

On this same line of thinking... if we can flip the demos and presentations really easily, we could potentially use the same presentation gallery to do different presentations for different verticals. We just store the settings, verbiage changes, images, and even options, features, tools, and usage models. That would be super cool.

- Maybe using the ice-down date as a transfer between transactional data to aggregated data... That is a great switch and/or trigger. Similar to the water to ice analogy... The transactional data is kinda loose... Once it gets pushed to the aggregated data, we really want that data to be more stable (more like ice). Great idea.

- What if we had some bulk tools on the transactional side to post and/or lock things down. Once that data is locked down, we can then pull that data across to the aggregated system. Steve was talking about a possible two-part effort. They get to set a date (virtual line in the sand) and things behind that date can't be changed without altering the ice-down date. We also allow the users to lock things down on the transactional side of things.

- On a different note, Steve would like to build things out to a trust level... Making a number of adilas players as dependable cofounders. As a side note, we could use the new customer loyalty points to keep track of a virtual club member point system. They, the special accounts, are already setup like mini bank accounts.

- Camp adilas overview - see screenshots - lots of new work on the mobile side of things. Exploring all of the different screenshots and options.

- We spent some time and did a small review of the demo yesterday.

- We still used world building but we related it to pieces that they could understand (going from full abstract to hey, this makes sense - speaking their language and at their level). That is huge. We talked about how we could do the same thing in a more general way.

- The demo felt more prepared and more simplified. That was good.

- One thing that came up... tracking history and seeing who does what in the system (the hidden audit trail and use of different logins). We introduced this later on in the demo but they really got excited about it. We may want that to surface earlier as what is going on and a key feature.

- When doing the ecommerce demo... that was a little rougher. We had to keep switching between systems due to images, settings, and being able to flip to the more pretty and mobile ready version. We had a few rough spots in this part of the demo.

- Lots of talk about the permissions page (aka the football field of permissions). We want to get the permissions broken down to a better level that is easier to understand and to copy/apply. They (our users) are wanting to break them (the existing permissions) into custom permissions, sub functions, and other functionality. Deeper control, yet a simpler interface and experience.

- We spent some time and talked about the new sales outline that Chuck is working on. We used it in our demo, our morning meeting today, and almost every other meeting today. Pretty cool. We like the direction that we are headed. Click here to see a small sample.

- As we build things out (in the sales flyer)... we would like to connect these to videos - we talked about keeping things generic and highlighting the pieces vs our brand (white label options).

- There were some conversations about talking about world build and getting it into a more simple thing analogy right off bat. Maybe even some scenarios that deal with beginner, intermediate, and advanced concepts. Once again, help it be more consumable.

- Brainstorming on world building ideas... We could start with a web layout, index page and then it goes from there, or icons and a more structured layout. We spent some time talking about how to help get our users and others to get their heads around the concepts. We ended up watching two videos to help us get into the frame of mind. The links are below.

Web link - video-bestbook.html - Brandon Mull (author) - What makes a great book (world building concepts)

Web link YouTube - Shannon Moore - System thinking - fun video from an older training session

Molly and Bryan joined the meeting. We introduced them to Chuck (designer) and showed them some of the new things. After Chuck left, we looked at the cross corp invoice to PO functionality. There were just a couple of tweaks that were needed. After we figured out what was needed, Molly left and Bryan and I added some code and then pushed files to all servers. We are making progress.

- Chuck is working on details and nitpicky things on the camp adilas project. Things like layout, margins, spacing, etc.

- On the extra services... Chuck is seeing that there will be an extra page for a mini shopping cart for general items, additional services, etc.

- We also talked about some of the next steps. These are in no particular order, but we talked about getting sign-off's, locking down the project scope (aka round 1 vs round 2), creating tour/marketing videos, starting to build our own CSS libraries, prepping for the next level or next project.

- Small note about videos. We talked about some sort of fund raising campaign and the pros and cons to that. Our current plan is to make the videos for us... either to help sell or pitch the product or to show people what we can do as far as a full end to end layout and design option. Both of those are really cool and will help us gain ground. Good stuff.

Met with Jonathan today about some of his layout ventures and site mapping and exploration stuff. We are making great progress. As a fun side note, in his demo today, he is hitting on almost everything that we have thrown at him via ideas and/or requests. I'm really impressed. And the best part... we are having fun along the way. Here are some notes from our meeting.

- We went over some of the things that Chuck (another designer) is working on and how that plays in.

- https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=748&id=5211 - sample screenshots from Chuck's sales work (presentation gallery)

- Jonathan then did a demo of his new layouts and I took 20+ screenshots. Super cool. I challenged him to create a virtual walkthrough video so that I could show it to other people. I'm super excited about that. Lots of refinement and making things more and more simple to handle and navigate.

- We talked about design systems or a system style guide - CSS - These are basically documents with visual elements and technical specs to help everybody on the team be on the same page. Helping to make the layout and look and feel all congeal and work together.

- https://data0.adilas.biz/css/ - Small link to some of our existing CSS style sheets - This was a simple page that has a bunch of dummy data on the page. We will use some of these pieces to create the system style guides and design systems.

- After we get some of the styling fixed and lined out, we'll start going through the app and working on flow and processes. We will hit the most used sections first such as clock in/out, shopping cart, searching for items, invoices, quotes, etc.

- My goal - if we can sell what we have and keep it powerful, easy, and pretty. It is already very powerful. We need some loving on the easy and pretty part of that equation.

- Making it easy so that we can go to the masses. We want to open things up a bit. Along with this, we realize that some of our legacy clients may never switch, but all of the new clients will start out on the new features and hopefully enjoy and gain from those new developments and new design UI/UX (user interface and user experience stuff) and love the products. We will keep heading in that direction.

Group meeting dealing with camp adilas project. We had Chuck, Marisa, Danny, Steve, and Brandon on the meeting. We are all really excited to see where things go. Good stuff.

- We talked about confirmation numbers and being able to add and search those.

- Being able to change customers after the fact. This could be the main customer or adding additional sub customers, depending on needs.

- If more options are needed, it will be built on top of the existing adilas backend platform - that opens up a number options.

- Report settings - adding prebuilt reports based off of the settings. Being able to tweak things as needed.

- Permissions and fully removing certain icons from the menu systems based on those permissions or lack of permissions. We decided that fully removing those options would be best for this project.

- Mobile and being able to help solve issues on site - this is huge and could be a great selling point (the mobile version of the app).

- We talked about helping with real traffic flow (actual cars, trucks, vans, SUV's, RV's, campers, trailers, etc.). If we can help alter the bottlenecks, that may be a huge help. The mobile app will open up some options there. Some good discussions around that topic.

- Self check-in options

- Digital signatures and disclaimers - other possible customer portal options

- "I'm here" button and then help them get checked in

- Using other adilas reps and consultants to help do other things and provide other needed services or additional options. This could be design, web work, custom code, training, setup, map stuff, etc. All kinds of options.

- Cart settings for scans and presets. Being able to show preconfigured add-on's and normal barcode scanner POS options.

- Being able to set a default home screen for different users. For example: the check-in desk, the gift shop, the reservations desk, whatever.

- We got the verbal green light to move from graphic concepting to HTML/CSS - clickable web mock-up with dummy data. After that gets finished, we'll actually wire the whole thing up via backend server-side code and database connections.

Awesome meeting. See attached for the video recording of the meeting. There are also a number of still screenshots in the photo gallery.

////////////////////////////////////////////

These are some notes that Chuck submitted after the meeting.

Hi everyone,

Here are the notes I took from today's meeting.  Let me know if I missed something.

Notes from meeting with Brandon, Steve, Marisa, Danny and Charles on the design sign off
 
Tweaks that need to be done to final product
 
- Reservation # added to invoice (under Invoice in the upper left corner of the invoice) and possibly use a bar code or QR scan for the invoice to pull up the invoice.
- We can use a setting for a seed to generate the reservation number for example use a date and site number for the seed or something similar
- We need to have the ability to change or split the invoice for different customers.  This can be placed in the settings icon on the invoice
- Have a go to admin that would place the customer back into the Adilas back end if they needed to adjust advanced settings
- Add a vacant filter quick button to the sites page
- Ability to add quick buttons to the menu list.  The customer would be able to add favorite searches or functions to the menu list by choosing an icon and setting up a tool tip.  Setting would be found under the setting icon for each section
- When we get to doing the front end we should look at having a self check-in option that can either be a full self check-in or an I'm here button to notify the user that a customer is there and ready to check in
- Need to look at icons and standardize some of the icons.  Replace the cog with filter at any area that a filter is being used instead of settings.
- Be able to set which cart/invoice section is default (cart, invoice, or scan)
- Make a user that only has access to the pos system and can just sit and scan
- Changed the calendar to have green vacant and red filed on the sites overview
- On the calendar ad function so you can click a day and it will take you to the sites page for that day
- Add a date range either through search or above calendar to change the background of the calendar pages.  When one of those dates is selected it will take you to the sites page with that date range pre-loaded

Shannon and I met and went over some ideas and questions presented by Chuck. We pushed up his copy of the presentation gallery outline. Some of his questions and comments were in yellow. See attached.

As Shannon and I were talking. We decided that we wanted the new presentation gallery to only go so deep. We virtually wanted to put a small floor on it and help it have a bottom (a border or boundary). We don't want it to go any deeper than 4 to 5 levels deep. Our plans deal with drill-down options, icon tiles, icon lists, awesome (static) screenshots or collages of screenshots or small videos at the bottom most level.

We talked about showing related items in different places, where they turn up... there are pro and cons to that. Some people may think, I've already seen that section, I'm not interested in going in there again. Other people may need multiple options to get to that section due to their angle of approach and/or there interest levels. If we repeat certain key features, it may actually play into the system mentality and system thinking type model. Once again, pros and cons to both approaches.

After we finished going through Chuck's new ideas and questions, Shannon and I went back to more brainstorming on CRM (customer relationship management) and CMS (content management systems) in our presentation gallery outline. We will post those changes as they become more defined.

Met with Chuck and went over some ideas that Shannon and I had come up with from an earlier meeting. Chuck and I reviewed his changes to the presentation gallery outline and we made a few more notes. Some of the new things are in yellow.

After that, we started looking at the next round on the camp adilas project. Chuck is taking his Adobe XD (layout, graphics, mock-ups, and design work) and moving it into real web code (HTML and CSS and JavaScript). Super cool and I was amazed at how well the web versions were a complete replica of the graphic mock-ups. I even had to ask Chuck, is this a graphic or code based. That is awesome.

Anyways, we went over a few things and then even looked at some code. Really exciting. As part of our conversation, I approved Chuck to bill us for some JavaScript training on a weekly basis. The ideal would be between 4-5 hours a week to help him improve on those skills. I was really happy with what I was seeing on the HTML and CSS side of things.

See attached for a couple small screenshots. Two of them are HTML/CSS pages (actual web code) and the other is a graphic mock-up and an actual web page.

Met with Chuck for about half an hour. We touched base on a few things and then went into some of the new progress on the camp adilas project. He is working on coding the pages and showed me some new pages. One of the new things was the ability to pop up a modal (sub window on top of the main window). The new code looked really cool and we also talked a little bit about some relative positioning of some of the sub menus and what not.

Chuck had a couple of questions about the design and which direction to go in. We switched gears and looked at some older sites/pages inside of adilas where we had to make similar decisions (what to hide, what to show, and how to pass in hidden choices). We also decided that Russell would be a good match for helping to wire up this application when the time comes.

See attached for a couple of new screenshots.

After the meeting. I spent the rest of the time doing emails and recording other notes from the day.

Cory and Josh were talking about the number of clicks, settings, and being able to show/hide certain fields. The two hot points were the shopping cart and the PO (purchase orders) page. Basically, getting items into the system and then being able to sell out those items quickly. We are leaning towards some shopping cart settings and also breaking down the needs into smaller steps as we know that some of the pieces may end up being really big.

We talked about sketching things out on paper/pencil and then moving things into a graphic mock-up, coding and then wiring things up.

We showed both Josh and Cory some of the new graphic mock-ups that are being done by both Jonathan and Chuck. We looked at some of their ideas and mock-ups to talk about options, layouts, and configuration options. We talked about showing them, meaning our clients, some of the mock-ups and graphics of where we are heading, that would be way better than having them design things from the ground up.

Managing customer expectations. That is always a challenge. As we were getting deeper and deeper, we are seeing more and more needs/wants of being able to configure and customize their own settings and such.

One of the projects that we talked about was dealing with updates and helping to let our clients know about certain updates before they get rolled out, especially if the updates may have consequences and/or possible issues. Some of the high traffic areas are carts, invoices, and state compliance stuff. We talked about delaying some of the updates instead of just pushing up new code.

Josh recommended a update log that could be searched and even have a small blame section - who coded it. Hopefully blame is the wrong word, but we all know what that means.

Maybe a different section, like the developer's notebook, where we could publish some of the updates and make announcements. We also talked about scheduling the code pushes and making sure that we aren't running faster than we are able.

Molly joined us towards the end of the meeting and had some great comments. Good stuff.

Russell gave me a phone call and we chatted for about half an hour. He is going to be working with Chuck on a number of projects and we chatted about priorities and direction. He is recommending that we do a cost analyst on the camp adilas project. We talked for awhile about both seen and unseen costs and hidden benefits as well. Great conversation. Russell has instructions to keep working with Chuck, do some project management, coding his own projects for adilas, oversite, and working on a new adilas business model with dependables and cofounders. Lots of interesting things. Good stuff.

Met with Chuck over a GoToMeeting session. Below are a few of my notes from the meeting.

- Light review of what is going on with Shannon on the presentation gallery. Shannon and I are still building out the main outline (prep work). Chuck is currently not doing any design work on that so that Shannon and I could finish with the first round and working on the outline.

- Review about plans working with Russell. Both Chuck and Russell have green lights to work with each other and keep advancing the ball in various areas and on different projects.

- We went over the camp adilas project. Chuck is working hard on building out the different pages including some of the modal window pop-ups (sub pages within the flow of the site). We also spent a little bit of time talking about "plugging" or "tabling" unknown pieces. We talked about charts and options for showing pre-built dynamic charts vs building things from the ground up. Lots of available options there. Both Russell and Alan are great resources for charts and plugging in those things to pages.

- A couple of challenges that were extended to Chuck - Have your wife check it out (what you are doing and building - get some feedback), have someone else who knows nothing about the project look at it - get their feedback, and on purpose change up the background images to see how things look as the background change (alpha, transparency, color schemes, font colors, etc.)

- Light review of how the training was going. Chuck reported on where things are at and making progress. Good stuff.

Met with Chuck to go over some progress on the camp adilas project. Here are some notes from the meeting.

- Report on showing it to someone else who is not involved - He showed it to his dad. He recommended the ability to add packages (buy this and get this and that). We already have this (called recipe/builds) and we could tie it in through the custom cart or POS system.

- From our last meeting - He added tool tips, different backgrounds, and different screen sizes.

- On the coding side, we talked about file imports and includes on backed CSS pages and code - backend stuff.

See attached for some new screenshots with different backgrounds. As a side note, the background won't change on each page... it will be a setting and the user will set what they like and then it will follow them through the application. In our demo, we switch the background tons of times to show options, in reality, it will be a single cool fixed image that the user sets. We will most likely have a corporation setting and then allow users to alter things as they choose (if that is allowed by the corporation). Pretty cool.

Chuck and I met for half an hour and went over some ideas and projects. We touched base on the sales flyers and presentation gallery stuff. I told him that Shannon and I were still working on the outline. We then switched over the camp adilas project. Chuck showed me some new web/CSS/HTML mock-ups and we chatted about some options. The project is going along great and everyday new pages are being mocked up in real web code. It always takes a process to go from graphic mock-ups to real web code with CSS and HTML code.

- We did talk briefly about a break through with icons as part of a dropdown menu. Chuck had to do some research and some trickery to get it to work. We lightly talked about some JavaScript options for helping to strip out the choices from the hidden form fields.

See attached for a couple of screenshots from the project.

 Met with Chuck to go over some new progress. We touched base on a couple of other topics. We then jumped right in to the camp adilas project.

- Discussion on some marketing efforts for the camp adilas project - leaning towards the name Wander Ways.

- Possible WordPress plug-ins and using API sockets to talk back and forth. That way the clients have their own site and still get the full adilas backend engine. If we go with a WordPress plug-in, that may be a great angle for us to pursue in the future. Currently, we want to acknowledge that angle but it won't be our primary focus.

- Light talks about competition and some sales ideas and goals.

- Chuck reported on his cross browser compatibility issues. He reported on multiple issues and multiple browsers. Good exercise and we learned quite a bit. Possible support issues if they are using a really old browser. See the scans for some funny screenshots (black and white versions).

- We may want to put some JavaScript checks for browser versions - this is especially true once we get out to the customer facing front end.

- Conversation about CSS variables. Chuck is building out more and more include files to make updating an easier task. Code once and use many. Make it maintainable.

- As a side note, we went over some light training and I gave Chuck an older training link with some videos and other resources.
https://data0.adilas.biz/adilas_training.cfm - code training is towards the bottom of the page

At the end of the meeting, we made some introductions between both Chuck and Jonathan. Chuck did a small demo for Jonathan on what he is working on. Exciting times.

See attached for a couple of screenshots to document the progress and development process.

Steve and I were on the meeting most of the morning. Dustin popped in and we talked about a few quick things. He is doing great. After that, Steve and I did some of our own stuff and also spent some time talking about some upcoming pieces. There are always some challenges and Steve really likes to keep figuring out the next step. Here are some of our notes.

- We spent quite a bit of time talking about an abundant model vs just trying to hold onto what we have. We really feel like we live in an abundant model (lots of options). We have an upcoming situation that we need to figure out if we are continuing, altering relationships, or moving on - dealing with an outside party. We spent quite a bit of time talking about this subject.

- We spent quite a bit of time talking about bringing things up to the next level and how the virtual data assembly line (stages and flex bubbles) play into what we both have and where we are going. We have had great success trying to follow that model. What is the next logical step and how are we going to get there.

- Steve and I spent some time and we were drawing on the screen and talking about ideas and current models that we are trying to follow. We were looking at the tri-facto model with system features, number of clients, and education and training legs of that tri-facto. We are trying to fill in more on the education and ease of use side of things. Some of our new efforts are dealing with the graphic designers like Chuck and Jonathan. We spent some time and looked at their (Chuck and Jonathan's) newest progress reports and where they are going. We also talked a lot about the future potential of what they are doing.

- From earlier this weekend, I had a guy who asked me about adilas and what it does. We talked about a platform based model that we could build on. We related it to a chemistry set and the ability to mix and blend those pieces. Basically taking custom development to the next level by mixing and blending what we already have. Build new, change up ratios, enhance existing, etc. Being able to mix and blend like a chemistry set, made sense to me. I thought that it was a fun analogy.

- Steve and I spent a lot of time talking about transitions and handling those transitions. Steve was talking about how business is all about transitions.

- We talked about burnout and how that can effect you now and even later on down the road (virtual flashbacks and post stress stuff). It is real. How do we deal with it, how do we prevent it, and how do we build going forward?

- Running a business takes a lot of both physical and mental abilities - it is a challenge.

- We need to be compensated for our time and efforts. We give a lot of stuff away for free. It is kicking our buts.

- You are either part of the problem or part of the solution. Where do you want to be?

- We are really wanting to attract people who really want to play (developers, trainers, designers, consultants, etc.). That may take a specific bread of people, but that is what we want.

- Steve and I will be doing more and more project management as we go forward.

- Focusing on one project at a time. Staying focused. Maybe something like one main project and maybe some small filler projects. Currently we get really spread out and somewhat lose focus.

- We talked about bottle necks and being careful about who is doing what. If you create too many key points (certain people do certain things), it creates bottle necks. Be careful. Keep things moving and flowing.

Met up with Chuck to go over some of the camp adilas project. He showed me some of his research on different sites, ideas, concepts, and products. He then showed me a number of new things that he is working on in the design realm. We talked about customer facing websites, advertising, sales, his team that he is working with, template/layout decisions, and web domain names (website names) stuff. Good meeting.

On a side note, Chuck was showing me some of the new date pickers, animated checkboxes, and other form controls. Some of which, he is wiring up using his own new JavaScript skills that he is learning through training. Really exciting.

See attached for some screenshots.

Meeting between Chuck and Brandon. Steve joined us part way through. We were talking about current tasks and direction.

- Not really learning ColdFusion right now but more on helping to get the snow owl theme to the rest of adilas.

- Pages that Russell and Chuck are working on - classic homepage, payee permission home, add/edit user permissions, mange corp info, corp-wide settings and defaults

- We have purchased the project theme (bootstrap CSS theme). All of those resources are available and online. We were looking at more of the options that come with the preset theme that is already being used.

- The look and feel is so important and really helps to sell the system.

- We may need a way to prompt our users to upgrade to the newer look and feel. This was an idea by Chuck to help us prompt the users to upgrade. If they do upgrade, maybe we could help them by flipping some switches and even changing some of the settings. Make it easy to switch.

- Tying in the new classic homepage design to a user setting. We may need a toggle to switch between the new and old style and also some image controls. Chuck was saying maybe even a picture of the day. We also talked about picture categories and maybe letting them choose.

- Looking at different online resources - get those from Chuck - He had a number of sites that offer free and awesome images and pictures.

- We talked about different levels of control. Do we allow it at a per corp level, then a per user level? Etc. If we bring something forward, we will quickly get requests for more control and more options.

- We are thinking of trying it on a few of our other homepages. We have like 5-10 homepage that this could work on. Talking about a fun changing background image.

- Flipping over to the campground project, we talked about sub dividing it into small pieces and who is going to do what. We may kick some of it over to Marisa to let us know what is the most needed pieces. Trying to shorten the development cycle and get it out to be used quicker.

- For our next meeting - lets get 5 categories of photos (space, mountains, general scenery, ocean, animals), 10 photos per category, figure out the main icons, vertical tabs in the bootstrap theme.

See attached for some screenshots. Some of the screenshots are dealing with possible mock-ups and internal pages and options.

Charles, please add your ideas and concepts here :)

Had Alan on the meeting with Chuck and I today. We wanted to get him in on the projects and getting a high level awareness of what is going on. We started out with the camp adilas project and where that is in the development cycle. Chuck did a demo for Alan and they went back and forth with ideas and questions. Both guys are excited to work together on the different projects.

After that, we rolled into a session talking about some snow owl theme (current look and feel inside the system) changes and where that could go. We looked at some mock-ups for the classic homepage and then then into user permissions and profiles. See the screenshots for some of the new ideas. Still in concept mode but definitely coming. We are thinking of putting a facelift on a number of the high usage pages or places where it looks older or more outdated. We are trying to change up the user experience and make it better and better.

We talked about user profiles, permissions, and allowing templates and presets. We talked about having tabs, vertical tabs, accordion displays (ways to show/hide additional data), floating submit buttons, putting help files and summaries under the gear icon on the side of the page, stash and go with a sock drawer type concept, and even changing the page flow to help the users. Currently, they do an action and may end up on a different page or on a success message. They then have to navigate away to another place or do some other action. Good page flow will really help.

A couple of other topics were mixing tasks and skills to get a job/project done vs a full stack developer (able to go from top to bottom or point a to point z - the whole thing). We may need to help some of our developers get really good at certain tasks to help with efficiency and productivity. We also talked about light messages and helping to lightly push our users towards the newer look and feel and/or new functionality options. We know that we have to be careful there, but we will make some attempts when ready.

After the meeting, Alan and I talked briefly about some of our developers and where we are headed and who could help in what regard.

New note added on 1/8/20 - Danny Shuford contacted me and asked that we make the view only permissions easier to get to. I showed him some of the concepts of where we are going with user profiles and permissions and said that I would add a note to this element of time. The original idea came from Kelly Whyman and Danny brought it to us. Great idea. That may require some special code just because the view only permissions are not standalone permissions. They require the main permission and then the view only permission to limit the options.

- Brief talk about application modes and how that works. This deals with how the system is broken down into the 12 main players or 12 main application players (think of the core layout). The modes work in a similar way. By default, the mode is the "data mode" or information mode. That means what is stored or organized per main player group. For example: All invoice information or data can be found under the invoice button or invoice category. In the data mode, you can get to the data for that main player group.

- If you switch the mode to say: "permissions mode", you would get all of the permissions that are related to that main player group. For our example: Say the invoice button or invoice category. You would get all of the invoice permission. You could do the same thing for settings and other main topics. Basically, you choose the mode and then select the player group. You then only get stuff that is related to that player group.

- The main application modes are: data mode, permissions mode, training mode, settings mode, usage and stats mode, tech/concept mode

- The 12 main application players (main player groups) are: customers, invoices, quotes, items, stock/units, elements of time, employee/users, vendors, PO's, expense/receipts, deposits, and balance sheet items. A couple other main  groups are things like banks, flex grid tie-ins, locations, corporations, media/content, and the list goes on. The primary 12 are listed first.

- The magic comes where you are able to click on a mode (data, permissions, settings, training, etc.) and then select one of the main player groups (invoices, customers, items, vendors, etc.). You are then able to see what plays into that section or group. Mixing the application modes and the player groups, allows for all kinds of combos.

- The concepts above are built from picking the mode first and then the application player group (example: data mode >> lets work with invoices). What if you were able to go the other way (example: work with invoices >> show me the permissions or show me the settings). It may be cool to go back and forth between the ways of interacting with the underlying pieces. As a side note, we do the same thing in a shopping cart (how we create quotes and invoices inside the system). It does matter if you start with the items or you start with the customer, as long as you get both pieces before you checkout, you are golden. Non-linear and information and relationships flow in multiple directions.

//////////////////////////////

- Talking about the camp adilas project

-- 1 person doing Ajax calls (Josh) - hardcoded data is passed back and forth - no real connections to the backend (kinda middle ground), 2-3 people doing the backend wire-ups (Brandon, Eric, Dustin) - deeper or core developers - maybe one to do database connections and the other doing the service layer (wiring), plus the designer (Chuck).

-- We will make a basic concept page that has some different parts and pieces. We will then assign that concept page out to the different developers. The concept page is just so that we can get some ideas and virtual mini library assets.

-- On the concept page, we want to get a full sign-off on that page before we let the other guys advance. That is checkpoint of sorts. The concept page will be somewhat of a group type project just to make sure that everybody knows what is going on. Walk through it with them, then let them drive, give feedback as needed.

-- Set a standard for the new stuff.

-- On the Ajax calls - we are thinking about pulling back actual HTML vs just data - that way we could just replace certain pieces without having to worry about mixing HTML with data.

-- Brandon and Alan will work together on the project management side of things.

-- Have meetings with each role to get them pointed in the right direction.

-- We want to write out test cases as well.

-- We will be creating a new folder for the new camp adilas project stuff. This includes js, css, html, ajax, and code.

-- We will work with Wayne to help with domain pointers and internal mapping.

Chuck, Alan, and Brandon were on the meeting.

- Brief overview of projects.

- We reviewed the camp adils project with Alan and made some small plans. Alan is going to help project manage that wire-up job (the main project).

- We also went over a number of mock-ups for the user permissions page and helping the older classic version get updated into the snow owl look and feel. See attached screenshots for details.

Meeting with Chuck. Alan joined us and Wayne joined part way through. We started out by going over new corp admin mock-ups, talking with Alan about projects and files, and then looping around and introducing Wayne to Chuck and vice versa. Wayne has been working in and on computers since 1979 (long time). Towards the end, we had Chuck show Wayne some of what he is doing on the camp adilas project. Nice meeting. See attached for a couple of screenshots.

- Both Chuck and Wayne have worked on the hardware and networking side of the IT world - As a funny side note, they don't like the pressure of "It's always the server guys fault" - Pretty common for IT guys. They get the blame. They don't get remembered when it runs correctly, they just get the blame when it has a hiccup or an issue.

Weekly meeting with Brandon and Chuck

Weekly meeting with Chuck

Met with Chuck over a GoToMeeting session. We covered three main things in our meeting today. The first thing we looked at was the Wander Ways website and the mock-ups for the sales arm of the camp adilas project. See the screenshot for an update. Nice looking site and Chuck will be working with Marisa and Danny on prices, verbiage, photos, and content. Exciting.

We also went over some new mock-ups on the adilas corp-wide settings and corp administrator homepage. We talked about some options and also decided that a nice banner image would really help that page out.

The last thing that we did was go over some code for the camp adilas internal tools and project. This project is in the coding phase and looking good. Chuck is using some of his new JavaScript skills to help wire things up a bit. Still in the transition between code mock-up (CSS and HTML) and backend wiring (making it real and come to life). Great report and making progress.

Working with Shannon. We spent some time and went over some of the main happenings and how the different projects are tying together. Both from the graphical user interface side (UI/UX - user interface or user experience), the layouts, the code, and then mixing and blending all of those pieces together. Super fun. I showed Shannon some of the screenshots from Chuck and projects that he is working on. We also talked about internal adilas and some of the page layout and flow changes that are coming internally.

After that, we spent some time brainstorming on payroll options and what pieces we wanted for our presentation gallery under the payroll stuff. All kinds of fun things like time clocks, user/employee options, vendor options, reporting, forms and paperwork, commissions, project time tracking, customer time tracking, check writing, automatic updates on forms and tax look-up tables, etc. Fun stuff.

We had a few of the guys on the meeting to start with. We had Alan, Steve, Dustin, Chuck, and myself on the meeting. Chuck and I started out going over some topics from the new promo videos for WanderWays. This is a new video that Marisa created for introducing the product and then pitching it to campgrounds. Fun stuff. Chuck has it under control and will get with Marisa to work on tweaking a few small pieces. Great start.

We then switched gears and talked about some of the bootstrap layouts for the existing adilas site. See the screenshots for more details. Lots of new pages and pushing them towards the current snow owl theme (bootstrap layouts). Currently there are about 5-6 pages that we are reworking.

We then went over some of the other WanderWays stuff. We looked at some new code and layout on the tool side as well as new code on the promotional or marketing side of things. Great progress. Towards the end of the meeting, Alan and I were talking with Chuck about some project management stuff and also getting another developer involved to help with some of the new code changes and wire jobs that are needed. Plans keep unfolding and we are trying to keep moving forward. That is fun.

Alan and I met for another half an hour after the designer meeting with Chuck. We talked about personalities and where each of us are heading and what we are wanting to do. If any of us get too much on our plates, we each tend to curl up and not get much of anything done. I've seen it happen over and over again. We talked about some project management stuff and getting a good direction and some traction going in that direction.

After that, I helped Eric out with some questions. I then got a call from Calvin and worked with him for a bit. I showed Chuck how to enter a reimbursement into the system to get paid for some of the stuff that he is doing. In between times, I was recording notes and pushing up screenshots for Chuck from our meeting today.

5/29/2020: Jonathan has a design worked out.

3/18/2020: Page settings: keep them but allow to collapse. Comes from the invoice sales and profit search page.

Print all option: Print to pdf view= looks like screen shot. Have a section of the mj operations page on the top of each section. You can skip to different sections. Each section needs to have its own total.

See attachment screen shots. a)Customer reports= data (like on mj operations page) then visual. Customer types and Queue Reports. Each exports as its own excel. Split expiring customer or patients column into 30 and 60 days. Then take over column 4 that is currently 60 days and make it queue reports.Add visuals. Switch customer types to be on the left and Customer Queue Report on the right. 

b)Sales Report= data =from inventory quantity/weight report. Use columns: category, quantity, weight, weight sold, running weight, sales price, cost, gross profit, percent. (remove vendor and inventory columns). Then add visual of sales. Want to see grouped by category and weight: ***How many 1/8ths, how many 5pk pre rolls, how many 200 mg edibles?

c) PO Reports: need to figure out how to recreate like invoices. Add the mj operations piece for this. (This example is actually from invoices.) We want to show how many did we purchase? By category and weight.

See visuals by category and weight. Need to group all by category and weight. 

2/10/20: Rewrite to mj operations homepage. Start with phase 1- first report for one corp. Walk first, then run. Have Charles work a few hours to make it look good. Get a better drawing from Molly, drawing over the mj operations page and reworking it. Use fake data. Includes all 5 reports Molly's clients want.

Multiple corps would be phase two.

2/4/20: Reviewed project 1627, 1628, and 1629 with Molly and got a new vision of what her client wants. This is all too much. (referring to the three projects- they won't want another system- what is the purpose? They want one page, one dashboard that is divided into 5 sections. One section has the customer data (new, total) one section has queue data: total time (queue to exit), avg total time, POS- exit time. Both of these have their data points and a graph. Section 3: sales and profit report with category and weight. Also multi or single location, multi or single corp. Daily, weekly, monthly, quarterly, all. Section 4: Purchases/Production- just pulls from PO's- no sales info- only cost. Still category and weight. Section 5: Inventory on Hand= looks to po's and invoices to determine. 

Want to keep it simple- similar to mj operations homepage, but just needs a little more data.

Original idea:1/29/20: Client wants a customer report with total customers and new customers displayed like invoice homepage data. Ability to print and also cross corp multi locations. Steve thinks we can use the invoice template for this and pull customer data instead of invoice data. 

7/6/2020:Total Time: about 91 hours

3/31/20: Progress has been made on classic homepage look and feel.

, Payee permission, corp wide settings and manage corp info pages

2/3/20: Brandon will relay this project to Russell, Chuck and John. The trio will have a budget of $1,000 to do the four pages. If it isn't enough we will determine at that time how to move forward.

1/30/20: Cory met with Charles and saw the mock-ups he and Russell have been working on (have 17 hours cumulatively into potential project). Quick and relatively easy way to make adilas look more updated/relevant. Start with Classic homepage- keep same functions but move around and simplify. Would be a relatively uncomplicated page. Payee permissions is much more complicated and more time consuming. Go through adilas one page at a time- open to customer feedback for direction. Hoping they see classic and get excited. 

Charles can work on this at the same time as his other projects. He can do front end design and development and code the front end. Needs someone ie Russell to wire up the back end. Russell is interested in working on this project as well.

** check with Brandon- has Eric started on duplicate permissions? If this project gets done is that as needed ie should he be focusing on something else?

We invited a couple of the guys to meet with Jonathan today. The main topic was the shopping cart or internal cart. So many things go on inside of the cart. It really is a heart or very viable piece of the equation. On the meeting today we had Chuck, Alan, Steve, Jonathan, and myself. Chuck started out by showing a few shopping carts and point of sale (POS) options from his WanderWays - camp adilas project.

Jonathan then showed us around some of the things that he is prototyping, including the custom navigation options, settings, and custom configuration pieces. We also went over things like the education mode, simplified searches (hide search form fields until needed and/or wanted), and combined searches. Lots of stacking, tabs, and just in time access menus.

After that, I did a small demo on how the cart works and how things get configured and used inside of the internal shopping cart. We switched carts, we did discounts, assigned customers, restored quotes to cart, added notes, payments, and all kinds of options. See attached for a small video recording of the walk through.

The last part of the meeting was dealing with some critiques and ideas from the different guys on the meeting. Good stuff and making progress.

Updated - as of 2/3/20, two new video links were added (see attached) for concepts of the invoice mode (mock-up for fake data) and also a proposal for the education mode and how adilas fracture interface could inter connect with the adilas café project. See the attached videos for some overviews.

Weekly meeting with Brandon

Meeting with Chuck and a new developer named John Peterson from the Logan, UT area. We had a fun meeting and went through some introductions, had a small Q and A session, and went over some project details. All of us were using webcams for this meeting. We don't often do that. Planning for the future, we are planning on having Chuck, Russell, and John work together as a small team of developers, designers, and project managers. Exciting times.

I will get the non-compete and non-disclosure documents over to John and Chuck and Russell will help get him going. We also briefly talked about other future options that may play out, depending on how this little arrangement works out. On a different note, we at adilas are really grateful for these guys/gals who are willing to help us out and play the game with us. Lots of moving pieces.

After John left, Chuck and I went over a few things dealing with WanderWays - camp adilas and some design decisions. Chuck is going to be organizing resources and assets to help standardize the process. Basically a style guide of sorts. We are using the WanderWays project as somewhat of a guinea pig project to help figure out some of these things. We also went over a few new layout options, some new code enhancements and even some fun pricing stuff. Chuck is adding in some flavor (light jokes and play on words) into the pricing matrix. Fun stuff.

Meeting with Chuck and getting a report on where things and different projects are at. Chuck and I spent the first half an hour on the meeting by ourselves. After that, we had Alan join us. Some of the topics today were progress on the standards and style guide, the code changes and layout for the WanderWays (camp adilas) toolset, tons of new development on the WanderWays customer facing marketing site. Looking good.

The whole last half of the meeting was Alan and Chuck asking questions about the WanderWays backend tool and going from rough layout and code into tech requirements for wire-up and development. Alan had a full page of questions and we went through each one and made notes and decisions. Fun process.

See attached for some screenshots.

General clean-up for the day and recording notes. Pushed up a bunch of new screenshots from a meeting with Chuck and Alan.

Web link - time_web_gallery.cfm?corp=748&id=5966 - screenshots for WanderWays website and the camp adilas project

Met with Chuck and Alan for a weekly check-up meeting. We talked about project management and I sent Chuck a copy of a document that we've been reading and reviewing. After that we talked about the adilas shopping cart and how to help that project out. Chuck is going to organize a meeting with some of our designers and developers to talk about the cart and how to do a full re-write. We got a bid from a developer, and it is looking like it would be around $20,000 (ish).

After our meeting on the cart, we jumped into a small review of the WanderWays tool - camp adilas project. Chuck has been working on the look and feel settings page. See attached for a couple of screenshots. By way of an update, the settings were getting to be so many that Chuck had to redesign and reuse the space better. Lots of work is going into that. Also, as he is going over all of the needed settings, it is helping to refine what is actually needed and how best to set things up and organize those values. For example: all the colors in one spot, all of the font types, and all of the possible background options. Everything needs its own spot.

The last topic of the day was planning for the future. We talked about setting up some of these current projects with an outlook (plan) and setup for future projects.

We were going to do some developer training but decided not to this week. Instead, we ended up just taking care of odds and ends. Bryan joined the meeting and we went over a small project that he has for promotion codes outside in ecommerce. His project is going to be really simple and will store and hold things in a simple JSON object. We talked about how, at some point, he will need to beef this project up and help build it out a little bit more. The first round will be really quick and small and then we'll circle back around and add more functionality as needed.

Towards the end of the call, Chuck joined and ran some screens past me. They are in the WanderWays tool - camp adilas project and adding in new inventory items. We went over what he has and also what we have in the main system. Good meeting.

Meeting with a number of folks. The goal was dealing with the shopping cart. We had Steve, Chuck, Jonathan, Cory, and a client on the meeting. The first part of the meeting was the client going over some of their requests. Here are some highlights from them...

- They would like to be able to send text messages from the customer queue

- They would love to have a hand-held scanner and have it automatically be able to update an unmanned cart. Some talks about using the built-in cameras on certain tablets and such. Other talks about hardware and software problems and solutions. Through the web, sometimes those pieces are hard to get to perfectly talk to one another.

- Lots of questions about barcodes, labels, and auto/bulk actions.

- They would like possible popup/modal type windows to see customer notes, maybe the last invoice, and even a modal popup on the ++ or advanced add to cart (haggle tools)

- The also spoke about major needs for tiered pricing - the same options that work on my cart favorite buttons and smart groups and tiered pricing. As part of this discussion, there were options mentioned about parent attributes, barcodes on buttons, advanced barcodes (QR codes), mini conversions, etc. This becomes a bigger and bigger need. It also needs to be more standardized. Lots of options, but because it could go so many ways, it is hard to find the correct path. Too many options.

- Along the tiered pricing vein, there was also a request to be able to assign items (subs or child packages) to a pricing tier through the build new PO process (bringing in the items and assigning them to a pricing tier as part of the inbound process).

- They really want a fully interactive cart, yet still locked down, yet still super powerful, yet super simple, yet, yet... Lots of requirements.

- Training mode, how to get to the best training and how to connect the dots. We have help files, news and updates, videos, etc. - but we need a way to get to that really quickly. They, the client, were also requesting that each new feature has a full tutorial and/or video. They only wanted the things that were fully done to be added to the news and updates.

- They would love for more onsite or local training options. They love the time and are willing to spend the money. They would love to get the training options to be standardized and regular (scheduled and consistent).

- They love the bulk update cart functionality

- Being able to bulk print labels and skip steps (save as a quote or cart checkout). The also wanted to be able to flag certain items that they only need one label vs multiple new labels per quantity, etc. It sounds like it could be pretty deep. There were also requests to be able to bulk print labels from the PO. Calvin's new adilas label builder does do bulk labels for invoices and PO's. They just might need some training.

- Online orders, ecommerce, and even options for delivery.

- In the cart, being able to see it at all times. Having some sort of split screen where there are items or look-ups on one side and all of the items on the other side. Lots of one pagers with asynchronous connections and easy flow through the sections and/or pages.

- We love ideas and helping to push the ball forward. The needs keep coming. We just try to keep solving those pieces as we can.

- We also allow the clients to chime in and help us prioritize, fund sharing, and have a say in where things are going.

////// more notes after the client left - Just Chuck, Jonathan, Brandon, and Steve

- Steve - a big thank you out to both Chuck and Jonathan - you guys are stepping up the game. He was also talking about collaboration between the different developers and how cool that will be.

- There may end up being 8-10 versions or variations of the shopping cart. At some point, we need to separate the logic from the view/design. Jonathan was also talking about putting the specialty features into settings so that each cart may be more configurable. Good stuff.

- Questions from Jonathan about market analysis and what does that say for us? Sadly, the reality, we haven't done anything there. Lots of options.

- There were some talks about having a system to run your stuff vs trying to marry all of the individual pieces together. There is pain on both sides, but we are heading towards the systematic type approach. Trying to bring all of these things together.

- Time to value - how many clicks to get those needs fulfilled. Not that we can't do it... we just need to figure out how to help speed up the process and make it easier and more easy to get to those pieces and features.

- Smoothing out processes and making it easy to get to the places that they need to. It kinda comes down to navigation and visual flow process. Aka - the full user experience.

- Steve was talking about how making these pieces work together to get all of the POS (point of sale) systems, inventory tracking, CRM (customer relationship management), CMS (content management systems), accounting, reports, and backend storage all in one place. That is the dream.

- Some of our clients are virtually starving for instructor lead training. Jonathan is saying that there is a barrier to entry to this... meaning the learning curve to fully know adilas. We need to help provide it and also help to standardize it. Small talks about competition, reps/consultants, and ways of teaching the processes, pieces, and principles.

- Small mention of the adilas café and how some of that would help us provide training and service type options. You could get training from the adilas university or you could get direct training and/or hire a certain person to help fill a certain need. Think of all of the power users that could offer services and/or training. What if we could show user stats on who has done what and what level they qualify.

- From Chuck - what about a monthly webinar? We could plan it out, record it, charge for it, etc. We could do digital meetings, in-person training, instructor lead trainings, etc. As we keep updating the system, we need to keep updating the videos. Maybe even using YouTube as a primary source of training. Possible Facebook groups, tips of the day, etc.

- From Chuck - doing light idea mining when we are out and about. For example: Hey, what processes do you do to sell things? We then record that and start making some settings, permissions, and selections together to help them with what they are doing. Presets per industry. Sometimes it is so overwhelming... we could really create virtual profiles and help with settings and configuration stuff.

- From Chuck - small talks about web components and being able to customize things on the fly. Separating logic, functions, views, displays, processes, etc.

- Lots of settings and even helping those people get to those settings and help it make sense for each industry. Settings and configuration options. Groups, categories, settings, nested presets, tiered pricing, labels, etc.

- From Chuck - he really doesn't like it if we do a process and then virtually dump him in an unfamiliar page (backend navigation). That comes back to page flow and user interface. We will keep working on this. If we send the users to the correct spot, we don't lose them and we even help them know what the next step should be. This may take some mapping and design stuff.

- Trying to stay small but still looking for talent and help.

- Help file on barcodes - Web link - help.cfm?id=413&pwd=cart - barcodes can really speed up shopping carts and there are tons of options. This is an area that could still be developed out further and enhanced. Just an idea.

See attached for a number of other resources. There are a couple of videos and some research on shopping carts and POS interfaces (point of sale interfaces).

- Recap of some marketing strategies - going after niche markets and/or advertising the general adilas platform

- We would like to setup some meetings to talk about targeting certain verticals and then building out those pieces

- Start working on the camp adilas project and dividing out the pages

- Talking about training and setting up trainings, conferences, and digital meetings

- Somewhat of a digital bootcamp with a specific topic - planned out, training, homework, and then making those trainings available after the fact

- Charging for training without going over the top - covering costs and making some money

- We had both Wayne and Alan join the meeting and ask some questions.

- We did a whole section where Alan started talking to us about project management and starting to show us what the process is looking like. Everything from mock-ups, wireframes, test cases, tech specs, sign-offs, timelines, and budget stuff.

- Trying to break things into smaller and specific tasks. Front end team, back end team, etc. Even talking about goals, requirements, timelines, and key phases and milestones.

- Chuck started showing us some new design work on settings and what not. Lots of work in the settings area. See attached for some screenshots.

Both Alan and Chuck were on the meeting. We covered a number of topics today. Just as a reminder, here is what I had in my notes: Talked about getting some funding through grants, direction on the internal shopping cart, color pickers, project management and specs for WanderWays (Chuck and Alan doing documentation), item/product management page, discount settings, meter read items, keeping running tabs or running totals on invoices (long stay invoices and options), things on account and/or multiple payments, online bill pay, multi invoice statements, icon pickers, site builder pages, sites and sub locations, bulk edit tools, handling work orders, dealing with cash drawers, hardware/software requirements, and permissions for things like refunds. Busy meeting but some great topics. Wonderful report.

See attached for a number of screenshots.

Alan was on the earlier meeting with Chuck and I. After that meeting, we touched base quickly and talked about a few projects. Our goal is to help get a few of the close ones over the finish line.

Our meeting ended early so I started working on the new 2020 state and federal withholdings. I did some testing and pushed up files to all servers. Shawn and I have been working on new withholdings for a few days now. Trying to get everything up and online.

Chuck and I had a meeting. Normally we would have been going over progress that Chuck is making on his projects. Instead, Chuck and I spent an hour going over options, plans, and business stuff. We covered things from our napkin budget, to forecasts, to what we want our business model to be. Fun meeting but slightly different than many of our other meetings. Lots of potential out there. We just need to work on picking it up.

Chuck and I were on a check in meeting. He was reporting on WanderWays (camp adilas toolset) and where things are at there. He is working through the code and making great progress. Last week, we ended up talking about other things and I didn't give him time to report on where he was at. See attached for some screenshots. Most of his current work has been focused on color pickers, wiring those color pickers up, add/edit sites page, bulk edit, some UI (user interface) decisions, and work orders. He has also been doing a little bit of research on other verticals and industry specific needs.

Steve and I were on this morning going over budgets and forecasting stuff.

Chuck joined the meeting around 10 am. The notes below here really show be on the meeting with Chuck. See this URL/web link:

Web link - time_web_gallery.cfm?corp=748&id=6052 - meeting with Chuck, Shannon, Marisa, Steve, and Brandon

- Target marketing vs broad or general advertising - industry specific - medical, alternate medical, herbs, homeopathic, preparedness stuff - industries that are helping or assisting other people right now - what about mom and pop little cafes and restaurants that want to do delivery or online orders or curbside pick-ups. 

- Using social media to help sell and advertise things - we haven't spent much effort there - helping to get people more engaged

- Small little places that need ecommerce and delivery options - In the last couple days, we have turned on the existing ecommerce package for multiple clients

- What about lists of different businesses

- Facebook marketing - super targeted and affordable - Facebook has a ton of ways to target certain demographics

- Other methods - radio, email marketing, google ad words (can be expensive but productive - you need a budget and a good ratio per click), flyers and beating the street - most of these were expensive and did really do much

- Email marketing worked good for your current clients because they knew you a little bit - Maybe do our own campaign.

- What if we did some more training, while everybody is at home. Sell it online, do it, present it, and record it. Basically a stuck at home boot camp. We would even harvest our own email list for that. Brandon volunteered to help teach classes if needed. Shannon has also taught in the past.

- Focus and target it in such a way to say - here is how we can help you!

- Maybe run some small experiments on some of these things - meaning make sure that you have a landing plan

- Videos are a huge way to get some training out there and done

- We had Steve, Brandon, Chuck, Maris, and Shannon on the meeting. Good input from all parties.

- Light talks about the existing 2020 model and selling things where we are at

- Steve wants to go full speed ahead on the existing ecommerce solution - this seems to be the current focus and/or target we want to pursue

- Small plan - Email marketing to our existing clients, news and updates, and get some training on how to setup and use ecommerce - we have a number of people who are very good with the ecommerce solution. We can coordinate those trainers and presenters. Prep things in such a way to help the clients. Open to anyone.

- Russell did a great job prepping the existing training on the ecommerce solution.

- We could also offer consulting, training, and even a series of training events to keep pushing the ball forward. Maybe start with the existing things and build from there.

- On training efforts during the next six months - adilas 10% and the other 90% is for Chuck and his team - note added by Brandon

- We have a viable solution and we just need to get our offerings out to the public in order to become more stable.

Notes were actually recorded on this other element of time. Great meeting. Trying to focus in and change direction.

https://data0.adilas.biz/top_secret/time_web_gallery.cfm?corp=748&id=6068 - see this for the meeting notes

Emails and phone calls with developers. Talked with both Chuck and Russell.

Cory booked this time block for me to work on payroll stuff. Clients are upset with this not working. They, the federal government, majorly changed how federal taxes are calculated.

Chuck and I met up over a GotoMeeting session. We started out by going over some screenshots from a meeting that I had last week with Jonathan Wells. This link shows a number of screenshots for an internal shopping cart mock-up that Jonathan is working on. Click to view cart screenshots.

After that, we rolled into some new things from Chuck. We talked about email campaigns, advertising, and training. We took a little bit of time and worked on an outline for an upcoming ecommerce bootcamp - ecomm basics course. Towards the end, we got into some new ideas and direction on the presentation gallery and digital outline of what we have to offer. Fun new things coming down the pipeline. Good stuff.

See attached for some screenshots.

Just for fun, these are some notes from Steve to his friend Danny.

adilas is the future of cloud
custom cloud

Current SAAS (Imagine a static cloud with our competition on that cloud)
Future CSAAS (imagine a dynamic cloud with just adilas on it)

Old SAAS is version based (updates roll out via version)
Future SAAS is custom based (updates roll out real time and are client driven)

Not only is adilas changing real time, adilas changes are driven by the client.

This creates the most powerful software and a client can drive their business forward.

Times change, software must change with the times

Business processes change, adilas changes by businesses.

Look at the black box code you just completed, that was an extreme example.
Look at the view only code you just completed, that was specific client based update that all clients have access to. Many will never use this but it's part of the process to build the solution bigger.

adilas - Expanding and Refining Functionality, Driven by Business

adilas gives businesses the ultimate tool

--------

As part of our meeting, Chuck joined us and we talked about the presentation gallery (navigation, slides, and talking points) vs a real self-guided website that has a self-contained sales pitch. Great little meeting. See attached for a small version of where presentation gallery and slides are headed.

Chuck reported on a number of things that he is working on. He is working on setting up an ecommerce class towards the end of April. Working with Marisa on email campaigns, and other training courses. We also talked about direction on the presentation gallery and heading into the slides and page layout options. After that we went over tons of adilas ecommerce settings and internal training.

Chuck and I met and had a good little update meeting. I updated him on a few things and he reported in on the projects that he is working on. Good stuff. He reported on his slides for the presentation gallery project, ecommerce training, working with Marisa on marketing stuff, and the internal project for new look and feel on the corp-wide settings page.

We spent some time talking about filling in gaps and checking to see where we are vs where we want to be. The difference is our current goal and ongoing project. Fill in the gaps. We talked about taking care of known needs, coordinating with others, and taking care of our existing clients. Great meeting.

As a side note, we may end up offering some free training courses to help train the trainers and get the curriculum down better.

Started out by recording some notes and catching up with the day. Sometimes things happen so fast, you only have time to jot down quick little scribbles that then you translate into actual notes. Lots of moving pieces.

The rest of the session was spent on working on other or older projects. Big older merge, duplicate expenses, email to chuck, group by question, default users per system, etc.

Chuck and I met and touched base on a number of different projects. I gave him a small review of some of the new direction with the core and value add-on's to that base core. We went over the different outer rings and some of those ideas. After that, we jumped into some of his projects. We talked about the corp-wide settings page, the new slides for the presentation gallery. We spent some time there talking and going over ideas and concepts. Looking good.

After going over his current projects we spent some time looking for a code bug in a page that he is working on... pretty hidden bug, we couldn't find it with our first initial glance. We then closed the meeting just chatting about general things that are happening and going on - life stuff. Good meeting.

Web link - XD file - current slides in the Adobe XD layout for the presentation gallery (still under construction)

Great little meeting. Chuck is working on a new corp-wide settings page with the snow owl theme. It is getting really close. He is working with Russell on some of his projects. We also talked about the presentation gallery and having he and Russell work on that project. That project is getting ready to leave mock-up stage and go into the coding phase. The other task that I gave him was working with Russell to build a new graphic that shows the adilas core with value add-on rings or levels. We just want to see some prototypes on that. Good stuff.

Meeting with Chuck to go over projects. He is currently working on some ecommerce email campaigns with Marisa. The email campaign has a Star Wars flair to it - kinda funny. He is also working with Russell on some of the re-vamp projects. The other thing on his plate is the presentation gallery project and getting that coded and working. He is currently working on menu systems and what not. Good report.

Chuck wasn't feeling well so we had a quick 10 minute meeting and called it good. He is doing some mock-ups for Bill (a client) and working with Russell and Marisa on different projects. Spent the rest of the time working on small little projects and to do list items.

Trying to catch-up on emails. Over 80+ new emails in my inbox this morning. Steve needed a merge with the master code branch. I spent some time working on that.

As a side note, one of the new emails was email 3 for the Star Wars - adilas ecommerce email campaign. I have copied in some screenshots from the email. Chuck and Marisa are having fun and I think it is fun.

Chuck and I had a good meeting. We went over some existing projects and progress reports on each of those. Chuck has been working with Marisa on email campaigns, ecommerce training, and prep for a meeting to show the camping stuff (wanderways website and campground tool).

We went over some font awesome stuff and then rolled into a project that he is working on for Steve. The new project is a custom dashboard for employees and special HR type functions. We did some training on black box stuff and pulling in images and photos to the new custom page.

Weekly check in from Alan. He joined earlier, but I was still working with Chuck. We got back together around 11:30 am. Alan reported on his current projects and showed me some new code that he is working on. He does a great job re-factoring and re-using different code blocks. He showed me some new stuff dealing with objects, DAO's (data access objects), services, and database triggers. All of those pieces are fairly advanced and above the ability of some of the other developers. Nice update.

Chuck and I were working on a custom flex grid project for a client. We mapped out 11 different flex grid fields and did some backend database clean-up on his local environment. We then started to pull in the data to Chuck's custom output page. Wire up job and doing some training along the way.

Steve and I were the only ones on the morning meeting this morning. We started out just doing our own things and working on small projects. After a little bit, we ended up talking about some of the challenged of doing custom code verses doing more specific and/or rigid specs. We have a lot of concepts and dreams that play into what we do. That is really hard for certain developers (black and white thinkers) to grasp. We sometimes code to the flexibility and potential of a project vs the exact need or output. We like that, but it does make it difficult at time.

This whole conversation started due to a report that a developer called me yesterday and said that he had decided to take a certain project in a different way than what was planned. Originally we had proposed three options and were leaning towards options number three. Unbeknownst to me and the other developer, Steve and Cory had quoted a few other projects based on the fact that certain prep pieces would be in place from this other project. To us, the other developer and I, we could go any direction that we wanted (we had multiple options in front of us). We didn't know about the other plans. This conversation between Steve and I got us talking about direction and vision and who is managing all of this... it gets pretty deep, pretty quick.

We talked about all of the different phases and how things either need to and should flow through certain processes. We talked about R&D, look and feel, mock-ups, project management, wire-ups, custom code, database design, servers and deployment. It gets pretty deep.

As a side note, one of my new emails was email 4 for the Star Wars - adilas ecommerce email campaign. I have copied in some screenshots from the email. Once again, both Chuck and Marisa are having fun.

Wrapping up a phase of Chuck's CSI project. We are going to be transitioning it into a new phase and pass it on to another backend developer. Chuck has taken it about as far as he could. As a side note, each developer has strengths and weaknesses (not bad things, just strengths and weaknesses). We need to had this project off to another developer. If not, poor Chuck will literally be on the side and not knowing what to do and what comes next. It goes beyond the reach and/or scope of the skills and talents currently available. More good stuff to come but currently maxed out.

Chuck will be going back and working on some other projects like the presentation gallery (sales tool and visual outline project) as well as some other projects that have been assigned.

We finished up our meeting and got some code and notes ready to pass on to the next developer who will run with the wire-up portion of the project.

Working on some code management stuff and project management for the CSI project. That project is a custom employee/user profile page that deals with custom photo scanning to check employee temperatures when they come in for work. Chuck and I finished up his part of that project yesterday and now we just need a backend developer to help with the rest of the wire-up job.

After that, I spent some time recording notes from yesterday. Transferring post-it note scribbles into elements of time (developer's notebook entries).

Going over projects and touching base with Chuck. He is working on the new corp-wide settings pages, a thing called "dev docs" - new section that deals with code snippets, style guides, naming convention, and other standard type stuff. We chatted for awhile and talked about WanderWays (camp adilas project) and other current and upcoming projects.

Chuck and I got on the meeting but the other server problem took over. In between random debugging pieces, Chuck and I sent some text messages back and forth.

Chuck joined the meeting to report on some of his projects. He and Russell are working on a number of cool pages and what not. He also showed me what he is working on the adilas docs - section to show SOP's (standard operating procedures) for adilas, style guides, code sign-off, and other info that everybody on our team needs. It is looking good.

I also got a report on his corp-wide settings page and light report on the WanderWays project (camp adilas).

After that, I used the rest of the time to record notes and more general stuff.

This meeting had two main parts or pieces. The first section was with just Chuck and I going over current projects. He is working on some sign-off documents and helper files for other adilas developers. He is really trying to help standardize things and make things happen on that side of the fence. He also showed me some stuff on his and Russell's Jira boards and where they (their little team) are headed. We talked a little bit about Jira (code specific projects) vs Trello boards (more of a general project management tool). Currently Chuck and Russell are leaning more towards the Jira side of things.

We went over some standards on the naming conventions and what the goals are there. Lots of different flavors out there. We are trying to help create our own style within our small development family. Even that can be challenging at times. Lots of cooks in the kitchen.

About half way through, we switched over to WanderWays and Marisa joined us on the GoToMeeting session. Marisa had created a small customer facing reservation tick list document and we went over that (see attached). We talked about reservation alerts and notices, date selection and number of day calculations, searching, selecting, confirming, and doing money stuff (checkout and putting down deposits). We also talked about hidden timers for active carts and other show/hide settings.

Lot of talk about mobile friendly layout and web page flow processes. Both Chuck and Marisa make a great team. I'm there as a sounding board and to add some ideas, but it is mostly them and their ideas and skills. Good stuff.

We did a back and forth work session. We pushed a number of new changes to the special employee, vendor, or guest (customer/patient) temperature scan and check system. This is some custom code that Bryan and Chuck and Steve have been working on (Covid-19 and employee temperature stuff). Anyways, we made some changes, pushed up some code and made some progress there. The site is now live and the client can start doing some preliminary testing and playing around.

Chuck joined the meeting and gave a report. He will be sending me some code to go over and check (read and proofread). It is dealing with a project that he is calling the adilas docs or internal documentation - code sign-off stuff, naming convention for code work, database stuff, and other company practices. Trying to get things standardized and help as we move forward. Other than that, we just chatted and touched base on a few things.

Part way through, Bryan jumped on and we worked on some code and projects.

9/24/20:

Three settings they can choose.

1) Do you want an age prompt?  use_age_prompt (tiny int) default 0

2) What age do you want to put there?  age_prompt_value (int) default 21

3) What is the verbiage? age_prompt_text var char 255 default null

**Check in with Brandon here if you have questions on the database syntax.

Shows up before you enter the site. Front end landing. (flash page or opening screen)

Monitor a session variable that shows the user has approval and they don't need it every time. The modal automatically needs to come up. Possibly part of a header or footer so it's included on every page.

In order to get past this, they need to say yes, I'm 21. 

Ask Russell or Chuck for help on modals. 

Setting needs to go on e-commerce page. https://data0.adilas.biz/top_secret/secure/ecommerce_home.cfm

Make setting 1.24 for the settings. Also add descriptions next to the settings.

cfc search 15 is where the e-commerce settings are.

Search for getEcommerceSettings. that is where we pull them all from. Currently in the corporations table.

Here is a page to check: update_20140102.cfm If you go here and search for this: newCorpSettings

Next you need to be able to pull it, add it, update it, and that it goes to the correct spot (header/footer)

Once this can be done, meet with Brandon for a code review.

7/6/2020: See quote for details.

Nice little meeting between Steve, Cory, Russell, and myself. The main goal of the meeting was how and what priorities we have for Russell and his team for the next few weeks. They, some of Russell's team are in between schooling stuff and doing a small sprint for the summer months. Here are some of my notes from the meeting today.

- We went back and forth on cutting out or adding in the new cart stuff. We ended up cutting out the new invoice homepage to substitute in work on the general cart project. We know that it may not be fully done by end of summer. Small time frame but we know that we need it - eventually.

- Some of the other projects are: new invoice homepage, roles and user permissions, corp-wide settings, header/footer session values, etc.

- Russell spends a lot of time prepping the vision of where we are headed and where we are going.

- Lots of talk between the new invoice homepage and the shopping cart. We hit this subject multiple times. As some side notes, if we do the invoice homepage, we would also want to add new graphical homepages for expense/receipts, PO's, deposits, etc. Kind of a suite of graphical homepages.

- Alan's name kept coming up due to skill level and deeper tasks. He is one of the main assets and everybody wants his help.

- When it comes to time... it feels like there is a pull to either be a developer and doing development or being a project manager and helping others. It is really tough to be both at an effective level. It seems like a choice - either development or project management.

- We are seeing three new carts coming into play soon - Spencer - one-pager quick cart, Jonathan Wells and Kelly - smart cart - industry specific, and Russell - new generic and configurable cart.

- We are heading more and more toward mobile friendly designs.

- Keep moving the core system along. We want to keep working where our clients will be - help them by keeping the ball moving forward in a good and positive direction.

- There were some talks about help files and splitting things up. This could be smaller help files or actually making them more in-line where needed. Ideas about pulling them more into the page flow and showing things just in time, as needed.

- Education mode, videos, helping our users with smaller, in-line help, and options. This could even include tech support and online chat, per page.

- Use technology to keep solving the problems that keep coming up.

- Ideally, keep finding predictive ways of responding to needs.

- We were talking about Russell's small team of developers and options for them once Russell goes back to school. There will be projects enough and to spare... Keep honing in on their talents and skills. Let them run where they can. Good stuff.

- There was quite a bit of talk about smaller redesign projects and lots of form fields and in-line validation stuff. We could gain or get a lot of mileage by doing some small tweaks to the layout and forms, including in-line form validation stuff.

- Chuck could even teach a class on doing in-line form validation to help the other developers.

- We now have access to page level JavaScript and custom JavaScript per page. This is one of the new changes based on the projects that Russell and his team have already produced this summer.

- One of Russell's favorite things is dreaming it up and then really making it happen and function like we were dreaming. That is awesome! Real-time problem solving.

- Everything is heading to customizable and configurable - out of the box - that's where we are headed.

Emails and prep work on the adilas presentation gallery outline. Trying to get it ready to send off to Chuck to work on the web site for the presentation gallery.

Quick meeting with Chuck. He has been out doing other things for a while. Just getting back into the swing of things. Touching base on a number of projects. I sent him a copy of the presentation gallery outline. He is mostly working with Russell, Marisa, and small projects for me.

After we finished, I worked on converting the presentation gallery outline into a PDF to put it on the web.

Web link - adilas_presentation_gallery.pdf - presentation gallery outline flyer

We also added a link to the online glossary to help other users.

Web link - time_web_gallery.cfm?corp=371&id=4030 - online glossary link

Marisa, Chuck, Cory, Steve, Sean, and myself were all on a meeting to get back into the WanderWays project. The primary focus was dealing with online scheduling of campsites, trailer/RV sites, cabins and what not. We already have a bunch of work done on the backend WanderWays tool (camp adilas project). We also have a ton of the frontend advertising website done. This next phase is dealing with an ecommerce or customer facing frontend tool. It will combine company websites, online reservations and bookings, ecommerce, and other frontend or front facing web stuff.

Chuck and Marisa were leading out on this project. That is great. Sean was new to this topic, so we did some introductions. Here are some random notes that I took:

- Using iFrames to embed the native sites into outside company web sites

- Chuck has a vision of what he is trying to build and make. We support that vision. Marisa is the inside person who has the knowledge in that area.

- Lots of talk about frontend set-up and customer type settings. We want to make a general tool that could be skinned and/or configured for certain industries. We just mentioned a few... think about auto shops, maintenance things, campgrounds, RV/trailer sites, cabin rentals, ski schools, rafting companies, adventure trips, sport lessons, etc.

- Going back to camping and campgrounds, being able to pick a site vs assigning sites on the fly - different companies like to do it differently - also some like to limit what the customer frontend or front facing app does vs the backend tools. That sounds like settings.

- Lots of talk about being able to shuffle things around. Including invoices, elements of time, locations, payments, and other relationships. Once we have all of the data, we need to be able to shift or shuffle things around.

- Marisa and Chuck are going to make up a number of scenarios and then go through the different options together.

- Dealing with the waiting lists and/or virtual queue type functionality. We need to detail out the waiting list functionality in a deeper way.

- We linked to some of the older notes - click here for details - dealing with rough numbers and budgets.

- Talking about funding sources and making a good and solid product. There was also some talk about making an MVP (minimal viable product) and/or an MVP+ (plus or slightly above a minimal)

- Treating the development and developers and founders as family - setting up good communications and scheduling bi-weekly meetings and demos. Steve talked a lot about breaking things up into smaller pieces to get some smaller chunks and good deliverables.

- The pace (running rate) is going to be increasing on this project. We want to keep it going forward.

- Making the plan and reporting to who is paying the bills (internal, adilas, or outside investors/contributors) - basically, return and report type concept. Let's see where it goes.

Chuck and I met and went over a bunch of things. I authorized him to go back to a 40 hour max week. We also set some priorities as:
1. Helping out Russell with some of the Snow Owl projects (timeline - this Summer)
2. Working on the WanderWays site - (timeline is ongoing)
3. New adilas SOP (standard operating procedures) and internal docs
4. Working on the presentation gallery outline and visual webpage to be used as a sales tool.

After going over some of that stuff, we flipped and he showed me some of the progress on the new user/employee homepage look and feel.

12.65 hours as of 2/3/21 for JM

Transition from Full Circle to Adilas Phones. Bryan is doing some of the coding and Chuck is going to be working on a small logo.

Talking to developers over the phone. On the phone with Calvin going over things. Then on the phone with Russell and Chuck to help out with payee/user images on the new user homepage. I ended up on a quick Zoom meeting with Russell and Chuck.

Chuck and I met to go over his current projects. We talked about the customer facing website for WanderWays (camp adilas project), colors and settings, being able to book generic sites for a category vs booking individual actual sites, and other customer reservation screens and processes. Chuck is making great progress. Next week, I'll grab some screenshots. I forgot until we got most of the way through his report.

Lots of talk about data driven toggles and other settings. Some of his new development is in what are called CSS/HTML cards and they will play right into toggle on/off settings. Kinda cool because the design is going to be prebuilt to match the settings. That will make it easier to code.

Chuck was also showing me some mock-ups that were in plain vanilla vs a skinned or mocked up version (tons of colors, logos, and deep look and feel). Seeing both the vanilla and the skinned versions help you see what was important vs just the visual look and feel.

We also spent some time looking over his internal docs and SOP's project (standard operating procedures). Things are looking good and this project will help us standardize things, including billing, checks, payments, code sign-off, style guides, and other internal docs and such.

Russell and I were going to be meeting and going over projects and code. However, we switched gears and invited Chuck to join us and we did a small session on some vision for what we want our company to be and what kind of culture we would like. The notes below come from both a meeting with Chuck and Russell, as well as a meeting with Shannon to go over what these two had said. This is somewhat of a mix, but good stuff.

- From Russell and Chuck - What they want and/or are looking for:

- Group of people that we trust

- Able to express their ideas

- Big system - virtual floating orbital system/engine (see attached for a drawing from Russell) - Think of a floating city where there is enough room to build and build and each person could carve out their own space. Having said that, the whole (floating platform or city) is run off of a dynamic core engine and/or core structure. Once again, see the drawing.

- Each person could be as big as they wanted to be

- Platform

- Independent model

- Build what you want but help support the core or the core principles

- Feed yourself type model - this doesn't mean that you don't ever need help... it just means that you are a self starter and willing to work

- Incentives and benefits or year-end bonuses - health care, sick pay, vacation pay, new hardware, etc. Originally thinking bigger numbers like: $10K/per person >> 10 people on the team = $100K (original thoughts) - (stepping stones or later thoughts) $1K or $2K/per person >> 10 people on the team = $20K (after thoughts)

- Keep the freedom but also provide some of the other incentives that help keep people around - retention of good people

- Dreams... having dreams and being able to act on them... - From Chris Jonnie - We support people with dreams

- From Shannon - Almost like each person has their own freedom to run their own business, but they have the support and security of a small community - a fusion between owning and operating your own business and being an employee at the same time.

- Family comes first

- The guys liked that there was a limit to hours... just dealing with direct billing - you could still do your own thing - this includes management in the limit on hours per week. Stay in that healthy and maintainable realm - less burnout.

- Residual pay and reoccurring revenue

- For Steve - in order to help him - Question - How can we help to split your work load? - Maybe even doing a project to help with that.

- Sales - You've got to believe in it - what you are selling - Shannon and I were talking... Think about dad... he really believes in what he is pushing- He can pass on the excitement and the energy - even if it isn't quite soo cool (funny stories)

- Seeing a need or opportunity and being able to jump in you want to

- They loved - being able to think of something and then build a product or service or solution to match - still playing right along that platform type model - adilas creates all kinds of byproducts and byservices (pretend that is a new word).

- Training and keeping that model going... Maybe something like - work 10 hours, be able to do 1 hour of training. So, if you work 30 hours a week, that would be 3 hours of training that you could do. Keeping up on the new technologies - lots of self improvement options - all of these things build value.

- Our platform or our framework - some ownership or skin in the game

- Shannon and I - how can we focus on different places (departments or areas of need) within the adilas jelly fish model? - See the need and then help to point people in that correct direction - delegation at the bigger picture level

- Going back to helping Steve - how can we help pull some pieces off of him so that we don't burn him out. He is one of our greatest assets.

Shannon and I were bouncing over some notes from an earlier meeting with Chuck and Russell. See this entry for those notes.

Eric checked in about 3rd party solutions and helping clients transition over to our internal solutions.

Small summary of the concepts in the other notes: The power of ideas and dreams, building together off of a common business platform, giving back, incentives to be a part of the family/community, freedom, family, limits, reoccurring payments and revenue, sales, building solutions, training, and helping Steve lighten his load.

To start out with, Chuck and I were on by ourselves at the beginning. We went over some settings and ways to configure some of the email options from inside of adilas. After that, Chuck reported on some of his current projects.

The later half of the meeting was somewhat of a group meeting. We had Russell, Alan, Chuck, Wayne, and myself on the meeting. The subject was dealing with internal documents and what is needed, wanted, and required. We covered code sign-off, frontend style guides, backend suggestions, and other protocols. Alan is going to produce a document dealing with the backend and database access structure. This will end up having outlines of our framework and dealing with pages calling services and services calling DAO's (database access objects) and those DAO's reporting back to the services and then back to the pages.

Wayne and Chuck (combo) will be creating and producing some test driven design docs and processes. Wayne requested Chuck's help to help with the actual writing and verbage. Wayne will show Chuck and Chuck will do the technical writing stuff.

See attached for a copy of some older work on some code sign-off ideas. This is more of a flavor vs a hard fast set of rules.

All 5 of us stayed on the call from the earlier adilas docs meeting (Wayne, Alan, Chuck, Russell, and myself). We switched gears and talked more about where we are headed and how that road will look. These are some of my notes and thoughts:

- We are not trying to redo all of the backend coding docs. We'll leave that up to the companies that provide the coding options and editors. We will however, do our own overviews and best practices docs and procedures and protocols.

- Dealing with training and internal documents, we want to follow a self-serve type model where the docs exists, a user or person may get to those resources at any time, and we have a standard place where they would look. That makes it so that they are not waiting for some other person or individual.

- Chuck is looking for content and will be flexible to add in the different pieces that we need, even if we don't know what those pieces are right now. A work in progress.

- Chuck can rewrite things and stuff as needed. He has some technical writing skills and a good background for that.

- We talked about using humor and how the use of humor in tech docs really helps (in the right places).

- We changed over to business models and how a trust might look and/or be setup. Wayne had some really good information about this. Wayne just got finished working for a ESOP trust in his old company and had some great insight on how that all works. An ESOP is an employee stock ownership plan. Just google ESOP trust and you will get some good info.

- After talking about the trust stuff, we switched over to some new code that Wayne is introducing and working on. The older model of ColdFusion (our backend programming or scripting language) uses a thing called an Application.cfm file. This was an auto include file where certain application or server wide variables were set and managed. The newer and more modern approach is using a thing called the Application.cfc (notice the small file extension change from .cfm to .cfc). The .cfc is a component or small library of preset and user defined functions. It allows for spanning, bridging, and extending classes and object oriented options vs the older A-Z linear code set of the .cfm files.

- We also talked about some new config files that will help the application switch between test and live without looking at the database and also how we are prepping the field to allow more than one site per server. Currently, the code just allows one site per server and just one main database connection. Where we are headed is allowing one server to be clustered (multiple servers doing the same thing), multiple sites per server if needed, and all kinds of other custom or special configuration. Lots of use of JSON (javascript object notation) files to help store and setup the config files for sites, servers, and even custom settings. Good stuff.

Meeting with Chuck over a GoToMeeting session. We touched base and he reported on a few projects that he is working on. One of the projects is a new payee/user profile page and add/edit payee info page. The new page will also have roles, permissions, tabs, and sleek new interface. It is looking good. He and Russell are working on the new pages.

We then switched over the adilas docs project. Chuck is currently working on some of the code snippets, examples, and style guides. As part of the coding conventions, he is proposing that we use some special characters in our comments to mean certain things. For example: An at sign "@" means a section heading or top level indicator. The double pounds "##" indicate a sub section or sub topic. An exclamation point "!" means caution and/or possible problem. The keywords "TODO" indicate a to do list item. Before we launch things, we need to resolve all exclamations and to do list items. I thought it was a good idea.

Chuck would really like to help us stabilize and standardize our coding, including whitespaces and indenting. Each developer has their own style. The more we can come together, the better it will be later on as each of us will end up working on each others projects.

As our last topic, we went over some our our current priorities and where Chuck is focusing. We have helping Russell with some of the new snow owl layout changes, WanderWays, the adilas docs project, and the presentation gallery and sales tools. Those are Chuck's current priorities.

8/24/2020: Project would require graphic mockup by Charles (roughly 8hrs). Turn to code- new data base table. Would be able to record data and add, edit and view.

Roughly 35 hours. 

Chuck and I had to meet a little bit later today. He was having Internet problems. We started out and he showed me some of the stuff that he and Russell are working on. They are revamping the whole user/payee/employee profile section. This includes a new layout, changes for permissions, and the addition of roles and templates for users and permission. It is looking good.

We also talked a little bit about the WanderWays project and how we approached it. We did some mock-ups, did some coding on the frontend, did a customer facing website, and then some other pieces. We basically ran out of money before we could really get it all wired up. It is still going, but we had to slow down on it. Anyways, we talked about that approach - the older way being what we already did, and we also talked about some new options and approach strategies. Good ideas and conversation. One of the key pieces was spending more time on the frontend to really show the product in a virtual working mock-up type prototype in order to get better buy in for the whole project. Basically, build out the full concept to see if you get more takers (meaning people wanting to own and/or fund the project further). We are constantly exploring our realm... just like pioneers.

At the end, Chuck and I went over some our priorities and projects that are in front of us. We also spent some time and just chatted about life and being well rounded, in general.

Chuck and I met and chatted for about an hour. We covered a bunch of different topics. No special order, but here were a few of the topics:

- Decisions of a leader to get out of the way to let things happen in a better manner. Sometimes that is hard.

- Report on WanderWays (camp adilas) project - see the screenshots and this link for more info: Web link - Adobe XD file

- Report on the adilas docs (internal how to manuals and style guides for developers and designers). See these links for more info: Web link - adilas-docs-home.html and Web link - core-components.html

- Full stack developers vs small teams and virtual departments to get the job done.

- We also talked about cannabis vs other business verticals. There are many of us who would like to explore other options and business verticals. WanderWays is a venture into one of those realms.

GoToMeeting session with Chuck. We went over some of his existing projects and I got updates on each one. He is still working on the adilas style guide - backend document for adilas developers and designers. He is still chipping away at the WanderWays (camp adilas) project. We also talked a bit about the presentation gallery or sales tool that we started a few months ago. We also talked briefly about bills and invoices. Good little report.

Meeting with Chuck to going over projects and what not. We talked about some changes to the WordPress stuff that we need (updates, back-ups, and new pro level theme headers). We also went over some of the adilas docs project that he is working on as well as some of his JavaScript training that he is working on. We are seeing more and more needs in the JavaScript developers role. Very marketable skill set.

Emails and working on a fix for the photo upload API socket. Added in the outbound photo name and special corp-specific path name. Pushed up some new files.

I got a link from Cory dealing with Flash and end of life stuff. Soooo sad! I really liked Flash.Web link - upsidelearning.com

Web link - adilas-docs-home.html

Emails and checking out Chuck's new changes and small video on the adilas docs (SOP's - standard operating procedures) for adilas. This includes meetings, code conventions, style guides, etc. The current adilas docs can be found here:

http://adilasdocs.swanhaven.co/adilas-docs-home.html

Also worked on some prep stuff for the Bear 100 mile race. They use adilas and will be running their event this coming weekend.

Chuck let me know that he wouldn't be on the meeting today. He is dealing with some moving stuff.

I spent the time working on new tweaks for the Bear 100 race. Custom code for the rolling start and new finish line queries.

A couple of the guys joined the morning meeting. The general topic was sales. We had Steve, Sean, Eric, and myself on the meeting. Steve is really trying to get the sales engine started up and going. We have a bunch of things circling around, just need some of those things to fall into place.

We talked about using Chuck in sales and redesigns of certain pages and flow. Eric brought up the need to convert some of our Flash modules into HTML5 or JavaScript. We know about that, but still haven't figured out what to do there. There is a constant need for more refinement and development.

As a company, we give a lot away for free. It could be consulting, custom code, design work, training, systems, upgrades, server stuff, or whatever. If that starts becoming required (meaning our clients expect those handouts), we end up losing the battle. We have to charge for our time and efforts. I am as guilty as anyone else. I love to see things happen, I'm not really good at numbers and business decisions. Eventually, we have to bring in more money than we are spending and burning. The old earn and burn ratio. It's part of business.

I think that both Steve and I really need some help, it's a hard burden to bear.

Wayne came on right around 10 am. We spent the next 30 minutes going over a bunch of things with Wayne. He is taking the servers to the whole next level. He is doing a great job. We went over some of his new fusion reactor stuff (adobe coldfusion monitoring), pingdom (web stats company), tracking server errors, code debugging, and talking about billing and support from our hosting companies.

We got into some discussions on ColdFusion mappings to help with revolving paths and variables in those path structures. We may end up looking more into this.

Finally, we had a small discussion about taking time for self and family. Important things.

We have Chuck, Danny, Steve, Sean, and I on the meeting to talk about gun shops, gun shooting ranges, and other business verticals. We have a big shooting range in Arizona that has been using our system since February 2014. We made some plans to contact them and setup a meeting to see what else they could use and/or would like to add. Just trying to find as many different angles as we can.

Towards the end, it was just Chuck and I left on the meeting. We ended up talking about operations and accounting and how you have to have the horse (operations) in front of the cart (accounting) and how that all works. Light training and chatting about options.

Met with Chuck to go over things. We covered a bunch of his projects. We talked about the adilas docs (style guide, coding conventions, and expectations) project and did a little bit of work there. We went over some new WordPress theme changes and what that is going to look like. We use WordPress for our news and updates. We are going to make plan to launch those new pieces. We also talked about a raise for Chuck. That goes into effect on 10/1/20. Good stuff. The other topic was adilas financials and where things are going and/or heading.

As of 2/3/21: $4984

10/5/2020: Created for Charles billing for templates

See sub notes for more details.

Meeting with some of the guys to go over new needs for the gun company and what they are calling templates. Basically, paperwork and processes that they need. Here is a link from Chuck with a couple quick concepts and ideas.

Web link - Adobe XD file - couple of pages for concepting flow

Other notes may be found by looking here (time_web_gallery.cfm?corp=22&id=1880) - look at the sub notes on this other entry.

Danny had a couple of gun range users on a call. We had a number of guys on the call. We had Steve, Brandon, Chuck, Danny, and Sean. These are some of the notes from the meeting. Danny had the couple on speaker phone and the rest of use were on the GoToMeeting session.

- They bought the gun range from a client who had 5 years of data.

- The whole adilas system is built on a web or web page type format.

- Some things that they would like is: sell a gun, add a member, schedule a lesson.

- They do use payroll - but they need a split rate for their employees

- They are looking for industry specific forms

- They need reoccurring invoicing - we have this - and they have multiple merchant accounts

- Text and form fields vs a simplified work flow

- They used to use adilas to help with waivers but it seemed to be a bottle neck

- Lots of typing. They want to use a driver license scan.

- In the sales process, it asks for the driver license and that should already be in the customer record

- They can tell that adilas has a powerful database backend, but they are looking for a simple work flow - aka a big button to do a task

- It would be nice if things were tracked from the manufacture

- On there inventory, they are running full vendor specific stuff where they could be using a more generic inventory

- They have a lot of paperwork that need to be online.

- They need lane use and scheduling.

- They feel like they have a number of different businesses running all under one roof. Retail sales, gun range, lessons, plus normal business stuff.

- They do like having all of the reports and data, but feel that most of it too complicated.

- They would like to have different modules that would be easy to turn on/off and hide/show those pieces as needed.

- They may be missing some training - a bunch of the pieces that they need are there but they may be missing some training.

- On payroll - they really need some split rates. They have to setup different departments and then they don't pull together to calculate overtime correctly due to the different rates.

- Training, training, training. They are making complaints that totally exist but they don't know how to use them.

- On the bottom of the calendar... they like the next month, last month buttons but they only go to the physical next or previous month. They want it to be fully go as far as needed.

- Pricing - They have seen big prices like $14K or $500/month.

- Lots of the ranges have tried tons of different software systems. Nobody seems super happy with their full products.

- There were some complaints about having to do things one way and then add that info into adilas after the fact. They would love to see things more streamlined.

- Go to the Las Vegas trade show in June - they saw 6+ vendors pitching their products. The show is huge.

- They would like built in online scheduling, directly from their website, with full merchant processing. All doable, but not out of the box currently.

- There are only about 20 main distributors in the gun market. They, the distributor, seem to want to share their product catalogs and inventory lists.

- They would love to get info from the distributor vs having to enter their own info for every gun. Lots of different makes, models, and small tweaks to what each gun has.

- They have 8 lanes. They had to close 3 due to Covid-19. That creates a huge wait and higher pressure. They really want online booking for their lanes.

- Each business needs stuff catered to their specific business model and industry. We are very general and it works, but they are really looking for an industry specific solution.

- We keep hearing this... training and training - they were talking about problems between splitting an invoice between a credit card and cash. That is built-in, but they don't know how to use it. As a side note, some of that training and lack of training deals with a breakdown on the communication channels.

- Steve jumped in and said that we are committed to making it easier and more user friendly. We would like to service specific industries and thus being willing to work directly with end users and persons who are in the know for their industry.

- Things keep changing - things that they want, keep being developed but not being communicated back to them.

- On the reoccurring billing, they want the full thing. The invoice, the payment, the full processing, the whole nine yards. They kept talking about similar to a guy membership where it auto charges, auto bills, auto everything. Once again, the full cycle. We have all of the pieces, but there is a small part of that process that is still manual.

- They do like the membership end date functionality that shows up in red if they are expired.

- They have membership cards and want to be able to scan those and make sure that it pulls up the correct customer. They said that it used to work, but now it doesn't work. We would have to see what it scans and then make sure that it coded into the system.

- They had major pain one day when adilas was down... they had to handwrite 250 tickets. That was terrible. They really need good up time.

- They have a new range software package. It took the other company about 2 months to get it all installed and configured.

- The amount of time is limited that they have to instruct and help their customers. They want it almost so intuitive that no instruction is needed.

- Trade-ins, verbage, and making things simpler. The naming convention doesn't tell them what it will do. Some examples are: system maintenance, system assets, elements of time, etc. They want it to say, sell a gun, add a member, schedule a lesson.

- Less typing - more scanning - more clicking (within reason). Minimal on the typing. Just for fun... they have to type in crazy names with screens, masks on, and other crazy Covid-19 type stuff. It just makes it tough.

- On memberships... They love that all of the carts are tied to customers and we track all of that data. However, if they sell a membership, they want it to auto add and update the correct fields and values.

- They seem to skip the news and updates - they are on a mission doing the task at hand.

- They like the high-tech toys.

- Getting the developers to get some immersion into the real business model and the style of what is going on. Aka - what is really going on and how should it flow in real life? Getting the developers out in the field more (exposure to the end user side of the puzzle). They called it immersion. Finding and solving the pain points.

- We may come out and visit their shop and their range. That would really help all parties involved. Steve, Danny, Chuck are all volunteering.

- Some of the other software platforms aren't deep enough or don't do enough. They can see how if we change the frontend of adilas, it could really handle most of the needs.

- Guns are a fear-based business. News, elections, crazy times, all of those things drive sales. Their industry is really pyrenoid on giving out personal info - the government may come after them.

- Being able to scale... sure we can do it once or a couple of times, but can we do this for hundreds and hundreds per day.

- Quick fixes like being able to scan the driver license or enter a phone number from a 10-key, etc. Things that already exist but need to be surfaced better. Steve was mentioning a new gun range homepage and/or interface.

- Let's keep the communication lines open. Reach out to Danny. danny@adilas.biz

- Steve was talking about both form and function. Let's get it going. He was talking about even some quick changes like a new custom homepage for gun ranges. Task based buttons and quick access to underlying functionality. Add some quick options that they will use.

We got together and chatted about projects. Chuck was on an earlier meeting today with a client. He reported on that and needs of the client. They have lots of paperwork and need to track certain processes. We talked about two other projects that Chuck is working on. We are almost finished with the adilas docs project that shows coding conventions, style guides, and common processes and procedures that we do inside of adilas. The other project that he is working on right now is the update on the news and updates and WordPress stuff. He, Wayne, and I will be getting things pushed up and scheduled here in the next couple of days to finish up that project.

The last thing we talked about was Chuck helping Steve, Sean, and Danny with the sales and marketing stuff. Lots of options there and we are making progress. Good stuff.

After our meeting, I went back to recording notes from earlier in the week. Kinda behind on recording the other meeting notes.

Early start this morning. We are going to be doing some maintenance on the news and updates pages. Chuck is installing some new WordPress themes and changes. Wayne and I are helping with different pieces. I spent the first little bit today working on a news and updates bypass so that Chuck wouldn't have too much traffic as he is making updates and changes.

After that, I spent a good couple of hours working on a custom data upload for a company. The upload was for their parts and item inventory. The upload did a special loop and check for certain parent attributes and web long descriptions. All of these pieces are used outside in ecommerce. The company is using an outside 3rd party to show their inventory and then using adilas API sockets to pass data back and forth. Kinda of a custom wire job. Anyways, about 2.25 hours working on the new CSV data upload options and logic. Very custom with lots of error handling and clean-up built in.

Chuck and I jumped on a GoToMeeting session. I was having audio issues with my computer. We ended up on a phone call and using GoToMeeting to show screens. Chuck is working on some news and update WordPress updates today. He also reported on some custom registration stuff for a client. We will try to wire those new pages up tomorrow. Somewhat of a quick touch base and report.

After that, I spent the rest of the time working on my audio connections for GoToMeeting.

Emails, news and updates stuff, and recording notes. On the phone with Chuck going over next steps on the WordPress news and update changes.

Danny, Sean, and Steve were on the meeting when I joined this morning. They were talking and touching base on things. I was doing emails and trying to get caught up with small to do list stuff. Here are a few notes that I gleaned just from listening.

- Keep building and connecting the pieces - take the next logical step.

- The deeper we go, the more we are seeing elements of time being an underlying foundation or under weaving of almost everything we are doing. Maybe keep exposing that and building towards that. We've always know it was there (foundation of events and objects over time) but maybe keep pushing that connection and foundation piece.

- Have the attitude, let's figure it out. We keep getting hit with more and more questions, what if's, wouldn't it be cool if's... etc. Well, let's figure it out!

- If you find the pain, then look at the tools that you have, and build a solution to fit.

After that, we changed course and started to talk about a project with a gun manufacture. They need to track gun registrations and RMA (return merchandise authorization) stuff. We invited Chuck on to the meeting and took a bunch of great notes. See attached.

- In this meeting, there was a lot of talk about the data assembly line concepts and how it would be super cool if we could do the limited flex grid type approach for flex grid as well as elements of time. Imagine a small and simple form with only a couple of key values, you submit it, and the next time you need to do something (say another phase or process), the small and simple form could keep track of where you are at and only show you the new limited fields that you needed. That would be so cool. Almost a generic process or phase builder. You pick what you need at what phase and then as you walk through the phase, you only get presented what you really need at that time. That concept may be worth exploring more. Think data assembly line for data, based on settings, templates, phases, and underlying processes (tasks to do and/or record). Simple, step-by-step processes with a powerful and dynamic backend so that the frontend looks super simple (trained monkey could do it - in theory). That would be pretty cool.

Chuck and I got on a meeting and worked on first round wire-up stuff for the SAR USA firearms registration page. He had already prepped the main form page. We are passing it on to a ColdFusion page (logic and validation) and then into the database. Working with Chuck on the process.

Chuck and I did a two hour wire-up session on the gun/firearm stuff for Bill (a client). The main part of the session was training on database interactions and using ColdFusion cfc's and methods. Making progress.

Alan checked in part way through and showed me some new code for some sub invoice and sub quote functionality. It is crazy to see how everything keeps going deeper and deeper into subs. We also briefly talked about servers and security stuff.

Alan joined while Chuck and I were working. Quick check in and chatting about current and upcoming projects.

Work session with Chuck. We were working on the gun registration wire-up job for a client. This is where their customers go in and fill out an online form and we then suck that info into the database through a custom wire-up job. Most of the session today was error handling, and making decisions on what to do in certain scenarios and/or use cases. Lots of training while doing the project.

Chuck joined at 11 and waited until around 11:30 am until we finished our other meeting and server security talks.

Once we got going, Chuck and I worked on a custom wire-up job that deals with adding a message page and custom validation to a simple form for doing a gun registration. We ended up getting rid of all of our prior validation and substituted it for our new custom tags and deeper validation routines. Good stuff and all part of the learning curve.

Chuck did some light training for Danny and I on popup modals and what is already available through our current CSS and project themes (bootstrap libraries and themes). After that, Danny left and it was just Chuck and I. We turned over to flex grid tie-in training and talked about how we were going to be using flex grid in our gun registration project. We then prepped his local environment and then coded or did a wire-up job from his custom gun registration page into full on customer records with associated flex grid tie-ins for his customer fields that were needed. It's not super tight yet, but he is getting the concepts and I hope that he is enjoying the custom wire-up training that we are doing. I'm hoping that it will help him later on when he is doing more frontend stuff and having at least, a knowledge of how we do the wire-ups after the facts. I think that it is going pretty well.

Here is a small help file that helps talk about concepts of what the flex grid is able to do (click here).

Working with Chuck on the flex grid wire-up job for the gun registration pages. We also did some light review on some of the other code that we were working on. Work/training session.

Chuck and I were working on the custom wire job to help with the gun registration page for a new client. We worked on some error messages, updating comments and notes in the database, and general overview of what we've got done so far. Good wire up training project. The project involves a custom form, validation, checking for existing records, and adding and editing registration results (including flex grid tie-in stuff). We should only have about an hour left to finish up this first round. Getting close.

Chuck and I met and went over some things. We talked about JavaScript and JQuery and some upcoming needs there. Chuck has been working on some new headers and footers for the SAR USA firearms registration pages. He is also working with Russell and Alan to get the AJAX photo upload piece working for the registration page. Good stuff.

Emails, recording notes, and talking with Sean and Chuck about flex grid tie-ins for a client. General stuff.

Lots of emails. Chuck joined me around 2 pm. We worked on uploading an image (customer receipt) for the firearm registration page. We used the customer photo gallery pages as a sample and coded his custom pages using pieces from the existing customer photo gallery.

Met with Bryan for half an hour. He is working on some API sockets and trying to connect to some local software for EMV chip reading technology. We talked about some options and also put up some warnings as to not get too far off the path. Some of it looks deep or specific to Windows software developers (bridges between web and Windows operating systems).

2 pm - meet with Chuck. We had a good meeting and filled in some gaps on the SAR USA gun or firearm registration page. We added some more JavaScript, showed prompts for uploading content, and got things ready for going live. We should be able to get it pushed live next session. That's exciting. Some of these projects are training projects for our guys. They could be done quicker, but learning takes longer, and hopefully the extra time pays off later on.

Great meeting between Chuck and I. We started out and did some debugging on some form validation and JavaScript stuff. We had to alter the way things happened and changed the order of events. We did some local testing and got his firearm registration form all prepped and ready to go live. We then pushed it up, merged in new code, and did the first live test. It went through perfectly, and we were both very happy. We even logged in and looked to see what it looked like inside of the site.

This is exciting. This is Chuck's first full wire job or custom write up. He built the landing page, the form, did all of the validation, and then we wired it up to an adilas backend database with both customer records and flex grid tie-ins. It also uploads photos and images (customer receipts) and ties things into the main customer record. Fun project. It was really fun to see him get it across the finish line. Success.

Going over option for inserting meta data in key pages. Danny was heading up a discussion about SEO (search engine optimization) with John M and myself. I was taking notes and the other guys were commenting and providing ideas and info. We started out with intellectual property and went from there. Here are the basic notes.

- IP - intellectual property - natural flood - you can't copyright or trademark or paten things that already exists... if we flood the area with prior art, that effectively prevents others from claiming things as their own intellectual property. Fun discussion about where we are headed. We are sharing to protect ourselves.

- SEO - buzz word - science and art of making things show up for searches and on search engines

- Seen and unseen - matching SEO content with real natural content - light talks about the history (good and bad) of SEO

- Marketing and getting a new website for adilas - we really want to get a good plan in place and then follow that plan - up until now, it has been a very natural progression that just sort of happens. We want to be more specific and deliberate on our efforts, messages, and marketing. It is time.

- We have a bunch of different levels - main website, secured content (SEO not needed - due to login and permissions), shop (ecommerce - a little bit more tricky), web/API sockets, and other pages and documentation.

- Web content - they virtually and really score your site based on responsive design (mobile ready), same domain name (traffic and visits), amount of time on that domain (frequency and length of time on certain sites), reciprocal links (who links to who), matching content (good natural content), etc. Going over the basics.

- Meta data - key words, buzz words, include photos and videos with built-in meta data

- Sometimes it is the little itty bitty things that help - small things but a lot of small things really start adding up - almost like a virtual score sheet

- We don't want to do anything that is sketchy... off canvas text, hidden things, tags and random content, etc. Play well and be honest.

- We want a main landing page and home base that deals with what adilas is and does (as a whole). This is not industry specific, but who and what are we.

- Animated story lines and time lines

- Some other links - see chat - elevator sales pitch, presentation gallery, outline, chuck's new sales tools, etc.

Web link - adilas_formula.pdf - adilas formula

Web link - time_web_gallery.cfm?corp=748&id=7089 - elevator pitch

Web link - adilas_presentation_gallery.pdf - presentation gallery outline

Web link - time_web_gallery.cfm?corp=748&id=6914 - internal questionnaire summaries (sill working on this - progress)

- Put Danny in charge of the team - pick a team, get a plan in place, set a budget, and help to roll things out.

- What do we want to sell and pitch? Up to this point, we have been pretty off the hip... we need a strategic plan as we go forward. It is time.

Emails and light clean-up.

Working with Chuck on a new purchase date field for his wire-up project for the firearms registration page. We added in a quick switch between test and live and coded a few other changes.

**Total for everyone 12/3/20 to 4/14/21: $13,837.34

3/18/21: 4.92
2/23/21: 2.83

12/21/2020: JM hours as of today: 10.31
11/25/2020: 

Chuck did a great job and checked in earlier when our original meeting was scheduled. John and I were still elbow deep in a bug fix so we couldn't meet. We ended up meeting in the afternoon. Chuck is working on a number of different projects. One of them is an RMA (return merchandise authorization) page/form for the gun/firearm dealer. It is looking good and we'll most likely be wiring it up this coming week. The design stuff is done already (mock-ups).

After that, we switched gears and talked about SEO (search engine optimization) and some ideas for a new web site. Chuck would like to use WordPress for the new site. He is quite good at WordPress sites. He is also doing some research on other sites that he likes and why they appeal to him. He showed me three sites. I didn't write them down, but here was the gist... good designs, simple yet elegant, power statements, solving problems for the consumer, removing risk, good content, good use of photos and icons, strategic use of motion/animation, targeted, simple, and enough push to help you sell things without being over the top.

Meeting with Chuck over GoToMeeting. We chatted about different projects and made some small tweaks to the firearm registration form (tied in the uploaded receipts to the correct gun registration). We talked about WordPress stuff and upcoming projects that may be dealing with WordPress connections and options. He is going to reach out to Wayne and make sure that all of the adilas WordPress stuff (news and updates) is fully working and functioning. Chuck also needed a quick refresher on doing a reimbursement for a service that he did for us (image optimization through an outside 3rd party tool). Good meeting.