Typo3

TYPO3 CMS Certified Editor (TCCE)

The “TYPO3 CMS Certified Editor” manages pages and content with various page and content element types provided by integrators. The “TYPO3 CMS Certified Editor” creates new pages, restructures the page tree and manages languages available in the setup.

Validity of the TYPO3 CMS Certified Editor

The TYPO3 certificate for the “TYPO3 CMS Certified Editor” expires 36 months after the issue date. The 36-month period ensures adequate security of investment for the Editor and at the same time provides security for everyone who relies on the up-to-date nature of the certificate. With a time limit of three years the version restriction no longer applies, thus the certification does not have to be dependent upon version numbers. 

TYPO3 CMS Certified Integrator (TCCI) 

The Certification Team defines the “TYPO3 CMS Certified Integrator” as follows:

The “TYPO3 CMS Certified Integrator” develops the template for a website, configures all the necessary extensions and creates the access rights for backend users. The “TYPO3 CMS Certified Integrator” does not install TYPO3 on the webserver and does not program extensions. The “TYPO3 CMS Certified Integrator” knows how to configure the pre-installed TYPO3 using the installer. 

TypoScript is by far the biggest part of the exam. As a Certified Integrator, you have established knowledge in

  • TypoScript syntax
  • Data types
  • Operands
  • Conditions, including comparison with TSFE, records (e.g: backend_layouts) or global variables (e.g: hostname) 
  • Constants
  • Functions, objects, and properties, with detailed knowledge in
    • OptionSplit, including all four rules
    • stdWrap
    • accessing data from various sources, like TSFE or page
    • knowing different wraps and their precedence’s in terms of execution / working order
  • Top-level objects and reserved names
  • Special Top-level objects (such as “temp”)
  • Hierarchical menus and menu item states (like CUR, SPC, etc)
  • Commonly used configuration directives form the “config” TLO

You are able to

  • put / split TypoScript values onto multiple lines
  • interchange doctypes and xmlprologues through TypoScript
  • render and configure a variety of navigation menus
  • write as few TypoScript as possible to not get an error in the frontend when visiting the page
  • optimize assets (like JavaScript or stylesheets) for page speed
  • debug TypoScript with debug functions provided from the core
  • can modify all possible parts of the generated html output through TypoScript (e.g: replacing head- and body-tags or putting own meta tags in proper positions)
  • outsource TypoScript into files and reference these files in the TypoScript template records
  • use the TypoScript Object Browser (TSOB) and can inspect and manipulate values through it

Also, you can differentiate various locations where TypoScript is used for configuration purposes, like

  • Users and groups (UserTS)
  • Pages (PageTS)

 TYPO3 CMS Certified Developer

The Certification Team defines the “TYPO3 CMS Certified Developer” as follows:

A “TYPO3 CMS Certified Developer” has to have experience collected through projects, should know the architecture, design patterns, best practices, and a fair share of internals both TYPO3 CMS and the extension framework relies on. A “TYPO3 CMS Certified Developer “is able to implement an extension completely in a state-of-the-art way and writes clean code by following the TYPO3 Coding Guidelines (CGL), and is well versed in a wide range of topics, from the initial setup of an extension up to the point of publishing it in the TYPO3 Extension Repository (TER).

As a Certified Developer, you have established knowledge in the architecture, knowing

  • what plugins are and how they are registered and configured
  • what modules are and how they are registered and configured
  • the MVC architecture and its parts
  • how to implement models, views, controllers, and repositories, according to the MVC design pattern
  • what view helpers are and how to implement these
  • the term “aggregate root” and can explain it
  • the intended purposes of files in your extension’s root folders (like ext_emconf.php, or ext_tables.php)
  • directory structure of an extension
  • general knowledge about database relations

CONTACT US

We're not around right now. But you can send us an email and we'll get back to you, asap.

Sending

©2017 Powered by Networx Security e.V.

Log in with your credentials

Forgot your details?