| 8:15am |
Registration open
|
|
Matt Weinberg
Topic yet to be announced
|
|
Erik Reagan
Environments & Version Control: The Why and How
There seems to have been a good bit of discussion about environments and version control lately. To those who haven’t entered this world it is a huge cloud of confusion. “Why spend the extra time with environments and database problems?” For those just diving in it sounds more like, “Why did I even make this decision? Can I have my life and sanity back?” Then you have the multi-environment veterans saying, “Why the heck aren’t you doing this?”
In this talk we will look at the pros and cons to having your EE sites in multiple environments and under version control. Going one step further, we will talk about setting up your site in version control with the multiple environment aspect in mind. By the end of the presentation, participants will be equipped with knowledge on how to move forward and what to expect. This presentation is geared towards experienced EE developers but the principles can apply to anyone working in web development.
|
|
Jacob Russell
EE, Faster
One of the less focused on but important parts of building an EE site is understanding how to optimize what you're building so it runs quickly. EE is great for allowing you to build a site however you want, which can, and often does, lead to slow sites. Usually this can be traced back to too many embeds, high numbers of queries, and an over-taxing of the template engine.
My talk would be an overview of where these dangers arise for the practical, front-end-focused EE user. I would go over what the causes of these problems are, how to identify them by looking at the queries and template debugging output on the site, and how to resolve them using good coding and readily available tools and add-ons. Specifically i would go over tools like template caching, template morsels, fresh variables, and low variables to
show where they shine, where they are weak, and when you should use each to improve the speed of your site.
I believe approaching this topic from the front end, rather then from a programmers deep-level perspective, would provide a lot of value to the designers and front end developers that make up the bulk of EE users. Web developers with extensive experience already might not find as much value in it, but my experience with the community has given me the impression that this is not the majority of people.
|
|
Coffee Break
|
|
Brian Warren
Making Client-Friendly Experiences with EE
|
|
Fred Boyle
Topic yet to be announced
|
|
Lunch (not provided)
|
|
Mark Huot
Developing in EE2, or How to Use CodeIgniter
We’ll cover the basics of creating an accessory, a module and an extension in EE2. Delving into the specifics of getting started, what’s required and some best practices. I’ll walk attendees through common mistakes and some things I’ve learned along the way. All the while I’ll be integrating some CI fundamentals into our add-ons. I’ll cover the Routing class, the Input and Uri classes as well as the newly awesome Template class.
|
|
Rob Sanchez
The Beast Within
The greatest learning resource for ExpressionEngine is the source code. By becoming familiar with what’s under the hood you can learn how to tune your site architecture for maximum performance, debug problems more quickly, and write better custom addons.
We’ll begin by tracing the path from HTTP request to response, from the CodeIgniter core all the way to the final output of the template engine and/or the control panel. Within this context, we’ll examine the database structure, how and when addons are invoked and how to truly interpret error messages by following the source code.
This is a “teach a man to fish” kind of talk. By the end of the presentation, I hope that the audience is better equipped to spend less time seeking answers in the forum, and more time pro-actively answering their own questions.
|
|
Coffee Break
|
|
Ruthie BenDor
No Guessing: Prototyping Interaction For EE
From Twitter: “3 static templates cannot adequately describe a CMS-driven site. Guessing developer = unhappy client. Designers: Prototype interaction.”
I work with a lot of designers that are used to thinking about static websites. So they’ll hand me a couple of static templates. Invariably, when I go to code the site, I find black holes — places that these static templates don’t cover, which means the designer didn’t consider them, which means the client didn’t consider them. So I’m left to hack something together based on my best guess of the client’s intention. This results in confusion, unmet expectations, and disappointment all around. We can do better.
I want to give a talk for designers and designer/developers about prototyping interaction. I’ll briefly talk about prototyping tools (paper, Balsamiq, etc.), but mostly focus on how to use prototyping to ask the right questions when building an EE site.
|
|
Greg Aker
Topic yet to be announced
|
