meeting with Russell, Steve, and Brandon on 12/31/18

////////////////////////////////////////////////////
small agenda items

- moving towards other products and other industries
	- Steve is looking to get into other industries
		- looking for companies trying to manage inventories and ecommerce
		- there may be some initial development to help some of these new industies

- share some ideas that Russell has been working on
	- cool tools
	- advances in tech
		- CSS variables
			- one style sheet with variables (top-level)
			- transparent widgets, non docked windows, one-pagers with db access through AJAX and JQuery
			- mini widgets and interfaces (maximize, full screen, resize, movable, non linked windows,
				 responsive, etc.)
		- web components - super dynamic css cards
		- CSS, permissions, AJAX, JQery, etc.
		- object oriented
		- bigger methods vs classes (mini getters and setters)
		- usage of different api sockets (ok to touch this... don't touch this or that)
		- web flow options (page builders and get the dynamic data from the system)
	- tags, flags, subs of subs
	- tons of custom code options
		- a standard core of functionality
		- each industry and/or user could then put the front end together
		- missing a master designer to help standardize things
		- processes and functions - being consistant

- receivables and header due dates (branches - ram-37 and bwm-33)
	- note - we have a date 11/6/18 on my post-it notes to get back to this
	- really close to done - review and go from there
	- bwm-33 is all done minus the final flip/flop
	- still need to merge and update all databases with the invoice due date
	- ram-37 needs bwm-33 finished first
	- ram-37 needs some logic pieces - it should have quite a few of the pieces already
	- as a note, if we change the due date (on the system or invoice side) it will give the company more time

- snow owl (template)
	- two tabs... the one you like and the new template - transfer things over to the new template
	- make it a default template and either force it for all
	- admin make and maintain templates, users may use them
	- there are even some tools to flip it per user

- ecommerce and allowing teired pricing to flow through

- what does the future look like?
	- what would Russell need time wise, monitarily, etc. - basically a small proposal on what would it take
	- potential team - Steve, Brandon, Russell, Alan, Wayne
	- plan it out
	- design phase (potentially hundreds of hours) - new core
	- building it out with plans, requirements, expectations, etc.
	- mock-ups, build-ups, documentation, prototyping, etc.