Newlands TYPO3 powered Consultation and Planning

1. About this document

The complete work stages for the new website to be done in TYPO3 7 LTS version 7.6.6. information containing the work stages, step by step instructions with estimate of hours for each step involved. Various options in developing the new website.

2. Preface

2.1 TYPO3 4.5 is still in use, now what: upgrade to TYPO3 6, 7 or 8 or equal to relaunch?

Since 2011, the TYPO3 4.5 version is on the market. It is the first Long Term Support version - short LTS - the TYPO3 Association. With the LTS version, the TYPO3 Association is committed, at least for 3 years for the version to develop security and bugfix updates and posting. Meanwhile LTS and the end of 2015 TYPO3 7.6 LTS were published in 2014 TYPO3 6.2. Most recently, March 2016 was published TYPO3 8. It's official: TYPO3 4.5 is no longer supported for a year and is becoming obsolete. Even the commercial Extended Support through the TYPO3 Association is now set. It is the time for action - but what's best: an upgrade to TYPO3 6.2, 7 or 8 or even better a relaunch? It comes as always important.

2.2 TYPO3 4.5 is a security risk

TYPO3 4.5 should no longer be used for safety reasons. For over a year there is no official security updates more for this version, and it became known several vulnerabilities since. Another security risk is the supported version of PHP, TYPO3 4.5 is officially only compatible to PHP 5.5. PHP 5.5 reached the End of Life status on 07.10.2016, then there is no more security updates for PHP 5.5.

2.3 Better Responsive support version 6

In addition to the critical safety aspects has TYPO3 4.5 yet another drawback: it does not feature for Responsive Webpages. Starting with version 6 provides TYPO3 better support for Responsive Webpages with Responsive Images. Whether the website has a B2B or B2C orientation does not matter, must optimized for mobile devices. Smartphone and tablet have become indispensable in the professional and private life. Otherwise, this has a negative impact on the search engine optimization of the website.

2.4 Upgrade to TYPO3 6.2 LTS, LTS 7.6 or Version 8

TYPO3 can not upgrade directly from 4.5 to 7'er or 8'er branch itself, the migration path must be respected. Who wants to upgrade his TYPO3 4.5 system, so must first upgrade to TYPO3 6.2 to then upgrade to Version 7.6 LTS, which will be supported in nearly 3 years by the TYPO3 Association with bugfix and security updates. The support of the TYPO3 6.2 LTS runs until 31.03.2017. Now already upgrade to version 8, is not advisable. On one hand, the long-term support version (LTS) planned for the end of March 2017 and the other part is TYPO3 8 5 no longer versions but only with PHP 7 compatible with PHP, what is more problematic for a number of extensions. Basically, usually only makes sense to upgrade after the release of the LTS version. Only if absolutely certain new feature of version 8 is required, it may be sensible to use the version.

Roadmap for Long Term Support of the TYPO3 Association. The bright-orange phase is commercial Extended Support after the official end of life of TYPO3 version. Source: https://typo3.org/typo3-cms/roadmap/

2.5 Upgrade versus Relaunch or the final solution

As for the cost, so can a relaunch sometimes be more meaningful than to perform multiple upgrades succession. In particular, the upgrade from version 4.5 to 6.2 TYPO3 is complicated since changed up some of the core functionalities such as switching to FAL (File Abstraction Layer). And then until March 2017, the upgrade to TYPO3 7.6 LTS, because from then ends the official support of 6.2.

Basically, the upgrade costs of the complexity of the individual TYPO3 system and the employed are Extensions dependent: For example, if all extensions upgradeable because updates in the TYPO3 Repository for which extensions or have to be adjusted manually during the upgrade.

If a website is not in Responsive Web design is or a mobile version has a relaunch may be more meaningful than upgrade. But this has mainly to do with the scope of the content. There is no simple content migration at a relaunch - unless that most of the content are set in records and not on content pages. All this is true, it usually weigh.

Thus, this is a major update of the current TYPO3 website as the present site uses old and outdated TYPO3 4.5 version. This means that there will be no security and important bug fixes for TYPO3 4.5 anymore and the rebuild using TYPO3 7 LTS is crucial. And The same is for design of the current website that needs to be modified. Please check the section 4 - “Design of the website pages” below for details. So I do believe that the rebuild of the current TYPO3 4.5 website using TYPO3 7 LTS is an answer. 3. Introduction to TYPO3 7 LTS

3.1. About TYPO3 7 LTS

The new version of TYPO3 CMS 7 LTS will be supported for three years as part of the Long Term Support from the TYPO3 CMS team. The completely redesigned, modernized interface has been equipped with uniform color and clear descriptions and been fully developed in Responsive Design. Furthermore, the functionality for image processing is now being integrated into TYPO3. The most striking new feature is the new backend interface that allows editors and integrators to work efficiently. A tidy login screen, simpler structures and the integration of previously distributed components in a web application enable consistent use. Customized images and buttons highlight actions and information boxes. All forms, , sections and are based on a uniform look and feel.

3.2. Revamped TYPO3 Backend

The biggest visible change is the restructured TYPO3 Backend which has received a full facelift, but also builds on simple Bootstrap 3 - based HTML5 and LESS/CSS3 as well as RequireJS and jQuery. This also marks the TYPO3 Backend as responsive.

A lot of other features are now available, such as default content elements based on the templating engine Fluid, Avatars for backend users, all new confirmation boxes, a new flexible search for as well as improvements when uploading new files.

3.3. Increase in performance

The speed of the TYPO3 Backend has been improved by separating JavaScript code from PHP and HTML. Fluid, the rendering engine also used in most of places of the TYPO3 Backend now, has gained performance boosts, making the TYPO3 backend feel more like a real web application.

3.4. Up to four times faster

By streamlining all of the components and using the latest technologies, the backend is significantly faster compared to previous versions. Many actions are now based on AJAX and a more efficient AJAX API for communications replaces the previous standard dialogs for confirmations. The Content Management is now responsive and allows for contents to be edited on touch-based mobile devices such as tablets and smartphones. All editors and administrators can now insert an avatar image to personalize their access. The dial-in screen, the TYPO3 logo and all styles can now be replaced by a project-specific layout.

3.5. New features for editors Working with online media such as YouTube or Vimeo Videos is now much easier. Links can now be referenced under "Text and Media," a preview is then shown, and can be organized like any other content in the File List module. The functionality "Image Manipulation" allows for cropping of images in the backend without the file being changed. If a file upload will overwrite existing files, you can specify whether multiple files should be moved, renamed or be skipped by performing an action. In addition, minor improvements have been integrated such as the display of the remaining number of characters in a text box.

3.6. New features for integrators

With TYPO3 CMS 7, integrators receive a new standard way of providing content items that are processed based on the fluid templating engine. The new extension "Fluid-styled Content" can be used to change certain content elements on websites via Fluid/HTML templates very quickly. Many TypoScript options are now available in standardized form to simplify configuration. Even the generation of forms is significantly easier because it is based on Fluid and Extbase.

3.7. New features for administrators

Administrators can now load the TYPO3 sources and all of the required extensions via the standardized PHP Package Manager "Composer." A central information system shows important system features in the latest version at a glance. In addition, backend user groups can be managed just like individual users in a separate module.

3.8. New features for developers

Thanks to a completely new approach to the backend interface that is based on Twitter Bootstrap 3, LESS/CSS3, HTML5, RequireJS and jQuery, TYPO3 CMS 7 makes it easier to add individual modules with simultaneous use of all standard rendering definitions and adapted, ready-to-use components. All PHP and Extension developers will benefit from the easy extension of the TYPO3 core system, which is completely based on PHP 5.5+ and allows for PHP7 and MySQL Strict Mode to be used. TYPO3 can thus be integrated into other PHP applications by using the Composer. With 8,500 unit tests and 700 functional tests, the TYPO3 core has proven itself in numerous application scenarios.

4. Design of the website pages

Websites that can be handled fully functional on tablets and mobile devices get more relevant each day, as the usage of mobile devices browsing the web increases dramatically. And it is a huge benefit for your website to be compatible with mobile and tablet devices ("mobile-friendly"). This increases visibility of your web site. People can browse your website anywhere from any device. So this is a major task to adapt your website and to make it really "mobile- friendly".

As discussed, I'll create the HTML/CSS designs for the website pages such so the tablet / smartphone version shows the header (logo, horizontal image e.t.c.) and then "Menu" (if someone taps it, it will expand like in the ktlo.com) and then the content of the "Welcome" page on homepage (if someone starts to scroll down, it will show the rest of the page).

I think that it'll take me about 4 - 5 hours to create responsive HTML/CSS for the website pages. It could include changing of header and adding the footer.

5. Development Work Stages in details 5.1 Developing ( adopting existing ) HTML/CSS templates for site pages

5.2 Developing Fluid templates for website pages

5.3 Developing ( adopting existing ) CSS-s to work in TYPO3 environment

Points 5.1 – 5.3. The development of Fluid templates could take few hours.

5.4 Creating the website page tree

This could take few hours to create the website page tree as it has the current site.

5.5 Developing basic TypoScript code

In short this means developing of such parts of the website as navigation menus, website header and footer using TypoScript. Adding the TypoScript configuration settings and applying the page object using Fluid templating engine.

I do believe that it could take up to 5 hours to program all the required TypoScript code mentioned above.

5.6 Adding languages support (if needed ?) 5.7 Configuring ( adopting ) existing extensions to work with site

List of TYPO3 extensions to configure(adopt) : 5.7.1 News System

Versatile news extension, based on extbase & fluid. Editor friendly, default integration of social sharing and many other features.

It could take me 1 - 2 hours to integrate such mews system functionality.

5.7.2 Contact Form

A very basic contact form for your TYPO3 site. It provides a very basic contact form for your TYPO3 site. Fields included are 'name', 'street', 'city', 'phone', 'email', 'message' and a 'contact by' field to let the user choose between 'phone' and 'email'.

Mandatory fields can be defined in TypoScript and default to 'name', 'message' and either 'email' or 'phone' depending on the user's selection. Unwanted fields can simply be removed from both form and email templates without breaking stuff.

It is possible to provide some spam protection. Please check an example how it woks here: http://www.speleo.me/get-in-touch/contact/

It could take me 1 - 2 hours to integrate such contact system functionality.

5.7.3 Newsletter System

Integration of an advanced Direct Mail/Newsletter mailer system with sophisticated options for personalization of emails including response statistics in conjunction with frontend subscription plugins such as Direct Mail Subscription or Email Address Subscription.

This extension handles the backend generation and mailing of newsletters. Extension Direct Mail (extension key: direct_mail) requires TYPO3 6.2.2+ and PHP 5.3.3+.

I do believe that it could take up to 3 hours to install, configure and also test the newsletter system by sending the test newsletter page.

5.7.4 Reservation System

As a reservation system it is possible to integrate a front-end plugin to show and book custom resources for example lodges. It allows the management of bookable resources. Bookable resources, like storage spaces, rentable property or various other contexts can be viewed and booked by date period from new contacs.

It has the following features:

Calendar

 Shows occupancy of resources;  Multiple resources per page, each with it's own calendar;  Multi-localization; Reservation Form

 Automatic messaging about new booking requests;  Input fields for contacts configurable;  Validation;  Date picker;  Spam protection;  Contacts and reservations saved;  Reservations can be accepted automatically or be reviewed

I really think that it could take me about 2 - 3 hours to install, configure and also test the reservation system.

5.7.5 Reviews or Feedback

I'm able to integrate the rating functionality that provides a rating for every type of content in the database. Every field of every table can be defined as a so-called 'ratingobject' that can be used for ratings.

Featurelist: - display ratings (graphically or text); - support for AJAX-ratings (graphically or text); - one-time voting for logged in FE users; - multiple anonymous votings; - highly customizable look for ratings, incl. support for vertical ratings

Example screenshot. Classic ratings

5.7.6 Photo Gallery (if needed) 5.7.7 Sitemap

Integration of easy to use sitemap generator for pages and records.

It could take not more than an hour to integrate a sitemap functionality.

5.8 Developing new extensions (if needed)

5.9 Populating site with static data 5.10 Preliminary testing 5.11 Fixing issues (if needed)

6. Search Engine Optimization stages

Adding such important features as 6.1 Real URL

RealURL makes TYPO3 URLs search engine friendly. The extension provides automatic transformation of URLs with GET parameter in the frontend (like “index.php? id=123&type=0&L=1”) into a virtual path, a so called “Speaking URL” (like “dutch/contact/company- info/page.html”) and back again. The objective is that URLs shall be as human readable as possible.

I do believe that it could take me not more than an hour to get the RealURL extension to work properly.

6.2 SEO XML Sitemap

When it comes to improve your rankings, a XML sitemap can be a really good partner. This protocol helps and other main search engines to easily understand your website structure while crawling it. It was first introduced by Google in 2005, with MSN and Yahoo offering their support to the protocol a year later. are known as URL inclusion protocols as they advise search engines on what to crawl. It comes in opposition to robots.txt files that are an exclusion protocol as it tells search engines what not to crawl.

The website Blue Corona made a good comparison between a XML sitemap and a blueprint for a house: “Think of your website as a house and each page of your site as a room. You can think of a XML Sitemap like a blueprint for your house and each web page were a room, your XML Sitemap would be a blueprint—making it easy for Google, the proverbial home inspector of the web—to quickly and easily find all the rooms within your house.” In other words, a XML sitemap will ease Google to find your pages when it crawls your website because all your pages could be ranked, not only your website as a domain. It informs search engines about pages on their sites that are available for crawling. While having no XML sitemap is not penalized, creating yours is highly recommended because it can improve your SEO.

Why should you get a XML sitemap Like we said, having an efficient XML sitemap can improve your rankings. But this is particularly useful when:

You have a website with a complicated structure or many internal links Your site is a new one or if you have just a few external links Your site is consistent and have archived content Your website has dynamic pages (mainly occurs for e-commerce website). Benefits of having a XML sitemap Having a sitemap on your site passes more data to search engines. So it also:

Lists all URLs from your site. And this includes pages that would not have been foundable by search engines Gives engines page priority and thus crawl priority. You can add a tag on your XML sitemap saying which pages are the most important. Bots will thus first focus on this priority pages. Gives temporal information. You can also include two other optional tags that will pass extra data to search engines to help them crawl your website. The first one, “lastmod’ informs them when a page last changed. The second one, “changefreq” tells how often a page is likely to change. Gives you information back from the Google Webmaster Central. You can access activity for instance.

I do believe that it could take me about 3 hours to integrate the XML Sitemap for SEO as it also needs to submit the sitemap to various search engines such as Google or Bing.

6.3 On-page features for search engine optimization

It enables important on-page features for search engine optimization (SEO) and expands the page settings e.g. with a preview for results.

Features advanced page settings preview for search results on google override browser title href lang support canonical url no index open graph twitter cards  set automatically the path segement from RealURL while creating a new page  example for robots.txt  migrate properties from metaseo and seo_basics Screenshot 1. Advanced Page Settings

Screenshot 2. Social Media TAB

Search engine optimization represents an integration of such extensions as: 6.4 Basic SEO Features

Adds a separate field for the title-tag per page, easy and SEO-friendly keywords and description editing.

Integration of features described in points 6.3 and 6.4 could take about an hour or even less.

7. Statistics

7.1 Adding the statistics system

This could be for example integration of the third party AWStats into TYPO3 as backend module and AWStats statistics in the Web-Section . The extension includes a module for administrators. Externally generated log files can be configured to be analyzed by AWStats like the TYPO3 generated ones.

From http://awstats.sourceforge.net/ :

“ AWStats is a *free powerful and featureful tool that generates advanced web, streaming, ftp or mail server statistics, graphically* . This *log analyzer* works as a *CGI or from command line* and shows you all possible information your log contains, in *few graphical web pages* . It uses a partial information file to be able to process large log files, often and quickly. It can analyze log files from all major server tools like Apache log files (NCSA combined/XLF/ELF log format or common/CLF log format), WebStar, IIS (W3C log format) and a lot of other web, proxy, wap, streaming servers, mail servers and some ftp servers.”

7.2 Integration of

Google Analytics is a free Web analytics service that provides statistics and basic analytical tools for search engine optimization (SEO) and marketing purposes. The service is available to anyone with a . Google bought Urchin Software Corporation in April 2005 and used that company’s Urchin on Demand product as the basis for its current service.

DEFINITION Google Analytics

Posted by: Margaret Rouse WhatIs.com

Sponsored News Better Together: Hadoop and Your Enterprise Data Warehouse –SAS Institute Inc. Information in Action: Europe’s Year of Sport –Veritas See More Vendor Resources Introduction to Web Analytics for E-Commerce: How to Track Activity to Optimize... –GeoTrust, Inc. HR Analytics Adds New Feel to the Human Touch –SearchFinancialApplications Google Analytics is a free Web analytics service that provides statistics and basic analytical tools for search engine optimization (SEO) and marketing purposes. The service is available to anyone with a Google account. Google bought Urchin Software Corporation in April 2005 and used that company’s Urchin on Demand product as the basis for its current service.

Google Analytics features include:

• Data visualization tools including a dashboard, scorecards and motion charts, which display changes in data over time.

• Segmentation for analysis of subsets, such as conversions.

• Custom reports.

• Email-based sharing and communication.

• Integration with other Google products, such as AdWords, Public Data Explorer and Website Optimizer.

Google Analytics is geared toward small and medium-sized retail websites. The service has limitations that make it less suited to more complex websites and larger enterprises. For example, the system collects data through a JavaScript page tag inserted in the code of pages the user wants to collect data on. The page tag functions as a Web bug to gather visitor information. However, because it’s reliant on cookies, the system can’t collect data for users who have disabled them. Google also uses sampling in its reports rather than analyzing all available data.

Furthermore, some security experts have raised concerns about privacy issues in Google Analytics. Through the Google Analytics Dashboard, users can collect information on people whose websites link to social networking sites such as Facebook and Twitter.

Google Analytics is the most broadly utilised website statistics service, actually in use on around 55% of the 10,000 most well liked websites.Google Analytics is a service suggested by Google that generates comprehensive statistics about a website's traffic and traffic sources and assesses alterations and sales.

Really Google Analytics is a great SEO tool offered by major search engine to check out the useful statistics of websites. It is easy to use and can determine everything ranging from the conversion rates to bounce rates of your website. Many SEO companies follow this tool while promoting websites online. It help companies to analyze which marketing activity is capturing the best traffic to your site and help to get positive results on search engines.

7.3 Piwik integration

Integration of Piwik into TYPO3 powered website. Piwik is a free Free Open Source Website Analytics Software. Adding the asynchronous Piwik JS tracking code in the footer of all the website pages.

Integration of features described in points 7.1 - 7.3 could take about 3 – 4 hours. Please note that it also needs to do administration tasks using Google Webmaster Tools and Google Analytics Dashboard to integrate the Google Analytics tracking code for the website. So it takes time. It additionally needs to be tested.

8. Future Upgrade Notes and Support

TYPO3 CMS 7 LTS will be supported by Long Term support until April 2017 including maintenance and bug fixes, as well as security and important bug fixes until November 2018. It would be easy for me to upgrade TYPO3 core if a new version is introduced.

So I'm ready to support you after the website is finished to do the upgrades if necessary. For your information current stable latest TYPO3 CMS 7 version is 7.6.9 (2016- 05-24).

9. Summary

To conclude, the whole project could take about 25 - 30 hours. But if there is no need in any of the described below features the resulted amount of hours could be decreased accordingly. Also if you need any new functionality the time (hours) could be set on the fly before the development of required feature.

10. Additional Notes

As I wrote before, if needed I'm able to develop new custom TYPO3 extension(s) if none of the available in repository is not suitable for the given purpose.

Also please note that I decreased an amount of hours a little bit because it is a bigger project. Please let me know if you have any questions.