all data is live and searchable
|
Basic Assignments
|
Options & Settings
|
Main Time Information
|
||||||||||||||||||||||
|
|
|
Blue
|
|
||||||
|
||||||
|
|
|
Notes:
|
|
-I have a plan! Review it, slow down, and focus. Work on specifics of that plan. Take the time to practice. Think about how you practice with a purpose for snowboarding. -The developers who can generate funds will help these who can’t. Once the stranger developers are ready, they can start doing independent jobs and projects. They could even start their own teams. -Take the developers on a round trip to meet with the rest of the adilas team. Have a team meeting and focus on our plan and where we are at on things. -Keep building out the customer facing pieces. This includes customer bill pay portal, eCommerce templates, front facing calendar, scheduling, media/content, web/API sockets, and eCommerce templates and black boxes. -On training and demos… Show real live people, where they are at, where they are headed, and a glimpse of the goal. Make it as real as possible. People can relate to that. A good example of that process is what we tried to do with Learn To Freeride. We used real people doing real tricks and moves at their level. We then did small video clips to help show progressions. -We want to build a house of bricks. A straw house is too easily blow down. That may take some time. -Use elements of time, photos, scans, media/content, and even the customer queue to help with adilas project management. -The customer queue is kind of like a big to do list… What if we added some code to make a system-wide template for a to-do list or project queue of sorts. We could allow some settings to be tweaked but maybe that would help people get their tasks and projects more organized. -The customer queue already has access from every page in the site… The mini calendar icon is another global access point. Elements of time and/or the customer queue would make a great combo. Make it easier to flow back and forth and between the queue and elements of time. -We had another request to mirror and/or make a back-up site available if the main servers go down. Mostly for parts, sales, and other mission critical pieces. As a side note… This could be a great 3rd part application that someone could charge for and develop. -Similar to the eCommerce and main view cart page, we need to add black boxes all around the site. -These black boxes could almost go to the level of open source with custom black box options. -The black boxes are virtually hooks or options to insert or add custom code. We are thinking about at least 4 custom access points per page. They would be – top or full takeover, css (cascading style sheets) box, top mini – under the header, and bottom mini – just above the bottom footer. Custom black box options: (please see scan in photo gallery) 1. Top or full take over 2. CSS 3. Top mini 4. Bottom mini A black box is where we put and/or access custom code per page. See notes on 2/5/15. Added two more for custom headers and footers. Our black box naming convention will be: (pretend that corp #77 is wanting custom code) 1. Top of full takeover – name_of_page_777.cfm 2. CSS – corp_css_777.css 3. Top mini – name_of_page_top_777.cfm 4. Bottom mini – name_of_page_bottom_777.cfm -Steve had the idea of being able to virtually “pin” the to-do list to the calendar and then let it float day to day. Just an idea. -Use the system to teach and show full cause and effects. Steve had the idea of showing a graphic of what is done and what is happening. Education and training as it happens. This may end up being a virtual watcher and/or feeder or sorts. -Get back to mapping and planning things out. That is a huge part of the game and/or puzzle. -Steve and I were talking and he said that he was taught a simple acronym of DIA. This acronym stood for: D = Delegate I = Inspect A = Approve -As we kept talking… We thought about ways of taking the DIA acronym and evolving it into the acronym of ADILAS. The word adilas is already an acronym of “all data is live and searchable”. We thought it might be fun to create a development cycle that used the letters that go with adilas. Here is what we came up with… still kind of rough… A – Acquire, Accept, Approve Requests D – Delegate to our team, Determine the scope, goals, budgets, and project management I – Inspect - microscope, details, inspect what you expect L – Love (you, them, us), logging & communication, learning A – Approve - clean up, upload, feedback S – Submit - close out project, push code up, bill, etc. |