1. Porting methodology Porting of an WEB Site using PTK To insert your company logo on this slide From the Insert Menu Select “Picture” Locate your logo file Click OK To resize the logo Click anywhere inside the logo. The boxes that appear outside the logo are known as “resize handles.” Use these to resize the object. If you hold down the shift key before using the resize handles, you will maintain the proportions of the object you wish to resize.

2. The list of the porting phases 1.Structuring the site content and reviewing the generic page design 2.Building the main categories 3.Building the services 4.Standardising the page format 5.Checking the broken links 6.Checking the look & feel 7.Delegating content management authority

3. Phase 1 – Structuring the site content and reviewing the generic page design The original website pages and the migrated ones should look exactly the same from a user’s point of view, with the sole notable exception of the improved services (ie. News and FAQs) The original logical structure remains the same, so we already have all the necessary elements to start to implement with Yihaw the hierarchical Directory

4. The generic page structure According to a true portal approach, the structure is consistent through all the pages of the site: A standard header (containing specific logos, banners etc) at the top of page; A left-hand side (LHS) navigation panel, containing links to the portal channels and other sites and services; A standard footer, at the bottom of pages; The content area, which is the only page-specific and therefore variable element, located in the central part of the page.

5. Phase 2 – Building the main categories  Define the hierarchical structured of the physical environment, that is establish the physical repository, made up of a combination of standard and Yihaw folders, which will contain all the Zope and Yihaw objects that make up the portal pages.  Fill up the repository with the appropriate objects to build up the pages containing the information related to the various categories and sub-categories.

6. Building the main categories For each of the chosen main categories (ie. Information, Products, Research) a standard folder has been created. Under these folders, a sequence of Yihaw folders “translated” from the previous static standard html pages must be built.

7. Building the main categories Depending on the information derived from the standard html objects before the porting, different objects should be adopted for the new portal version, according to the following rules:  the original folders became Yihaw folders, with the exception of the main categories, which became root folders  the original standard files became "Yihaw files".  the standard images have remained standard images  the previous static html pages, depending on their content, have been changed into ZOPE dtml Documents, Yihaw URLs, Yihaw Pointers, Yihaw Tops, ZOPE dtml Methods

8. Transformation rules applied for the html pages  a html document containing descriptive text -> a simple dtml document with previously contained text;  a html document containing a list of URLs has -> a set of Yihaw URLs;  a html document content -> Yihaw pointer when internal cross-links were necessary;  a html document content -> Yihaw top when internal links where necessary in the home-page or in parent folders;  a html home-page or section page -> a dtml method;  a html document containing an URL requesting an access to the database -> the Zope object "Section Value"

9. Phase 3 – Building the services The services available through the initial site had already been defined and consisted of:  News repository  Meetings and events repository  FAQ repository and they were integrated by web forms submitting e-mails later processed by the webmaster.

10. Services building - News The news services consist of the "add your news", "read news" service, "consult newsletter and related print-outs" section. The news items themselves can be placed in any Yihaw folder, and they will work in the same way:  all news items in the same folder (simplicity for the administrator)  topic-related news items in different folders The news mechanism should be implemented by adding "Yihaw News Items" inside the \news Yihaw folder.

11. Services building – FAQs The FAQ (Frequently Asked Questions) is based the Yihaw FAQ item. The FAQ channel should be accessible directly from the site home-page. Distributed content management is available by using the ZOPE and Yihaw environment standard facilities. The single FAQ items has been created as a different Yihaw FAQ item, by using the function "add Yihaw FAQ item" from the Zope management panel

12. Phase 4 – Standardizing the page format Standardisation of the generic page format has been implemented via templates and the cascade style-sheets (CSS) so the common look of all the pages is delegated to such objects Once the standard has been defined, all the pages share the same common part (navigation panel, header and footer) and the dynamically generated content has the same look-and-feel (fonts, colours, size and so on).

13. Standardizing the page format The standard page format basically consists of the files: Cascade Stylesheet \standard_html_header \standard_html_footer

14. Applied methodology The standardisation process consisted of the following activities: develop an original full-page template as a dtml document; identify the content area for the page; split the template into a html-header and a html-footer develop code for error-management of the dtml documents applicable to the previous template page; develop a CSS (Cascade Style-Sheet) and apply it to header and footer, making also available the standard styles to the content area.

15. Phase 5 – Checking the broken links This function is quite critical, since the link-check is a focal and often resource consuming issue for the web management, and will be object of further developments. In this phase a special Yihaw dtml method has been made available: the "Yihaw-broken-link". Such method allows to check the internal broken-links, since Yihaw is a "Directory" environment which expose directory facilities.

16. Phase 6 – Look-and-feel control The look-and-feel test needs to be performed: this consisted of the control of the page layouts as they appear over the browser, once entire set of pages has been built. For this purpose, pages must be submitted both to a technical and non-technical user, already familiar with the original pages (before the porting) of the ported ones.

17. Phase 7 – Delegating content management authority Administration should be turned over to others as you traverse the folders in a URL. The administrators at each level can define new administrators below their folder => passing the work down the hierarchy. Some (simple) training for the delegating users must be provided.

18. Delegating content management authority The four key components of Zope security are: users – people (groups of people) roles – kinds of responsibility (ie. Manager, Author, etc.); provide linkage between authentication and authorization permissions – are specific to objects acquisition – a mechanism for sharing information among objects contained in a folder and in subfolders

19. Delegating content management authority Create a new role sufficiently high in the Zope hierarchy, with the following permissions: "Add Yihaw Objects“ "Delete Objects“ "Manage properties“ "Use mailhost services“ "View management screens“ "Manage Yihaw Objects"

20. Delegating content management authority Letting someone from each department to maintain the content of the directory for their own branch comports: assigning each user a local role or creating an acl_users folder and create the user there.