Users

Frontend and Backend

Editing

List Module

Versioning

RealURL

Localization

Templating

• HTML
  

  Start by making a web page as normal.

  Marks look like this, they have no spaces, and shouldn't go inside comments:

  ###TITLE###

  Things get substituted into them.

  Subparts are things inside a pair of marks. In this case, the marks can be inside comments.

• Using it
  

  We create a template, and set it on our root page. It is then inherited.

  Then we write some TypoScript to use it:

  page = PAGE { // Create page object
      includeCSS.base = fileadmin/my_template/style.css
  
      10 = TEMPLATE { // Set first content object as template
          workOnSubpart = DOCUMENT // What our content is templating over
          template = FILE { // Set template object's template to a file
              file = fileadmin/my_template/index.html // Set file object's file to a filename
          }
  
          subparts {
              SUBPART_NAME = thing
          }
  
          marks {
              MARK_NAME = TEXT {
                  value = my text
              }
          }
      }
  }
  

• Menus
  

  We need a HMENU object

  nav = HMENU {
      wrap = <ul>|</ul> // Tell our menu what its outer object is
      special = list { // We'll provide a list of pages
          value = 2, 3 // List of pages by id
      }
      entryLevel = 0 // Start from the top
  
      // Inside our HMENU, we need some items like TMENU and GMENU
      // Nav depth 1: text menu
      1 = TMENU {
          NO = 1 # Activate normal link styles
          NO {
              // If we had multiple levels, we'd need wrapItemAndSub instead
              allWrap = <li>|</li>
          }
          ACT = 1 # Activate active link styles
          ACT {
              allWrap = <li class="current">|</li>
          }
      }
  }
  

• Content
  

  CONTENTRIGHT = CONTENT
  CONTENTRIGHT < styles.content.getRight
  
  

Backup

Folders

• fileadmin
  

  Files uploaded by the content authors. Can be accessed using the File Module.

• typo3
  

  This is a symlink to the actual typo3 PHP code.

  The .tar.gz package you download has all the composer stuff (which fetches libraries) already done.

  • typo3/sysext
    

    System extensions.

    Each extension folder can contain:

    • ext_emconf.php describes the extension programatically
    • ext_{localconf.php} sets up hooks and configuration
    • ext_tables.sql create table statements which should look like MySQL dump outputs
    • ext_tables.php sets up backend display of database tables
    • Classes
    • Configuration
    • Documentation (in restructured text format)
    • Resources
    • Tests
    • hooks
    • composer.json
    • ext_icon.svg
• typo3conf
  

  Configuration. All configuration in typo3 is state: it's done after installation.

  • typo3conf/ext
    

    Downloaded extensions live here.

• typo3temp
  

  Cache. You can delete this at any point and TYPO3 will make it again.

• uploads
  

  Uploads directory. Not sure how this differs from fileadmin?

Architecture

Command Controller

File Abstraction

Database

• Schema
  

  In $GLOBALS['TCA'] there is a database table description.

  See TCA Reference.

  Contains:

  • validation
  • join fields
  • backend vs layout (hmm?)

  An extension controls this using a file <ext_name>/Configuration/TCA/<database-table-name>.php. This file is automatically found, and its result cached.

  Each element of $GLOBALS['TCA'] is a table name => associative array mapping.

  Each table has the following:

  • ctrl (mandatory) is general stuff about the table
  • interface backend display properties
  • columns
  • types maps columns to an editing form
  • palettes a list of special fields which don't get in the main editing form.
• Schema Upgrades
  

  There are tools in the backend for checking that the schema is up to date, and migrating it if not.

Fluid Templates

• Content templates
  

  You need to create a backend layout which goes with your content template.

  Then you write a typoscript template for your root page.

  Then you assign that backend layout to your pages.

• Layout
  

  This is the part you share between all your pages.

  fileadmin/templates/layouts/main_layout.html

  You can reference a layout from within your content template.

• Partials
  

  These are small pieces like headers.

  I could just include them in my layout instead.

Operators

Conditions

Includes

Comments

Page TypoScript

User TypoScript