10/15/20
Steve and Sean talking with Chuck about SAR USA gun stuff

What is needed for the wire-up job

Brandon and Chuck will be working together on Monday afternoon

SAR is the importer

where it is right now...
	- three top categories or forks in the road (these would be buttons or main selections) - different channels
	- each of these branchs could fork or branch further
	- distributor
	- gun dealer
	- end user - current goal (starting place)
		- gun registration
			- we need a form for the user to fill out
			- where does that info go - basic info, firearm info (may be multiple)
				- main customer info and flex grid... we will go in and set it up
				- check for a customer - add or edit
				- maybe some log notes
				- tie extras into (limited) flex grid

what has been promised? it could be pretty open ended.

this could go on and on... we want to make sure that we take care of the gun registration and RMA (return merchandise authorization) stuff.

chuck has some other templates that have been passed to him. They are RMA form, parts form, service and parts forms.

we know that we may burn through some monies... doing things on our own vs fully paid by the clients

steve would love to create generic pages or forms that could be turned on/off so that we could offer these services to others - thinking along the lines of generic and dynamic forms and where they go (where the data ends up).

link in ecommerce - there are settings to turn pages (sections) on/off. steve is thinking that we could do more settings that allow us to be more dynamic. toggle things on/off, setup new pages, new pieces, as much as possible without having to talk to a developer. just some ideas... online scheduling, product registration, certain forms, etc.

there was some talks about the custom field settings stuff - we can rename, show/hide, require, alias, set defaults, show/hide on the web, etc. for main customer data fields. steve would like to keep extending this out to other sections and make sure it expands out to ecommerce.

once we build one... they always want more and/or be able to update things on their own. instead of developer (custom code) driven... making it more of a content management tool (CMS) where it becomes templates and then allowing clients to make changes and do small things for themselves (no developer is needed).

more dynamic - let the users (aka our clients) have the power to create, control, and virtually organize their forms, pages, graphics, verbage, flow, etc. also, where does that data go once submitted.

using elements of time as a backbone to track things behind the scenes

another side note... we have this thing called limited flex grid. we use it for beaver mountain. it would be so cool if it was more global (as tool). the concept of a simple form... could also be used for our end users to setup fields, forms, and simple things. Easy, simple, clean, and powerful. super simple.

on the limited flex grid... we would love to have a mode like simple and full (the old one)

the same concept deals with elements of time... could we put in a simple version... before the real one... similar to the limited flex grid. thinking along the data assembly line type concept.