.. You may want to use the usual include line. Uncomment and adjust the path. .. include:: ../Includes.txt ================ EXT: Page Teaser ================ :Created: 2010-02-18T17:33:18 :Changed by: Henjo Hoeksma :Changed: 2010-03-28T15:46:55 :Classification: pageteaser :Description: The keywords help with categorizing and tagging of the manuals. You can combine two or more keywords and add additional keywords yourself. Please use at least one keyword from both lists. If your manual is NOT in english, see next tab "language" ---- forEditors (use this for editors / german "Redakteure") forAdmins (use this for Administrators) forDevelopers (use this for Developers) forBeginners (manuals covering TYPO3 basics) forIntermediates (manuals going into more depth) forAdvanced (covering the most advanced TYPO3 topics) see more: http://wiki.typo3.org/doc_template#tags ---- :Keywords: forDevelopers, forBeginners, page, teaser, description, additional :Author: Henjo Hoeksma :Email: me@henjohoeksma.nl :Info 4: :Language: en |img-1| |img-2| EXT: Page Teaser - pageteaser .. _EXT-Page-Teaser: EXT: Page Teaser ================ Extension Key: pageteaser Language: en Keywords: forDevelopers, forBeginners, page, teaser, description, additional Copyright 2000-2010, Henjo Hoeksma, This document is published under the Open Content License available from http://www.opencontent.org/opl.shtml The content of this document is related to TYPO3 \- a GNU/GPL CMS/Framework available from www.typo3.org .. _Table-of-Contents: Table of Contents ----------------- `EXT: Page Teaser 1 <#1.EXT:%20Page%20Teaser|outline>`_ **`Introduction 3 <#1.1.Introduction|outline>`_** **`Users manual 4 <#1.2.Users%20manual|outline>`_** **`Administration 5 <#1.3.Administration|outline>`_** **`Configuration 6 <#1.4.Configuration|outline>`_** **`Tutorial 7 <#1.5.Tutorial|outline>`_** **`Known problems 8 <#1.6.Known%20problems|outline>`_** **`To-Do list 9 <#1.7.To-Do%20list|outline>`_** **`ChangeLog 10 <#1.8.ChangeLog|outline>`_** .. _Introduction: Introduction ------------ .. _What-does-it-do: What does it do? ^^^^^^^^^^^^^^^^ This extension provides a field 'Page Teaser' in the page. It will be listed under the tab meta and contains a RTE bodyfield. You can use it to add some sort of teaser to your page. For example see: http://henjohoeksma.nl (dutch) where it is used next to the logo. .. _Screenshots: Screenshots ^^^^^^^^^^^ Page properties, tab Meta: |img-3| At the bottom you'll find the Page Teaser field: |img-4| .. _Users-manual: Users manual ------------ .. _Installation: Installation ^^^^^^^^^^^^ Install the extension from TER, I figure you know how to do that ;-) After installing and updating the database with the new field, go to a page and edit it's properties to make sure you see the page teaser field. Next fill in something and save it to verify it is working. .. _Usage: Usage ^^^^^ Next use it so it is being displayed on your page, for example using code like this: :: ## Description [begin] lib.description = TEXT lib.description.data = page:tx_pageteaser_teaser ## Description [end] Of course you can extend the TypoScript to whatever you like and be fancy with it building lists of pages and their teaser. For that you could also use the jp\_pageteaser extension though. .. _FAQ: FAQ """ - Why this extension? - I wanted to use a description on my blog ( `http://henjohoeksma.nl `_ ) with the possibility to use Rich Text formatting. Next to that I didn't like using the meta description tag – since it serves originally a different purpose. - Extensions like this are easy to build using the ext\_kickstarter – so why not? And why not share it – maybe someone will be able to use it :-) - Why not use the abstract field or the description field of the meta tags? As I said: those fields are officially used for different purposes. The purpose of this field is more content related than it is a meta tag. - Why did you put it under the tab Meta? It doesn't really belong there... That would be a valid question. Basically because I am used to filling in descriptions of a page in that area so it feels logical. It also isn't logical on the other hand, since it clearly isn't a meta tag... Feel free to discuss this at my blog ;-) .. _Administration: Administration -------------- None. .. _Configuration: Configuration ------------- None. .. _Tutorial: Tutorial -------- See the section 'Users manual'. There's really not more to it. .. _Known-problems: Known problems -------------- None. .. _To-Do-list: To-Do list ---------- None so far. .. _ChangeLog: ChangeLog --------- See changelog file. |img-2| 10 .. ######CUTTER_MARK_IMAGES###### .. |img-1| image:: img-1.png .. :align: left .. |img-2| image:: img-2.png .. :border: 0 .. :height: 21 .. :hspace: 9 .. :id: Grafik2 .. :name: Grafik2 .. :width: 87 .. |img-3| image:: img-3.png .. :align: left .. :border: 0 .. :height: 161 .. :id: graphics1 .. :name: graphics1 .. :width: 469 .. |img-4| image:: img-4.png .. :align: left .. :border: 0 .. :height: 204 .. :id: graphics4 .. :name: graphics4 .. :width: 470