Your SlideShare is downloading. ×
Kickstarting SItes With a Custom Package
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Kickstarting SItes With a Custom Package

1,342
views

Published on

Published in: Technology

0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,342
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
22
Comments
0
Likes
2
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide


  • 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.
  • 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


  • Transcript

    • 1. KICKSTARTING SITES PROJECT WITH A CUSTOM PACKAGE DATE CLIENT 04.17.2009 T3CON09-DALLAS
    • 2. Ron Hall Busy Noggin Jeff Segars Web-Empowered Church
    • 3. Why kickstart? Launch quicker and cheaper. Maintain less code.
    • 4. KICKSTARTER 1.0 (WHAT YOU’RE ALREADY DOING)
    • 5. ⌘+C KICKSTARTER 1.0 (WHAT YOU’RE ALREADY DOING)
    • 6. ⌘+C ⌘+V KICKSTARTER 1.0 (WHAT YOU’RE ALREADY DOING)
    • 7. KICKSTARTER 2.0 (WHAT YOU NEED TO BE DOING)
    • 8. ⌘+C KICKSTARTER 2.0 (WHAT YOU NEED TO BE DOING)
    • 9. ⌘+C ⌘+V KICKSTARTER 2.0 (WHAT YOU NEED TO BE DOING)
    • 10. ⌘+C ⌘+V ⌘+S KICKSTARTER 2.0 (WHAT YOU NEED TO BE DOING)
    • 11. ADAPT BEST PRACTICES FROM THE SITES YOU BUILD NOT A ONE SIZE FITS ALL SOLUTION!
    • 12. Templates CSS Frameworks, inheritance & FCEs.
    • 13. Modular Typoscript Menus, constants, and external files.
    • 14. CSS Zen Garden Menus mainMenu = HMENU mainMenu { entryLevel = 0 1 = TMENU 1{ wrap = <ul>|</ul> NO { allWrap = <li> | </li> } ACT < .NO ACT = 1 ACT { allWrap = <li class=quot;altquot;> | </li> } } }
    • 15. Shared configuration with custom constants # Define the date and time formats constants.wec.dateFormat = %m/%d/%y constants.wec.timeFormat = %I:%M %p # Convert the date format of news to WEC constant defined value plugin.tt_news { displaySingle.date_stdWrap.strftime = {$constants.wec.dateFormat} displayLatest.date_stdWrap.strftime = {$constants.wec.dateFormat} displayList.date_stdWrap.strftime = {$constants.wec.dateFormat} displaySingle.time_stdWrap.strftime = {$constants.wec.timeFormat} displayLatest.time_stdWrap.strftime = {$constants.wec.timeFormat} displayList.time_stdWrap.strftime = {$constants.wec.timeFormat} } # Convert the date format of blog comments to WEC Constant defined value. plugin.tx_veguestbook_pi1 { datetime_stdWrap.strftime= {$constants.wec.dateTimeFormat} date_stdWrap.strftime= {$constants.wec.dateFormat} time_stdWrap.strftime= {$constants.wec.timeFormat} } example: wec_constants
    • 16. External Typoscript via TS Setup <INCLUDE TYPOSCRIPT src=”fileadmin/resources/ts/menu.ts” /> External Typoscript via Extensions <?php t3lib_extMgm::addStaticFile($_EXTKEY,'static/ts/','My Menu'); ?> example: wec_constants
    • 17. Simplified Backends Groups, permissions & TSConfig
    • 18. Groups and Permissions • Keep configuration in groups not users • Baseline group for common settings • Task or section based groups applied to pagetree example: WEC Starter Package
    • 19. TSConfig & TCA // Allow additional fields to be excluded in user and group records. $TCA['tt_content']['columns']['header_position']['exclude'] = 1; $TCA['tt_content']['columns']['header_link']['exclude'] = 1; // Force new content elements to be allowed before they appear. $TCA['tt_content']['columns']['list_type']['config']['authMode'] = 'explicitAllow'; // If be_acl is loaded, hide its records from list view. if (t3lib_extMgm::isLoaded('be_acl')) { t3lib_extMgm::addPageTSConfig(' mod.web_list.hideTables := addToList(tx_beacl_acl) '); } example: wec_config
    • 20. Maintenance Version control and a common platform.
    • 21. Build up or tear down? Broad client base vs. niche markets
    • 22. What goes into your package? Extensions, Typoscript Libraries, etc.
    • 23. The Busy Noggin Quicksite http://templavoila.busynoggin.com WEC Starter Package http://www.webempoweredchurch.com
    • 24. Credits • Kickstarter Photo http://www.flickr.com/photos/adifferentryan/133065997/ • One Size Fits All Photo http://www.flickr.com/photos/angusf/2270317189/