RealURL ist eine der meistgenutzten Erweiterungen für TYPO3. Viele Anwender sind jedoch schon an der Konfiguration verzweifelt. Hier sind die Folien zu einem Vortrag anlässlich der TYPO3 Akademie 2011, der sich mit dem Thema RealURL befasst
RealURL ist eine der meistgenutzten Erweiterungen für TYPO3. Viele Anwender sind jedoch schon an der Konfiguration verzweifelt. Hier sind die Folien zu einem Vortrag anlässlich der TYPO3 Akademie 2011, der sich mit dem Thema RealURL befasst
Start vandaag met het maken van eigen Joomla modules!
Wat zijn modules, en hoe kan een zelfgemaakte module het beheer van Joomla versimpelen? We leggen de basis uit van PHP, MySQL en XML en laten zien hoe je eenvoudig zelf een module maakt.
Deze presentatie is gegeven bij de Joomladagen 2016 en verschillende lokale Joomla User Groups.
Presentation on creating a bridge between formal and informal ECM processes in an organisation by using Lotus Quickr ECM. With a focus on desktop connectors to enhance the user with Basic Content Services within daily used content tools.
This document provides information from a CertiFUNcation Day event about website performance. It discusses how page speed matters to both Google and website visitors in terms of conversions, page views, and customer satisfaction. It then outlines specific optimizations that can be made on the backend (e.g. caching, removing unused code) and frontend (e.g. concatenating files, optimizing images, preconnecting resources) of a website to improve performance. Finally, it lists tools that can be used to measure performance like YSlow, PageSpeed Insights, Pingdom, WebPageTest, and GTmetrix.
This document outlines the key changes and new features in TYPO3 CMS 8 LTS. It notes that since the previous LTS version, 249 contributors made over 3,400 commits changing nearly 12,000 files and over 800,000 lines of code. New features for editors include a responsive backend interface, responsive images, improved CKEditor and FormEngine. New features for developers include Fluid as a standalone templating engine, Composer support, Doctrine DBAL and TypeScript support. Meeting and event dates are also provided.
Start vandaag met het maken van eigen Joomla modules!
Wat zijn modules, en hoe kan een zelfgemaakte module het beheer van Joomla versimpelen? We leggen de basis uit van PHP, MySQL en XML en laten zien hoe je eenvoudig zelf een module maakt.
Deze presentatie is gegeven bij de Joomladagen 2016 en verschillende lokale Joomla User Groups.
Presentation on creating a bridge between formal and informal ECM processes in an organisation by using Lotus Quickr ECM. With a focus on desktop connectors to enhance the user with Basic Content Services within daily used content tools.
This document provides information from a CertiFUNcation Day event about website performance. It discusses how page speed matters to both Google and website visitors in terms of conversions, page views, and customer satisfaction. It then outlines specific optimizations that can be made on the backend (e.g. caching, removing unused code) and frontend (e.g. concatenating files, optimizing images, preconnecting resources) of a website to improve performance. Finally, it lists tools that can be used to measure performance like YSlow, PageSpeed Insights, Pingdom, WebPageTest, and GTmetrix.
This document outlines the key changes and new features in TYPO3 CMS 8 LTS. It notes that since the previous LTS version, 249 contributors made over 3,400 commits changing nearly 12,000 files and over 800,000 lines of code. New features for editors include a responsive backend interface, responsive images, improved CKEditor and FormEngine. New features for developers include Fluid as a standalone templating engine, Composer support, Doctrine DBAL and TypeScript support. Meeting and event dates are also provided.
The document discusses the future of TYPO3 CMS. It outlines several pillars for TYPO3 including the community, association, and TYPO3 Inc. TYPO3 Inc. aims to speed up development, provide growth and support. It will create a marketplace and focus on marketing, project support, operational support, lead management, crowdfunding, and training juniors. The future of TYPO3 will focus on topics like marketing automation, personalization, accessibility, SEO, and content channels. It will also improve solutions for editors, developers, and DevOps.
Impress the web bot and the people searching for you - taking seo a bit furtherPatrick Broens
Schema.org is a collaborative effort to create a standard set of schemas for structured data on the internet. It defines common entities, relationships between entities, and an extendable modeling framework. Structured data can be marked up on web pages using HTML5 semantics like article, nav, section etc. or embedded using JSON-LD. Marking up content with Schema.org vocabulary enables rich snippets and potential benefits like increased click through rates for search results.
This document discusses switching from TypoScript to Fluid templating in TYPO3 and provides instructions for configuring Fluid templates and content elements. It encourages the reader to get involved in the community and provides various social media links for further engagement.
Client is King and Agencies are Idiots. Satisfying ignorant clients is not th...Patrick Broens
The document discusses challenges with clients and agencies in web development projects. It notes that clients can often be ignorant and come up with weird ideas, while agencies are mostly idiots. It advocates for clients to become more educated and involved in projects to help overcome these challenges.
The document discusses web accessibility and why it is important. It touches on many people having disabilities or becoming disabled, and that people should not be limited by physical handicaps if their spirit is not disabled. It emphasizes that content is king and interaction is a feature, and that accessibility allows websites to be easily available to everyone. Accessibility can increase traffic from search engines and provides transcripts. It highlights techniques like progressive enhancement, WCAG 2.0 guidelines of being perceivable, operable, understandable and robust, and examples of forms, images and text.
5. Aanbevelingen & eisen
Frontend geen verschil
Terug naar de basis van TYPO3 CMS core
Gebruiksgemak
Geen XML in DB
Verwijder ongebruikte functionaliteit
Documentatie
6. Migratie Voorbereiden
TypoScript van fileadmin en db -> extensie
Herstructureren TypoScript (hiërarchie en naamgeving)
Verplaatsen Resources van fileadmin -> extensie
FCE elementen -> Content elementen
Plugins -> Content elementen
TemplaVoila pagina templates -> Backend Layouts
7. Migratie
One script to Cleanup
One script to Prepare
One script to Convert Plugins
One script to Convert FCE’s
One script to Convert Content elements
8. One Script to rule them all
#!/bin/bash
runTask "cleaner cleanAll"
runTask "preparation prepareAll"
runTask "plugin convertAll"
runTask "fce convertAll"
runTask "cleaner removeLanguage1"
runTask "cleaner resetDoktypes"
9. Schoonmaken
Verwijderen verwijderde records (pagina's en content)
Verwijderen arme 'verweesde' records
Verwijderen lege FCE containers
Verwijdert ongeveer de helft van de pages en
tt_content tabellen! Migratie loopt daarna een stuk
sneller
10. Basis Voorbereiden
Schone Database import: productie -> dev
Backend-Gebruikers en -Layouts Injecteren
Bestands-Synchronisatie: productie -> dev
Onnodige database tabellen en velden verwijderen
Database collatie rechtzetten
Nieuwe database tabellen en velden aanmaken
11. Plugins
Alle informatie uit FlexForms van custom plugins zijn
omgezet naar extra tt_content velden.
Een veld uitlezen uit de database is een stuk sneller
dan een stuk XML uitlezen om dat vervolgens te gaan
parsen.
Aantal extensies teruggebracht van 58 naar 29
12. Flexible Content Elements
It’s magic! Je kunt er ALLES mee!
Zelfs datum en tijd-velden in opslaan :-)
46 FCE types omzetten
Zie vorige sheet!
13. Rechten
Voor een betere gebruikerservaring zijn zo veel mogelijk
velden in de backend uitgeschakeld
Per backend layout, Pagina type, colPos en userGroup
wordt bepaald welke content elementen mogen
worden geplaatst.
15. Visueel Testen
Voor en Na de migratie moet de site er hetzelfde
uitzien. Er zijn alleen wijzigingen 'under the hood'
Lijst met pagina id’s opstellen die gemigreerde
elementen bevatten en deze pagina’s op productie en
dev met elkaar vergelijken
VisualCompare.rb to the rescue