Basic Assignments
 
Options & Settings
 
Main Time Information
Color Code: Green
Created By: Shannon Scoffield
Created Date/Time: 11/19/2014 10:03 am
 
Action Status: Blank (new)
Show On The Web: Yes - (public)
 
Time Id: 2886
Template/Type: Daily Tasks
Title/Caption: Daily Tasks
Start Date: 10/23/2014
Main Status: Active

click to enlarge - photo by: Shannon Scoffield -
click to enlarge - photo by: Shannon Scoffield -
click to enlarge - photo by: Shannon Scoffield -


Notes:
• Working with an intern to help make custom document assignments. Reskinning pieces to allow customers and clients to get to custom code.
• Demo with prospective clients. We covered eCommerce, CRM, flash demo, education module using flex grid, and talk about API sockets. They had questions about multi-level websites, duplicating pages and code, marketing and commissions, tracking promotions and referrals, and multi-level direct sales and commissions.
• Setting up an intern with PDF’s and custom documents.
• Phone call with Steve. See new brainstorming notes on the Microsoft Word document for sub inventory and cost controls (packaging). Lots of direction, depth, goals, and vision. Great session!
• Emails and phone calls. Helping an intern with his web/API documentation project.

• Working on the new database update page for discount settings. Also on the phone with another developer going over options on custom code, rules, and assignments. We talked a lot about the glove analogy or the black box analogy for handling custom code. Basically, each page has or will need a way of allowing custom code, logic, or custom output without hurting the main page or underlying structure. (Sketches – Black box analogy – page hooks or page sockets. Black box at the top & another black box just before the output.) The black box is a way of saying… Do you need to add something? It could be code, processes, or even output. We could do a simple include or pass through (no abort just a simple include) or we could run standalone code that would or could virtually take over. This could be done by adding an abort command at the end of the custom include page.)
• Working with an intern on some vision of the future. Lots of small drawings and chatting back and forth.
• New logo for a client.
• On the phone with a developer. We were going over the adilas main login procedure and how the different pieces play into the mix. Good session.