May 5th 2017 naw.info FLOW3 Blog

Nützliche Helferlein für jeden TYPO3-Anwender

In diesem Monat wird es mal ganz kurz & praktisch: Ich habe unser „Bitmotion Team Content“ gebeten, mir die solche TYPO3-Kniffe zu nennen, die sehr hilfreich, aber kaum bekannt sind.

Hier kommen nun drei solche nützlichen Helferlein.

Alle diese Werkzeuge gibt es in TYPO3 schon sehr lange; die Abbildungen beziehen sich jeweils auf die aktuelle Version TYPO3 Version 8 LTS.


1. Effiziente Massenarbeit durch Assistenten

Als erstes wollen wir uns einmal das Modul mit dem unscheinbaren Namen „Funktionen“ anschauen. In diesem versteckt sich eine Sammlung von Assistenten („Wizards“), die je nach Aufgabenstellung enorm viele Klicks sparen können.

Für das Funktionen-Modul ist immer zunächst die gewünschte Seite auszuwählen, auf der der Assistent aktiv werden soll. Der klassische Anwendungsfall ist das Anlegen vieler neuer Seiten (siehe Screenshot), aber je nach installierten Erweiterungen kann es hier verschiedenste weitere Möglichkeiten geben.

Jeder Assistent kann auch Optionen mitbringen, hier etwa finden sich

  • Neue Seiten nach existierenden Unterseiten anlegen
  • Neue Seiten verbergen
  • Neue Seiten in Menüs verbergen

Pro-Tipp: Bei der Planung eines eigenen Erweiterungsmoduls sollte immer auch überdacht werden, ob „Massenaufgaben“ anfallen und auf welche Weise diese unterstützt werden können. Vielleicht ist ja ein eigener Assistent der Königsweg!


2. Suchen und Finden als Redakteur

Noch viel mehr unterschätzt ist die Volltextsuche im TYPO3-Backend – wer diese nicht nutzt, ist selbst Schuld!

Der einfachste Einstieg ist rechts oben über das Suchfeld mit Lupensymbol. Die Treffer werden „live“ eingeblendet. Aufgepasst – hier gibt es nun zwei Möglichkeiten:
A) Direkt auf den Treffer klicken = diesen öffnen,
B) Auf „Alle anzeigen“ klicken = Trefferliste öffnen.

Die Trefferliste (B) kann übrigens mehr Treffer enthalten als die Live-Vorschau (A).

Oberhalb der Trefferliste (B) hat man übrigens eine etwas erweiterte Sucheingabe. Diese kann man auch jederzeit direkt öffnen, indem man eine Seite auswählt und im Bearbeitungsfenster auf das Lupensymbol klickt:

Neben der Volltextsuche gibt es übrigens noch eine weitere – nämlich die „Filter“-Funktion über Seiten: Klickt man auf das Filter-Symbol, so kann man anfangen, den gesuchten Seitentitel einzugeben, und der Seitenbaum reduziert sich auf die passenden Treffer.

Pro-Tipp: Diese Suche funktioniert auch mit Eingabe der Seiten-ID!


3. Bookmarks machen das Leben leichter

Für alle, die einen verzweigten Seitenbaum zu verwalten haben, dabei aber häufig an dieselben Stellen navigieren müssen, hält TYPO3 Lesezeichen („Bookmarks“) bereit.

Dies ist nicht zu verwechseln mit den üblichen Browser-Bookmarks – denn hier haben Sie die Möglichkeit, gezielt einzelnen Dinge im Backend zu markieren, neben Seiten z.B. auch Systemordner (etwa für News-Artikel) und sogar einzelne Inhaltselemente.

Per Stern-Symbol lässt sich jedes Element zur Lesezeichenliste hinzufügen:

…und abrufen lässt sich die ganze Liste ebenfalls durch das Sternsymbol, diesmal das am oberen Rand des TYPO3-Backends:

Wie unschwer zu erkennen, erfolgt hier auch die Lesezeichen-Verwaltung – Bookmarks können nicht nur gelöscht, sondern auch umbenannt werden. In der Praxis ist dies vor allem bei Lesezeichen einzelner Inhaltselemente sinnvoll – was aber per se der seltenere Anwendungsfall ist.


Fazit

Allen drei beschriebenen Tipps ist gemeinsam: Es geht hier nicht um spektakuläre Killer-Features, sondern um nützliche, aber wenig bekannte Hilfen für das echte Leben. Ich persönlich würde in der täglichen Arbeit auf nichts davon verzichten wollen!

Read full article

Feb 15th 2017 news.typo3.org: FLOW3

punkt.de is TYPO3 Platinum Member

Involved from the start

"After years of cooperation as a TYPO3 Gold Member, we have now decided to become a Platinum Partner, in order to give back even more to TYPO3. We owe our growth to TYPO3 and would now like to contribute to making the system even better and to further strengthen the successful development of the past two years," says Jürgen Egeling, CEO of punkt.de. "TYPO3 has been providing us with the opportunity to grow with our customers since 2003. We began our work as a web and hosting agency with small websites like fertiggaragen.de. Now, we are running diverse TYPO3 solutions from corporate websites like leaseplan.de and intranet portals like rehaVital to very complex solutions like the partner portal of the Deutsche Post. For us as a service provider, a deciding factor was always the reliability and the updatability of the system. This is why we would like to contribute to the development of TYPO3, in order to further establish it within the market in the long term. 

Expertise: from website to individual applications

punkt.de has 20 years of experience in the market and knows the customers' requirements. The teams develop various solutions for their customers with a passion for all things digital, technical know-how and a very transparent mode of operation – whether it be a corporate website, web portal, shop, intranet or an entirely individual application. 
In order to carry out innovative projects in an agile manner, the agency has been counting on open source software and agile software development for many years. A close and fair cooperation with the customers and the development of sustainable, long-lasting projects are key features for punkt.de. This pays off: About 70 percent of the customers have been placing their trust in punkt.de for over four years; among them the Deutsche Post and the listed analysis specialist Bruker. 

A loyal partner of the community

The agency punkt.de is well-known within the TYPO3 community. punkt.de is present at events, takes part in code sprints and is involved in the TYPO3 marketing team. Additionally, the CEO Jürgen Egeling was chairman of the TYPO3 Association for three years. Back then, Kasper Skårhøj, founder of TYPO3, still conducted the introduction to TYPO3 himself. Ever since, the team has been very involved in the community and, among other things, organized the very first TYPO3 conference in Karlsruhe in 2005, then called the TYCON3. Last but not least, the countless other events that punkt.de sponsored over the years. 

About punkt.de

With more than 30 employees punkt.de is creating a large range of digital solutions and is providing integrated support that spans from requirements analysis, to development and up to consulting: no matter if it concerns features, technologies, technical SEO questions or hosting. punkt.de's solutions are based on TYPO3, Neos and other modern frameworks and programming languages. Among these, punkt.de specializes in optimizing business workflows, modeling business processes and implementing complex user rights restrictions. The latest success is the honor of receiving the TYPO3 Award 2016 for the best "Small Website" project with the donation web shop of nph deutschland e.V. (https://www.hilfefuerwaisenkinder.de/shop/).  
Contact Fabian Stein
punkt.de GmbH
info@punkt.de
0049 721 91090

Read full article

Feb 14th 2017 news.typo3.org: FLOW3

TYPO3 v8.6 released

What's new?

New image manipulation wizard

Image handling has been a strength of TYPO3 ever since. Next to integrator related features, version 7 brought a basic image manipulation wizard to the backend, allowing editors to crop images per usage.

This feature has been heavily extended in v8.6: Most importantly, the image manipulation wizard now allows multiple crop variants for a single image. This allows editors to show different image areas according to the display size in the frontend.

Editors can also select a focus area to provide a hint which area in the image is the most important and should always be visible.

Last but not least integrators can mark cover-areas which give editors a visual indication which areas of the images might be covered by other elements of the website.

This feature was sponsored by SYZYGY Deutschland GmbH.

Flexible Menu-based content elements

A lot of work has been put into “fluid_styled_content” and “css_styled_content”, the basis for rendering content of a web page. As a main goal, the two extensions are now much better aligned and reduce headaches for integrators if dealing with the two.

As a nice side effect, this revamp comes with a couple of visible UX improvements for editors when dealing with content elements: The “menu” elements like “List of pages” and “List of sections” are now true content elements and can be selected in the new element wizard directly without another step in between.

Improved link element and validation

To further improve the editing experience of forms in the backend a couple of great usability improvements were integrated: Link handling got a better preview that includes improvements like showing the page path instead of a cryptic internal link. Additionally, form validation errors are now displayed in the top right corner of the backend, allowing editors to directly jump to invalid fields.

The link dialog gained features to make it extensible, providing the ability to create links to all kinds of records. This functionality has previously been provided by the extension “linkhandler”. 

Language synchronization feature

The steady refactoring of crucial parts of the code base like the data, form and language handling allows to add new custom features easily on top of TYPO3. A new wizard has been implemented allowing translators to select if a single field of a localized record has a dedicated value or if it should inherit the value of its language parent. The data handling within the core ensures the field content is copied to the translated record in case of changes to the parent record.

Improved scheduler module

Multiple features were added to the scheduler, the task runner of TYPO3. It’s now possible to have fine grained control of tasks and task groups. Single and multiple tasks can now be scheduled to be executed on next cron run and the user interface for handling long lists of tasks has been improved.

Fluid Styled Content & CSS Styled Content refactoring

Innovation is as important to us as to protect your investment. With TYPO3 Fluid we introduced a new template language a couple of years for a simple reason: To reduce the cost of creating websites for Frontend developers. More intuitive and easy to maintain predefined templates enable developers to speed up integrations, that are more reliable and flexible than ever before.

CSS Styled Content (CSC) has been the preferred template rendering engine for TYPO3 for a long time, and is part of TYPO3 since version 4.0, dating back to 2006. CSC is extremely flexible but also hard to learn and understand even for highly trained TYPO3 integrators. With the release of TYPO3 CMS 7.6 we fully embraced TYPO3 Fluid also for the rendering of content elements.

Fluid Styled Content (FSC) was introduced as successor of CSC but the feature set diverged from the beginning. The lack of flexibility and incomplete feature set in comparison to CSC made it hard to migrate existing instances that have embraced all features and the enormous flexibility before.

With the release of TYPO3 8.6 we are now making migrations even easier and provide new possibilities for more cost-efficient integrations. CSC is now fully compatible with FSC and shares the same capabilities to make a transition as easy as possible. To focus even more on the development of FSC in the next major version of TYPO3, CSC is now deprecated and in maintenance mode.

For compatibility, CSC is now supporting “Text and Media” that was previously exclusive to FSC. On top of that, FSC has learned some tricks from CSC. Now Fluid Styled Content has support for all content elements prior existing only in CSC, this includes "Text", "Text and Images" and "Images". Also for example „Frames", "Space before" and "Space after" have been integrated and fine tuned for better maintainability and understandability for Editors and Integrators. We cannot wait to see what you are creating with these new options.

Further changes

As usual, we have a lot of small but nice changes in TYPO3:

The previously introduced Form Framework in 8.5, originally derived from the Flow Framework of Sebastian Kurfürst of the Neos project, has some better integrations for “Finishers” and optimized templates to be used out-of-the-box.

The command-line handling of the TYPO3 Core has been optimized, making it easier for TYPO3 to run without creating a Backend user before.

The newly introduced CKEditor Rich Text Editor is now configurable through Yaml-based configuration presets, allowing to re-use configurations in multiple installations.

For a full list of changes, see our documentation for more information: https://docs.typo3.org/typo3cms/extensions/core/8-dev/Changelog/8.6/Index.html 

Download TYPO3 now

TYPO3 v8.6 is available on our download page or via composer (see composer.typo3.org). The minimum PHP version required to run TYPO3 v8 is PHP 7.0, so make sure your system is equipped with the proper PHP version.

What's next?

The final v8 release, which will be labelled as TYPO3 v8 LTS will be released on April 4th, 2017.

From now on, the team will concentrate on bug fixing, documentation and finishing a couple of loose ends. The goal is to release a first TYPO3 v8 LTS version as stable as possible, so administrators, integrators, developers and editors can rely on it as a stable product right from the beginning.

To achieve that, we need as much testing and feedback as possible of v8.6 now. Please participate in this process, upgrade your instances to v8.6 and help find and fix issues not tackled yet. Helping now will directly safe time and money when it comes to the roll out of TYPO3 v8 LTS to the huge user base.

Read full article

Dec 20th 2016 news.typo3.org: FLOW3

This Week in TYPO3 (2016, Week 49)

Past, present and future of tt_address development

Kasper Skårhøj started development of TYPO3 almost 20 years ago. He also introduced  ‘plugins’ like tt_address, tt_products, tt_news, tt_content, tt_poll, tt_board, tt_calender, tt_guest to TYPO3 version 3.3.0, where ‘tt_’ stands for typotable. Each having a number assigned to them. For instance tt_news had the number ‘9’. These numbers were the predefined CTypes for those content elements. Some of them you might recognise as extensions you might still use, even though at that time these were not really plugins. They were just there, no way to turn them off. These "extensions" were part of the core, but later extracted into extensions.

Introduction

tt_address might be one of those extensions you still use. It's a good and flexible base to manage records for any kind of contact, location, office etc to be used with a lot of extensions or to display that on websites. Kasper transferred it to Ingo Renner who managed it for several years. Last year Benni took over the further development and improvements. After some talks between Benni and Clemens Riccabona on TYPO3 conferences and the TYPO3 Slack channel, they concluded that tt_address should be a solid and stable one-stop-base for address-record storage and visualization. This means that some features might not come to tt_address, as they might be out of scope, like nesting address-records. These features could be part of another extension, e.g. by connecting fe_users and tt_address with a relation. Most of the changes which need to be applied should be non-breaking, as not to annoy users of tt_address. However, some changes are breaking, and they must be applied to be future-proof. Clemens tells us more:

tt_address version 3.2.1

The current version of tt_adress is 3.2.1. How did we get there? It took quite some work to modernize the tt_address codebase and extension structure to get where we are. There is still more effort needed to bring tt_address to the conventions which have been introduced with extbase and autoloaders. Moving to the native sys_categories in favour of the ancient custom category code was done by contributors of our community working on version 3.0. 
  • A domain was included for tt_address PSR-2 coding standards were applied composer.
  • json was added
  • CA was moved to the new 'Configuration/TCA/Overrides' and there were some more structure-based non-breaking changes.
  • The extension is compatible now with TYPO3 6.2.2 up to 8.4
  • With version 3.0, all the social-media fields were added, and we ironed out some backdraws recently, like making the fields bigger (all the social-media fields are now varchar (255))
  • A common desire was to add the field "crdate", like almost all content-tables in TYPO3 have it. This was integrated with version 3.2
  • With 3.0 there were also added longitude and latitude fields to tt_address, but they were missing in domain and in TCA. This has now been fixed, and we also changed the datatype to what is suggested commonly for geo-coordinates
  • In version 3.2 the basic template (which is by now marker/pibase based) got annotations according to schema.org suggestions.
  • There was a bunch of bugs ironed out, most of them recorded in forge.typo3.org
  • We moved the development over to github: https://github.com/FriendsOfTYPO3/tt_address. If you want to contribute, fork our project and submit your changes as pull-requests.
  • At the moment we are about to move the open tickets in forge to the new github repo. If you have issues, please use github for submission! It is our goal to make github our one-stop resource for tt_address

Next steps

  • In the next few versions (maybe 3.5) we want to add a wizard for selecting geo-coordinates through a map, based on OpenStreetMap.
  • A custom eval in TCA for the geo-coordinates as the native ones are not fitting our needs completely.
  • Geocoding 'onsave', as well as a scheduler-task for geocoding a selectable number of records at-once.

Planning the future

  • We want to include an extbase controller and a basic FLUID template, featuring a list-view with basic filtering by e.g. group, first-char of name a detail-view ** a map-view, optionally connectable with the listview
  • Translation of tt_address records. This is also a common desire, as far as we can see, and it should go along with moving from the old language-xml files to the new xliff format.
  • We will most likely deprecate the old pibase based class and templates at some point in future, as soon as extbase/fluid code is considered to be stable

Three Projects That Will Seriously Benefit You

Swedish TYPO3 company Pixelant is one of big TYPO3 companies in the Northern regions (Denmark, Sweden, Norway, Finland). I talked with CEO Robert Lindh over the past few months on several occasions and to lead developer Jozef Spisiak and Mattias Nilsson more specifically about three ongoing projects. Pixelant is working on front-end editing, a starter kit and a user oriented TYPO3 manual. Robert describes Pixelant mission as: “We believe that through the internet, the world is changing in an ever quicker pace and it's only by sharing we can keep up. Internet is for everyone and we believe that everyone should have equal ability and right to use the internet to communicate their ideas and thoughts.”

Frontend editing

As a matter of fact TYPO3 already had front end editing of sorts before any other CMS. We are talking the year 2000 here. TYPO3 featured backend forms in the frontend, a very rudimentary and not very user friendly way of editing in the website, pictured below, but editing in the front end nonetheless.   These days we have grown accustomed to a seamless editing experience like Medium for instance offers. The past years TYPO3 has been steadily developing towards a system that is user friendly for editors, while remaining a strong enterprise solution. One of TYPO3’s strengths is its granular access rights, which allows the full administrative backend to be scaled down to a more editor friendly environment. Despite that scalability the traditional backend can be pretty discouraging for those editors that simply want to add content accompanied by some pics.

Aloha

Efforts for adding true inline editing to TYPO3 already started years back with the integration of the Aloha editor. At that time the team working on Neos (at that time the supposed successor to TYPO3) already integrated the Aloha editor. Georg Ringer started this effort and was soon joined by Pixelant to develop the product further. Lead developer Jozef Spisiak lets us know that Aloha worked pretty good for TYPO3 CMS 4.5 and they had some success with TYPO3 CMS 6.2, even though a version for 6.2 was never released to the extension repository, due to bugs and missing documentation. The 6.2 version was also the last effort with Aloha, before CKEditor came into play. Jozef says: “The reason we switched from Aloha to CKEditor was twofold. First of all we were not really happy with progress and browser support of the new Aloha 2 editor. On top of that there were some issues with the licensing model, which was supposed to be changed later on. Seeing the Aloha 2 editor has been discontinued makes me feel it was a great decision.”

Crowdfunding Frontend Editing

Jozef introduced the idea, with some mockups and screenshots, at the User eXperience Week 2016, where he went with his colleague Phat Hoang. A crowdfunding campaign was introduced late May with the goal of getting 50.000 euro together. The campaign drew quite a lot of attention and managed to reach its goal in time with a total of 118 backers pledging well over the intended goal. It shows people’s confidence in the team behind the campaign and the need for frontend editing. The Pixelant team doing the work consists of Jozef, Mattias Nilsson and Dmytro Hrynevych. The team is working in very close cooperation with the TYPO3 core team. The team talks to core team leader Benni Mack on an almost weekly basis. CKEditor is not only the choice for frontend editing, but will also be the default backend editor for the next TYPO3 Long Term Support version 8LTS. Especially in this light it makes a lot of sense the teams are in close contact to avoid duplication also know as re-inventing the wheel.   The project consists of 9 phases of which phase 2 (Inline editable content elements) was reached on the 5th of December. The team confided in me saying they are on schedule, even a bit ahead. Until now the development of the frontend editing extension will be done in a separate extension until it's fully compatible with the TYPO3 Core for 8LTS (April 3, 2017). The fe-editing repository is public and hosted on github under Pixelant company github page: https://github.com/pixelant/pxa_feediting

T3KIT

We talked about re-inventing the wheel earlier and the same collaborative mechanisms mentioned also work for the T3KIT project, although not in the form of crowdfunding. T3KIT has been developed in house by Pixelant to kickstart their projects, but has gained quite some adoption over time. Well known TYPO3 companies like Web Essentials and dkd have jumped on the bandwagon. T3KIT is a package with which you can easily start a TYPO3 project AKA website. A lot has changed since the time where a TYPO3 installation left first time users bewildered with the for many all too familiar ‘Template not found’ message. Little did people know how to work with typoscript to create a template back then. The TYPO3 3.x series actually included a few very basic typoscript templates, like tmpl_green, first uploaded in 2003 to TER. The road to a proper starter kit was long and paved with many different experiments, usually dying down, because the project was only applicable to one specific project or the original authors did not provide access or encourage others to participate. All too often authors develop on their own and just do not have the time to join forces with others.    The T3KIT initiative seems to have found common ground among users and it gets even better. T3KIT uses the Themes extension that is in itself also a combined effort of two templating projects that joined forces years back at TYPO3camp Hamburg 2012. The TYPO3 Themes project is run by Joey Hasenau, Kay Strobach and Thomas Deuling. The guys have even written a book about ‘Themes’ which ... dkd CEO Olivier Dobberkau says: “We have joined the T3KIT project as we think it's necessary to create and maintain a community standard for TYPO3 CMS projects. T3KIT offers a wide range of ready to use presets that can be expanded and customized. At dkd we will maintain the search functions based on Solr. Additionally we will support the use of T3KIT in Clouds such as Platform.sh and Microsoft Azure.” he further adds “T3KIT enables us also to accelerate the way we can create a concept for costumers. A team of 4 colleagues are responsible for the close contact with the T3KIT technical community”. webessentials’s Dominik Stankowski explains why making their own starter kit failed: “At Web Essentials we fell into the same trap thinking that we also needed our very own starter kit for direct customers or for the few agencies which were lacking their own. And we quickly thought our own setup was the best of all (since we invested a lot of time and money into it – we felt it was worth something... you get the point).” The T3KIT repository is public and hosted on github: https://github.com/t3kit

TYPO3 manual

TYPO3manual.com is an online manual for editors working with TYPO3. It is not so much focused on technical aspects and rather user/client oriented. Pixelant originally started it for their clients and made it available for the public. Currently it has translations in German, Swedish, English and Dutch. A French version is in the works. The website also features few english and german tutorial video’s and will see more in the future. You can see these three projects are quite different by nature. One crowdfunding, one pure collaborative and a project that could perhaps be combined in the future with already existing documentation efforts.

This is ‘MEET TYPO3’

MEET TYPO3 is a new TYPO3 Business/User event series, very similar in focus to the very successful Meet Magento series.  MEET TYPO3 saw its first event in Hamburg on April 13, 2016. MEET TYPO3 is THE event for agencies + clients, first contacts, decision makers, marketeers and hard-core-developers. The event features a special designated area with top notch speakers from the TYPO3 community and features a number of booths with TYPO3 professionals that answer questions, show demos and give insight into live solutions and use cases. MEET TYPO3 is a portable format for a business event to be hosted in any city. The initiator sitegeist started off with a german version in Hamburg. MEET TYPO3’s main goal is to generate more publicity and business interest in TYPO3.

Why attend MEET TYPO3?

Interested agencies that already know TYPO3 meet there to learn more about the highlights of the latest LTS version and the future vision. It’s going to be just as exciting for clients, who think about using TYPO3 as a potential CMS or who already work with TYPO3 and would like to see interesting case-studies to see what else can be done with the newest version. Agency deciders have the chance to see where TYPO3 is superior to other CMS and benefit from the experiences of other agency managers. Online-marketing-agencies and also advertising agencies can try the usability, see online-marketing cases and examples for fast landing page-campaign-development. But also TYPO3-expert-agencies and high end developers will get their money’s worth having exchanges with other TYPO3 pros. In addition to the live-stage and TYPO3-expert-bases there will be an mini-expo-area where agencies or hosting-companies will be happy to answer any questions. If you want to organise a MEET TYPO3-Event in your city, please contact meettypo3@sitegeist.de for more details.

MEET TYPO3 NETHERLANDS

On April 20, 2017 Meet TYPO3 will be organised in Rotterdam, The Netherlands. The organisation already has an impressive line-up of speakers amongst which Mathias Schreiber, Olivier Dobberkau and Dutch speakers Ric van Westhreenen, Matthijs Goense, Hans Olthoff and Jos Kruis. The location for this event will be the Oceanium in Blijdorp Zoo. It is a country specific event so most talks will be done in Dutch.  

First TYPO3camps in Venlo, Netherlands and Vienna, Austria

A new year and a new series of TYPO3camp starting with early bird TYPO3camp Venlo. TYPO3camp Venlo will be held on Friday March 10 and Saturday March 11. It is noteworthy that this international TYPO3camp will be held for the fifth time already. The organisation also announces Domani as new and pretty awesome location smack in the middle of Venlo. Join this first TYPO3camp of the year conveniently situated near the German border! Get an impression of last year’s event by reading TYPO3Camp Venlo 2016 on typo3.org. Join TYPO3camp Vienna in the heart of Europe and have a great TYPO3 event. You'll get 2,5 days worth of networking, learning, socializing, and connecting. You could present yourself as a freelancer or company: Give a talk, organize a session!
  • 24 - 26th March, 2017
  • University of Vienna
  • Warm up party Friday, 7:00 pm
  • 130 participants from all over Europe
  • For all questions regarding sponsoring, please contact us on t3cvienna@gmail.com
Both TYPO3camp Venlo and TYPO3camp Vienna are international camps.

T3BOARD17 is coming to Tyrol!

One of the oldest and most traditional events in the TYPO3 universe is the TYPO3 Snowboard Tour. Last winter with the 15th anniversary of the event, it took place in two different locations. One location being Whistler, Canada and the traditional European one in Zillertal, Tyrol. Clemens Riccabona explains what the coming event will be about: For the coming year, 2017, we will converge everything into one single event again. T3BOARD17 will be held in Pitztal, Tyrol, from January 29 to February 5. The Pitztal and its illustrious skiing region, Pitztaler Gletscher (Glacier of Pitztal), perfectly fits our needs and we could guarantee for snow! Through the years T3BOARD has been one of the official TYPO3 events alongside the TYPO3 conference. Beside skiing and snowboarding during the day evenings are filled with sessions in barcamp style if you wish, or we play some games (werewolves are most likely to be met ;)). Last year in Zillertal most of us took a break on thursday until late noon, and we worked and discussed together. Everything is possible in this unconference setup. For the coming event we are planning a toboggan (canadian sled) evening (on an illuminated run) like we had last year. Our accommodation will be a 4* Hotel again, including half-board, a small SPA area with Sauna and infrared-cabins, WiFi and much more. The rate of € 799,- includes the accommodation (bed in a room with one mate of our great community, 7 nights, half-board), a 6-days skipass valid for 4 different skiing regions and all taxes. For more information, please visit the dedicated website https://t3board17.typo3.org and follow us on Twitter @T3Snowboard, hashtags #T3BOARD and #T3BOARD17. Join us and be a part of the fun!

TYPO3 User eXperience Week (T3UXW17)

T3UXW17 marks the fifth anniversary of this user experience week. As in 2009, 2014, 2015 and 2016, the TYPO3 User eXperience Week 2017, from March 25 to April 1, will be a week dedicated to the improvement of the usability of TYPO3. The Wald und Sporthotel Festenburg is located in the middle of nowhere.  You can simply ease out from irrtitating noises and stressful environment. Only surrounded by forests, the hotel resides in the Nature Park Harz, which is famous for its landscape and world heritage Upper Harz Water Regale. Room reservations and travel costs are covered by sponsoring and T3A budgets. You are more than welcome to sponsor yourself though. You can apply for participation until the end of February. Soon after the closing date you will be informed if your application is accepted. T3UXW is a breeding ground for community collaboration based on inspiration and innovation. Events like this mean a lot for the TYPO3 community and give a lot of motivation for jointly dealing with TYPO3 CMS issues that will give our CMS a competitive edge.

Of course there is always more

One source to keep a close eye on for TYPO3 community news is Marcus Schwemer’s blog typo3worx.eu. Marcus has a nice overview of English and German TYPO3 blogs, a calendar of upcoming events and regularly posts new articles. The blog started a series called Friends of TYPO3 with as a first an interview with Tomas Norre Mikkelsen. Also really valuable is another new format called “TYPO3 Reading List”. Nepomuk Gasteiger compiled a list of 10 resources to start with TYPO3.

Read full article

Aug 25th 2016 news.typo3.org: FLOW3

New certification badges and print certificates

What's new

Thanks to our Design Team, we finally can resolve the situation of only having badges for Certified Integrators. Every announced certification program will now have a badge, which is usable by any certified person, as outlined on the certification program's "Certification Badges" page. Also, the print certificates for all certifications are now complete and we will start shipping them as soon as they arrived. They have changed slightly in color and composition.

Why it is new

Over a year ago, we started a concept for badges, covering multiple certification programs for TYPO3 CMS, Neos, and Flow. With a finished concept and a published implementation of the now deprecated badge, TYPO3 CMS split up with Neos and Flow. Our concept was quite broken, and updating it with our existing ideas did not work due to a variety of guidelines from the design styleguide being in a reworking phase at that time. We had to start over. In addition, we felt that the existing badge from our old concept did not fully represent the modern but simple style that was also introduced with the print certificates introduced at that same time.

Usage

Please have a look a the "Certification Badges" page for the certification you own. You can still use the old badges and logos, but we recommend to update to the new look.

Read full article

Apr 26th 2016 TYPO3 Blogger - FLOW3

Recap of Inspiring Conference 2016

inspiringconference2016

tl;dr

The 5th edition of the Inspiring Conference was the first edition after the split of the Neos Project from TYPO3 community last year and again a great and well organized conference with a good balance of technical talks, best practices and case studies. The Neos community has proven to be still very enthusiastic & really dedicated. In the last 12 months the Neos team has made it’s way into independence with great success.
But despite the great number of product visions the Neos project still lacks a resilient roadmap and timetable for the future and efforts to onboard new integrators to get a broader user base.
The Neos CMS Award could have been a great showcase but unfortunately wasted it’s possibilities due to the poorly chosen presentation environment.

Note: I’ve linked all currently available slides and will update this article when more links become available.

Keynote – Inspiringnote

The conference started with an Inspiringnote by Stefan Willkommer, CEO of the host company TechDivision. Being an experienced mountaineer he compared Neos with his ice axe, the all-in-one tool which is most important for him when climbing in the ice.

Afterwards Robert Lemke talked about the Past, Present and Future of Neos. Last year was marked by the split from the TYPO3 project, the build of an own infrastructure, the move to GitHub and the efforts to create a funding platform to attract new sponsors. A lot of new releases of Flow and Neos have been made, particularly noteworthy is the release of Neos 2.0 and 2.1.

The Neos team is proud that 1und1, a big german hosting provider, uses Neos CMS for managing content of their very own website. And Volkswagen created the After Sales Fleet Tool with Neos. Flow is used for example by DE-CIX and t3n.

Currently the Neos team works hard on establishing the new brand together with a completely new website and a brand-new package repository. Furthermore the launch of an own legal entity like a Neos Foundation, most probably as a community interest company (CIC) is on the agenda.

On the technical side, a rewrite of the Neos user interface with React is in the making. In the future Neos will receive quarterly releases. Flow will continue developing as a standalone product.

For a glimpse into the future of Neos Robert presented the vision of Neos as a content hub and a decoupled Neos to support a headless approach. Regarding new features, the Neos team is heavily dependent on monetary sponsoring.

Neos Product Vision

[Slides] In their talk, Christopher Hlubek and Tobias Gruber first pointed out that Neos was always about User Experience for both, developers and editors. Then they looked back, what Neos already has archived and what topics are currently important to the CMS business like Static Site Generators, Content APIs, a lot of APIs in general, Multi Channel, Content Integrations and Content Streams.
The target market for Neos are still ambitious web content project of all sizes. The vision hasn’t changed and UX still matters. For the future, Neos wants to refactor the UI with React and improve on inline editing, the content repository and content dimensions. The challenges Neos would like to take on are structured editing (e.g. bulk editing), CQRS and event sourcing, a content API and to decouple the components more.
The Flow framework should get improved DDD concepts and CQRS & event sourcing. It will stay independent and a part of the Neos project.
A clear roadmap and timeline for both projects is missing nevertheless.

Neos CMS Award

On the evening of the first conference day, the Neos CMS Award took place for the first time to award the best websites made with Flow and Neos:

Neos CMS Gold Award
H-Hotels – ‪‎Sitegeist

Neos CMS Silber Award
Explorer Fernreisen – ‎mindscreen / HiMedia‬

Neos CMS Bronze Award
EIZO – ‪Dotpulse‬

Excellence Award
Corporate Website – ‪‎Gesagt-Getan‬

Excellence Award
Core Kites – ‪networkteam‬

Excellence Award
günderberater.de – ‪Creativestyle‬

Unfortunately the event and the prize winners didn’t get the attention they deserved. The location and scope of the event were unsuitable. I would have wished for a much better presentation of the projects, some screenshots and more information about why they were chosen as winners.

Hacking Neos

[Slides] Sebastian Kurfürst and Christian Müller gave an overview about all the possibilities for planned and unplanned extension points in Flow and Neos.

Why monolith? Go headless! Using Neos as content API provider

[Slides] Dimitri Pisarev and Wilhelm Behncke presented multiple ways to decouple the website, application or any other consumer from the CMS.

Automation and External service Integration in Neos

[Slides] Dominique Feyer explained how to integrate external services in Neos and Flow and what challenges these news dependencies create regarding downtimes and budgets. His hints are very useful for any kind of web project.

Tasty Neos Recipes for every day

[Slides] Sebastian Helzle picked up on the talk of Aske Ertmann from last year and pointed out that the majority of the recipes from last year are still valid. Afterwards he presented a bunch of new useful recipes.

Long-Pager with Neos – so simple even your clients can do it

[Slides] Jonathan Uhlmann showed an approach how to create a long-pager and handle page sections, links, SEO and what the benefit of his approach are.

Neos Bloopers

[Slides] In his recap Christian Müller outlined a lot of stories about quotes and failed development attempts out of the history of the Flow and Neos project.

The Neos Brand

[Slides] Florian Heinze & Robert Lemke presented the long awaited new logo for Neos and described the process that lead to the new brand guide. At the end of the talk, they officially launched the new version of the Neos website.

Designing Content Types

Karsten Dambekalns described how a content-driven approach to building a website can be put into practice by creating a content strategy first and then implement it in Neos.

Emerging best practices about TypoScript / Content Rendering

[Slides] Sebastian Kurfürst described based of his experience in several projects how to structure TypoScript and to get the most out of the content cache.

Lightning Talks

This type of talk was introduced this year and gave seven speakers the possibility to quickly present a topic in not more than five minutes. This new talk concept was well received by the audience and will be continued next year.

Case Study: architectes.ch

[Slides] Dominique Feyer impressed with his show case about the website architectes.ch that contains more than 2000 reports, 12000 enterprises profiles, 30000 pictures and more than 12 years of archives. The main challenge was the clearing up of the content and then migrating it to Neos.

Pac-Man – Best practices for building Neos and Flow packages

[Slides] Florian Weiss & Dimitri Pisarev presented their approach to build Neos and Flow packages. There is no way to create the perfect package, but here are a lot of possibilities to optimize them.

One more thing

As established last year the „One more thing“ session is a panel discussion about ideas on the Neos team. This year Robert Lemke, Sebastian Kurfürst, Bastian Waidelich and Christopher Hlubek discussed on stage about CQRS & Event-Sourcing.

Der Beitrag Recap of Inspiring Conference 2016 erschien zuerst auf TYPO3 Blogger.

Read full article

Mar 13th 2016 news.typo3.org: FLOW3

Report on codesprint Karlsruhe 3.3-6.3.16

Some TYPO3 Core Developers and a whole bunch of interested contributors met for four days in Karlsruhe at Flagbit to pave the path for the first release of TYPO3 v8.
In total, 21 people managed to merge round about 80 patches to master, not counting bug fixes and improvements applied to the stable branches 7.6 and 6.2. With this amount of activity, we pressed the number of open and pending patches well below 200!
The focus was to improve the backend layout towards a more consistent and intuitive look and feel. Some patches in this regard have been merged, but more energy was put into peripheral aspects. The introduction package and the dependent bootstrap package are now ready for the v8.0 release. Unfortunately, it turned out realurl is not ready for this early sprint release. In order to ship a working introduction package anyway, realurl as a dependency has thus been dropped for the time being.
The "form" extension got quite some love with TYPO3 CMS version 7 already, especially from the great people at Tritum. Three of them joined us in Karlsruhe to further improve this part of TYPO3. As a remarkable milestone it should be mentioned that editors can now use predefined forms registered by an integrator. The form wizard is now directly integrated within the editing view and no standalone component any longer to further improve the editing experience.These features will be part of TYPO3 v8.
Another big chunk of work is worth mentioning: Since version 6.0, a continuing effort provides automated tests for the Core, automatically executed on every patch that is merged by the service of Travis CI. It started with unit tests in version 6.0, with 6.2 functional tests were introduced. With v8 we will see acceptance tests based on codeception and the selenium server entering the stage. The environment is ready and a small group of contributors is busy to provide tests and build up best practices for all of us to use and learn from. This new test suite will verify no new patches destroy the functionality of the backend on a rather high level.
Naturally, when passionate people gather, a lot of discussion arises. This sprint was no execption. Some highly technical and architectural decision have been tackled and decided upon. It is a pleasure on its own to watch our lead architects taking over the whiteboard and engage in heated discussion. 
The majority of sprint participants engaged into what we call casual patch handling. This means we go through the open reviews and pick everything that seems halfway ready. Then, for each of those issues, we strive to move it forward until it is ready to be merged. During this process a lot of new issues may turn up and are fixed on the go, too. This is the kind of work that keeps a group of devs busy at their laptops for 12 hours straight. It is the Flow, this visible process, the feeling of success. In average, we started coding at 10am and generally did not quit before 11pm. Meanwhile our hoster flagbit didn't let us starve. It has been a pleasure to spend those days in Karlsruhe.
After everybody is back home now, the stablisation phase for v8 started. Expect the release two weeks later, if no blockers turn up. In case you are interested in helping out, testing and reporting bugs on the first sprint release of v8, check out the master branch and test it to its limits. This sprint release will be stable and usable in production (if you feel lucky) and will be supported until the release of v8.1.
TYPO3 v8 - miles ahead.

Read full article