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.