Kickstarting SItes With a Custom Package

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

more share options
Embed For WordPress.com

Without related presentations

Notes on slide 1

Compare to developing TYPO3 from scratch. You wouldn’t do that, so why rebuild the same sites over and over again.
Long term maintenance costs decrease when a bugfix on one site works on many sites.

Copying and pasting code from existing sites serves as an informal reference library.

Not a one size fits all solution
Identify what YOU already when building sites and extract it into a formalized solution
For the WEC Starter Package, this means identifying a pagetree and extensions that fits the needs of most churches and gives them a point to start learning TYPO3.

Hope you attended Ron’s template talk yesterdayCSS FrameworksCommon FCEs that complement your CSS frameworkDefine a consistent base and customize on top of it
No need to worry about templates as extensions, just rely on version control

GMENU still useful in certain situations but simple markup + CSS takes care of most needs.
CSS Zen Garden

WEC Constants

Task-based groups
Keep groups as lean as possible

Not automated!

WEC Constants

Version control + extensions = quick and easy upgrades and rollbacks
Common platform means less worry when upgrading TYPO3

WEC targets churches and wants them to learn TYPO3 and be self sufficient. Thus, a comprehensive package where features will be disabled fits. Busy Noggin works with a diverse client base so a simple config where pieces are added fits better.

Open discussion about best practices and extensions

2 Favorites & 1 Event

PeaceSfiSh favorited this 6 months ago
Tags typo3
asakurayoh favorited this 6 months ago
Jeff Segars, Developer at Web-Empowered Church, added this to the event T3CON09 Dallas