Steve, Russell, and I met to talk about some business options. Russell has been working on some prototype code that he wanted to pitch to Steve and I. The new code is really cool, but not all the way finished. We talked about a number of the concepts and they will be great additions and could be the base for some of the fracture stuff that we are planning. Here are some of my notes.

- Russell really wants to take what we have and restructure it into a more cohesive core. We build and build and stack and stack. Some of what Russell wants to do is take all of that, and re-make it in such a way that it becomes more mobile and modular. Same type functions, just change the backend core pieces to work better in the future. See attached for a small diagram (drawing) to help illustrate the concept.

- Russell really wants to fix and patch the current ship as well as start building a new and faster ship on the side. Enlarge our fleet, in a way.

- We build and break, build and break. That's how we keep learning and growing.

- We want the adilas core to be 80% of what people need and use all the time. The other percentage will be industry specific code and custom code per corporation and/or business.

- At some point, we bump up against a few tougher obstacles such as volume (quantity of records or quantity of choices) and up against evolving tech. Those two things seem to be a common thread.

- Lots of talk about using web components. This is where we make a small mini widget and then use it over and over again. The little widget holds the code and the logic, we just pass data to it and it knows what to do. Some places where we want to do web components or something like that are: Movable pieces to set up your own flow or virtual data assembly line (think of the cards on a Trello board). Media/content libraries - be able to upload items and then use for multiple places vs just uploading the same thing over and over. We also want to add drag-n-drop functionality and our own version of the data tables. Russell has more info and ideas. There are things that will end up playing in the fracture interface.

- We talked about the value of being in the know and having experience to go along with that. Huge key.

- One-to-many and using shared libraries and media/content galleries and libraries. We already have some of that (media/content remote references) but we want to make it more visual and spread it out more across the system.

- Building and using some tech and pieces from other companies like WordPress and Trello (cards, boards, and that type of interface). WordPress is a pretty deep CMS (content management system). Lots of good ideas. We'll end up with our own flavor of sorts.

- We want to keep making the tool better, prettier, faster, and more powerful. In Russell's words - Easy, Pretty, Powerful.

- As a side note, I wanted to record a saying that Russell said back in 2016. "Adilas is a great companion software package for any business." (4/13/16)