Enhancing Presentations: A Guide to Successful Meeting Planning
Table of Contents
1. Presentations
Review the available sessions and determine the type of meetings that are generally of interest.
http://infocampseattle2008.pbwiki.com/Daily+Sessions+Schedule+
May want to add progressive enhancement session.
2. Outcomes
3. Artifacts
The following should be used for the tagging in flickr:
infocamp infocampseattle infocampseattle2008 upcoming:event=454157
http://www.flickr.com/photos/18305513@N00/tags/infocampseattle2008/
5. TODO Development Tools for Faster Development presentation
Auto-complete and other systems have been used to simplify construction of new systems. When looking at some of the new IDEs it might be helpful to have that functionality dropped into Emacs.
6. TODO Progressive Enhancements for the Web presentation
6.1. Communication
How is the
6.2. Technologies
Consider the use of jQuery as the core technology.
6.3. Work-flow
What are the tasks for the engineer for the full product life-cycle.
6.3.1. Marketing and Strategy
What are the goals for the organization. Is there a feature that is fully conceived before hand-off or is hand-off a misleading principle?
6.3.2. Product Modeling and Design
Determine the core objectives and strategy. UI Engineers should be involved to simplify the costs of the development in particular to determine what will need to be included in the technical design documents.
6.3.3. Visual Design
Is the world pixel perfect across browsers? There should be some notion of priority of the elements that are included on the page.
6.3.4. Technical Design
What are the core elements that need to be included in the technical design for a product:
- URLs and parameters
- Mapping of old URLs and rewrite rules
- Model information
6.3.5. Prototyping Visual Interactions
If a base set of interaction or UI renderings are known then new UI or dynamic functionality can be prototyped and scheduled outside.
6.3.6. Ajax: When to GET or POST
Include as part of site-map. Ensure that data access is considered for URLs. Consider REST.
6.3.7. Ajax: Progressive Enhancement
The initial view should just be basic semantic markup.
For polling of data there should be a base rendering, add a status item if the data or UI for the data isn't immediately available.