DOCSLIB.ORG

Migrating Multi-Page Web Applications to Single-Page Ajax Interfaces

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Migrating Multi-Page Web Applications to Single-Page Ajax Interfaces Delft University of Technology Software Engineering Research Group Technical Report Series Migrating Multi-page Web Applications to Single-page Ajax Interfaces Ali Mesbah and Arie van Deursen Report TUD-SERG-2006-018 2nd revision SERG TUD-SERG-2006-018 2nd revision Published, produced and distributed by: Software Engineering Research Group Department of Software Technology Faculty of Electrical Engineering, Mathematics and Computer Science Delft University of Technology Mekelweg 4 2628 CD Delft The Netherlands ISSN 1872-5392 Software Engineering Research Group Technical Reports: http://www.se.ewi.tudelft.nl/techreports/ For more information about the Software Engineering Research Group: http://www.se.ewi.tudelft.nl/ c copyright 2006, Software Engineering Research Group, Department of Software Technology, Faculty of Electrical Engineering, Mathematics and Computer Science, Delft University of Technology. All rights reserved. No part of this series may be reproduced in any form or by any means without prior written permission of the publisher. Mesbah & van Deursen – Migrating Multi-page Web Applications to Single-page Ajax Interfaces Migrating Multi-page Web Applications to Single-page AJAX Interfaces Ali Mesbah Arie van Deursen Software Engineering Research Group Software Engineering Research Group Delft University of Technology Delft Univ. of Technology & CWI The Netherlands The Netherlands [email protected] [email protected] Abstract web sites if their user friendliness is inadequate. Many or- ganizations are beginning to consider migration (ajaxifica- Recently, a new web development technique for creating in- tion) possibilities to this new paradigm which promises rich teractive web applications, dubbed AJAX, has emerged. In interactivity and satisfaction for their clients. As a result, this new model, the single-page web interface is composed the well-known problem of legacy migration is becoming in- of individual components which can be updated/replaced creasingly important for web applications. If until a year independently. If until a year ago, the concern revolved ago, the problem revolved around migrating legacy systems around migrating legacy systems to web-based settings, to- to web applications, today we have a new challenge of mi- day we have a new challenge of migrating web applications grating classic web applications to single-page web applica- to single-page AJAX applications. Gaining an understand- tions. ing of the navigational model and user interface structure of The main question addressed in this paper is how to iden- the source application is the first step in the migration pro- tify appropriate candidate single-page components from a cess. page sequence interface web application. Obtaining a clear In this paper, we explore how reverse engineering tech- understanding of the navigational model and user interface niques can help analyze classic web applications for this structure of the source application is an essential step in the purpose. Our approach, using a schema-based clustering migration process. technique, extracts a navigational model of web applica- In this paper, we present a reverse engineering technique tions, and identifies candidate user interface components to for classification of web pages. We use a schema-based clus- be migrated to a single-page AJAX interface. Additionally, tering technique to classify web pages with similar struc- results of a case study, conducted to evaluate our tool, are tures. These clusters are further analyzed to suggest can- presented. didate user interface components for the target AJAX appli- cation. 1. Introduction The rest of this paper is organized as follows. We start out, in Section 2 by exploring AJAX and focusing on its charac- Despite their enormous popularity, web applications have teristics. Section 3 presents the overall picture of the migra- suffered from poor interactivity and responsiveness towards tion process. Section 4 describes our page classification no- end users. Interaction in classic web applications is based on tion and proposes a schema-based clustering approach. Sec- a multi-page interface model, in which for every request the tion 5 outlines how we identify candidate user interface com- entire interface is refreshed. ponents. The implementation details of our tool, called RET- Recently, a new web development technique for creating JAX, are explained in Section 6. Section 7 evaluates a sample interactive web applications, dubbed AJAX (Asynchronous web application and its recovered navigational and compo- JavaScript And XML) [14], has emerged. In this new model, nent model by applying RETJAX. Section 8 discusses the re- the single-page web interface is composed of individual sults and open issues. Section 9 covers related work. Finally, components which can be updated/replaced independently, Section 10 draws conclusions and presents future work. so that the entire page does not need to be reloaded on each user action. This, in turn, helps to increase the levels of in- teractivity, responsiveness and user satisfaction [20]. 2. AJAX Adopting AJAX-based techniques is a serious option not As defined by Garrett [14],SE AJAX incorporates:RG standards- only for newly developed applications, but also for existing based presentation using XHTML and CSS, dynamic display TUD-SERG-2006-018 2nd revision 1 Mesbah & van Deursen – Migrating Multi-page Web Applications to Single-page Ajax Interfaces 1 and interaction using the Document Object Model, data in- Web App Page deltaChange terchange and manipulation, asynchronous data retrieval us- 1..* <<build>> ing XMLHttpRequest, and JavaScript binding everything to- viewChange Widget View gether. deltaUpdate AJAX is an approach to web application development uti- 1..* lizing a combination of established web technologies to pro- <<UI Component>> vide a more interactive web-based user interface. It is the combination of these technologies that makes AJAX unique <<Input>> <<Output>> <<Navigation>> <<Layout>> on the Web. Well known examples of AJAX web applica- Generic Part Specific Part Data tions include Google Suggest, Google Maps, Flickr, Gmail Button Image Tree File Label and the new version of Yahoo! Mail. Tab Panel PanelCell Taskbar 1..* AJAX enables web developers to create web applications Text Anchor Window based on a single-page interface model in which the client- Menubar Select Hidden /server interaction is based merely on state changes. The Secret communication between client and server can take place Textarea Modal asynchronously, which is substantially different from the Radio Checkbox classic synchronous request, wait for response, and continue model [20]. Figure 1. The meta-model of a single-page AJAX Figure 1 shows a meta-model of a single-page AJAX web application composed of UI components. application which is composed of widgets. Each widget, in turn, consists of a set of user interface components. The spe- cific part of the meta-model is target specific, i.e., each AJAX 2. Navigational Path Extraction framework provides a specific set of UI components at dif- ferent levels of granularity. The client side page is composed 3. UI Component Model Identification of client-side views, which are generated by the server-side 4. Single-page UI Model Definition widgets/components. Navigation is through view changes. For each view change, merely the state changes are inter- 5. Target UI Model Transformation changed between the client and the server, as opposed to the full-page retrieval approach in multi-page web applications. Below we briefly discuss each of these steps. The main The architectural decisions behind AJAX change the way focus of this paper is on steps two and three, i.e., finding can- we develop web applications. Instead of thinking in terms of didate user interface components to be able to define a single- sequences of Web pages, Web developers can now program page user interface model. Nevertheless, we will shortly their applications in the more intuitive single-page user in- present how we envision the other steps which are currently terface (UI) component-based fashion along the lines of, for part of our ongoing research. instance, Java AWT and Swing. Retrieving Pages An overview of the architectural – processing, connect- Looking at dynamic web applications from an end-user’s ing, and data – elements of AJAX, and the constraints that perspective enables us to gain an understanding of the ap- should hold between them in order to meet such properties plication without having to cope with the many different as user interactivity, scalability, and portability is given by server-side web programming languages. Building a run- our SPIAR [20] architectural style for AJAX applications. time mirror-copy of the web pages can be carried out by ap- plying static as well as dynamic analysis techniques. Static 3. Migration Process analysis can examine the pages and find href links to other internal pages. Dynamic analysis can help up to re- What we would like to achieve is support in migration from a trieve pages which require specific request parameters (form- multi-page web application to a single-page AJAX interface. based), for instance, through scenario-based test cases or col- In this section we describe the steps needed in such a process. lecting traces of user actions (e.g., sessions, input data) inter- Figure 2 depicts an overall view of the migration process. acting with the web application. It is clear that the more our Note that we are primarily focusing on the user interface and retrieved mirror-copy resembles the actual web application, not on the server-side code (which is also an essential part of the better our navigational path and UI component identifi- a migration process). The user interface migration process cation will be. consists of five major steps: Navigational Path Extraction 1. Retrieving Pages In order to migrate from a classicSE webRG application (source) to a single-page AJAX interface (target), we first need to gain an 2 TUD-SERG-2006-018 2nd revision Mesbah & van Deursen – Migrating Multi-page Web Applications to Single-page Ajax Interfaces Nav. Classic Web The identified list of candidate components along with the Model Nav.
Load more

Recommended publications
  • Build Lightning Fast Web Apps with HTML5 and SAS® Allan Bowe, SAS Consultant
    1091-2017 Build Lightning Fast Web Apps with HTML5 and SAS® Allan Bowe, SAS consultant ABSTRACT What do we want? Web applications! When do we want them? Well.. Why not today? This author argues that the key to delivering web apps ‘lightning fast’ can be boiled down to a few simple factors, such as: • Standing on the shoulders (not the toes) of giants. Specifically, learning and leveraging the power of free / open source toolsets such as Google’s Angular, Facebook’s React.js and Twitter Bootstrap • Creating ‘copy paste’ templates for web apps that can be quickly re-used and tweaked for new purposes • Using the right tools for the job (and being familiar with them) By choosing SAS as the back end, your apps will benefit from: • Full blown analytics platform • Access to all kinds of company data • Full SAS metadata security (every server request is metadata validated) By following the approach taken in this paper, you may well find yourself in possession of an electrifying capability to deliver great content and professional-looking web apps faster than one can say “Usain Bolt”. AUDIENCE This paper is aimed at a rare breed of SAS developer – one with both front end (HTML / Javascript) and platform administration (EBI) experience. If you can describe the object of object arrays, the object spawner and the Document Object Model – then this paper is (objectionably?) for you! INTRODUCTION You are about to receive a comprehensive overview of building Enterprise Grade web applications with SAS. Such a framework will enable you to build hitherto unimaginable things.
    [Show full text]
  • Webbrowser Webpages
    Web Browser A web browser, or simply "browser," is an application used to access and view websites. Common web browsers include Microsoft Internet Explorer, Google Chrome, Mozilla Firefox, and Apple Safari. The primary function of a web browser is to render HTML, the code used to design or "markup" web pages. Each time a browser loads a web page, it processes the HTML, which may include text, links, and references to images and other items, such as cascading style sheets and JavaScript functions. The browser processes these items, then renders them in the browser window. Early web browsers, such as Mosaic and Netscape Navigator, were simple applications that rendered HTML, processed form input, and supported bookmarks. As websites have evolved, so have web browser requirements. Today's browsers are far more advanced, supporting multiple types of HTML (such as XHTML and HTML 5), dynamic JavaScript, and encryption used by secure websites. The capabilities of modern web browsers allow web developers to create highly interactive websites. For example, Ajax enables a browser to dynamically update information on a webpage without the need to reload the page. Advances in CSS allow browsers to display a responsive website layouts and a wide array of visual effects. Cookies allow browsers to remember your settings for specific websites. While web browser technology has come a long way since Netscape, browser compatibility issues remain a problem. Since browsers use different rendering engines, websites may not appear the same across multiple browsers. In some cases, a website may work fine in one browser, but not function properly in another.
    [Show full text]
  • EMERGING TECHNOLOGIES Dymamic Web Page Creation
    Language Learning & Technology January 1998, Volume 1, Number 2 http://llt.msu.edu/vol1num2/emerging/ pp. 9-15 (page numbers in PDF differ and should not be used for reference) EMERGING TECHNOLOGIES Dymamic Web Page Creation Robert Godwin-Jones Virginia Comonwealth University Contents: • Plug-ins and Applets • JavaScript • Dynamic HTML and Style Sheets • Instructional Uses • Resource List While remaining a powerful repository of information, the Web is being transformed into a medium for creating truly interactive learning environments, leading toward a convergence of Internet connectivity with the functionality of traditional multimedia authoring tools like HyperCard, Toolbook, and Authorware. Certainly it is not fully interactive yet, but that is undeniably the trend as manifested in the latest (version 4) Web browsers. "Dynamic HTML," incorporated into the new browsers, joins plug-ins, Web forms, Java applets, and JavaScript as options for Web interactivity. Plug-ins and Applets While Web pages are beginning to behave more like interactive applications, traditional authoring tools are themselves becoming Internet-savvy, primarily through the use of "plug-in" versions of players which integrate with Web browsers. The most commonly used plug-in today is Macromedia's "Shockwave," used to Web-enable such applications as Director, Authorware, and Flash. "Shocked" Web pages can be very interactive and provide a visually appealing means of interacting with users (as in some sample ESL exercises from Jim Duber). Plug-ins are easy to use -- they just need to be downloaded and installed. Some come bundled with Netscape and Microsoft's browsers, which simplifies considerably the installation process (and gives developers the confidence that most users will actually have the plug-in installed).
    [Show full text]
  • Php Tutorial
    PHP About the Tutorial The PHP Hypertext Preprocessor (PHP) is a programming language that allows web developers to create dynamic content that interacts with databases. PHP is basically used for developing web-based software applications. This tutorial will help you understand the basics of PHP and how to put it in practice. Audience This tutorial has been designed to meet the requirements of all those readers who are keen to learn the basics of PHP. Prerequisites Before proceeding with this tutorial, you should have a basic understanding of computer programming, Internet, Database, and MySQL. Copyright & Disclaimer © Copyright 2016 by Tutorials Point (I) Pvt. Ltd. All the content and graphics published in this e-book are the property of Tutorials Point (I) Pvt. Ltd. The user of this e-book is prohibited to reuse, retain, copy, distribute or republish any contents or a part of contents of this e-book in any manner without written consent of the publisher. We strive to update the contents of our website and tutorials as timely and as precisely as possible, however, the contents may contain inaccuracies or errors. Tutorials Point (I) Pvt. Ltd. provides no guarantee regarding the accuracy, timeliness or completeness of our website or its contents including this tutorial. If you discover any errors on our website or in this tutorial, please notify us at [email protected] i PHP Table of Contents About the Tutorial ...........................................................................................................................................
    [Show full text]
  • Creating a Dynamic Web Presence
    CREATING A DYNAMIC WHAT’S INSIDE Key Concepts ......................................1 WEB PRESENCE Static vs. Dynamic Websites ..........1 The need for a dynamic web presence has increased dramatically Features of a Dynamic Site ............2 as consumers on the Internet become more knowledgeable Dynamic Techniques ......................2 and more demanding in having their needs filled. With internet Getting Started ....................................2 technologies continuing to evolve rapidly, small businesses 1. Research and Planning .............2 2. Branding and Web can easily create more interactive sites to engage their Development ..............................4 target audiences. Nuts & Bolts .......................................4 1. Select and Register a Domain Name .........................4 Key Concepts 2. Review Hosting Requirements ...5 Static vs. Dynamic Websites 3. Generate Content ......................6 4. Incorporate Interactive Tools.....6 How do they differ? A dynamic website includes elements that allow 5. Address Security, Privacy interaction with visitors, builds relationships through dialogue, and and Legal Issues ........................9 personalizes the whole web experience. Contrast this with a static, or 6. Get Indexed ..............................10 “read only,” site where there really is no way to know who your visitors are unless they contact you. Whether you are designing a site for the 7. Market Your Website ................10 first time or redesigning a current site, the goal of achieving a dynamic
    [Show full text]
  • Report Google Chrome's Browser
    CISC 322 Assignment 1: Report Google Chrome’s Browser: Conceptual Architecture Friday, October 19, 2018 Group: Bits...Please! Emma Ritcey [email protected] ​ Kate MacDonald [email protected] ​ Brent Lommen [email protected] ​ Bronwyn Gemmill [email protected] ​ Chantal Montgomery [email protected] ​ Samantha Katz [email protected] ​ Bits...Please! Abstract The Google Chrome browser was investigated to determine its conceptual architecture. After reading documentation online and analyzing reference web browser architectures, the high level conceptual architecture of Chrome was determined to be a layered style. Individual research was done before collaborating as a group to finalize our proposed architecture. The conceptual architecture was proposed to coincide with Chrome’s four core principles (4 S’s): simplicity, speed, security, and stability. In depth research was completed in the render and browser engine subsystems which had the architectures styles object oriented and layered, respectively. Using the proposed architecture, the process of a user logging in and Chrome saving the password, as well as Chrome rendering a web page using JavaScript were explored in more detail. To fully understand the Chrome browser, Chrome’s concurrency model was investigated and determined to be a multi-process architecture that supports multi-threading. As well, team issues within Chrome and our own team were reported to support our derivation process and proposed architecture. 1 Bits...Please! Table of Contents Abstract 1 Table of Contents 2
    [Show full text]
  • Pagedown: Paginate the HTML Output of R Markdown with CSS for Print
    Package ‘pagedown’ June 23, 2021 Type Package Title Paginate the HTML Output of R Markdown with CSS for Print Version 0.15 Description Use the paged media properties in CSS and the JavaScript library 'paged.js' to split the content of an HTML document into discrete pages. Each page can have its page size, page numbers, margin boxes, and running headers, etc. Applications of this package include books, letters, reports, papers, business cards, resumes, and posters. Imports rmarkdown (>= 1.16), bookdown (>= 0.8), htmltools, jsonlite, later (>= 1.0.0), processx, servr (>= 0.18), httpuv, xfun, websocket Suggests promises, testit, xaringan, pdftools, revealjs License MIT + file LICENSE URL https://github.com/rstudio/pagedown BugReports https://github.com/rstudio/pagedown/issues SystemRequirements Pandoc (>= 2.2.3) Encoding UTF-8 RoxygenNote 7.1.1 NeedsCompilation no Author Yihui Xie [aut, cre] (<https://orcid.org/0000-0003-0645-5666>), Romain Lesur [aut, cph] (<https://orcid.org/0000-0002-0721-5595>), Brent Thorne [aut] (<https://orcid.org/0000-0002-1099-3857>), Xianying Tan [aut] (<https://orcid.org/0000-0002-6072-3521>), Christophe Dervieux [ctb] (<https://orcid.org/0000-0003-4474-2498>), Atsushi Yasumoto [ctb] (<https://orcid.org/0000-0002-8335-495X>), RStudio, PBC [cph], Adam Hyde [ctb] (paged.js in resources/js/), Min-Zhong Lu [ctb] (resume.css in resources/css/), Zulko [ctb] (poster-relaxed.css in resources/css/) Maintainer Yihui Xie <[email protected]> Repository CRAN Date/Publication 2021-06-23 04:40:05 UTC 1 2 business_card R topics documented: book_crc . .2 business_card . .2 chrome_print . .3 find_chrome . .5 html_letter . .5 html_paged . .6 html_resume .
    [Show full text]
  • Fiz: a Component Framework for Web Applications
    Fiz: A Component Framework for Web Applications John K. Ousterhout Department of Computer Science Stanford University Abstract Fiz is a framework for developing interactive Web applications. Its overall goal is to raise the level of programming for Web applications, first by providing a set of high-level reusable components that simplify the task of creating interactive Web applications, and second by providing a framework that encourages other people to create addi- tional components. Components in Fiz cover both the front-end of Web applications (managing a browser-based user interface) and the back end (managing the application's data). Fiz makes it possible to create components that encapsulate complex behaviors such as Ajax-based updates, hiding many of the Web's complexities from applica- tion developers. Because of its focus on components, Fiz does not use mechanisms such as templates and model- view-controller in the same way as other frameworks. ger and more useful structures. We will release Fiz in 1 Introduction open-source form and hope to build a user community Although the World-Wide Web was initially conceived that creates an ever-increasing set of interesting com- as a vehicle for delivering and viewing documents, its ponents, which will make it dramatically easier to cre- focus has gradually shifted from documents to applica- ate applications that advance the state-of-the-art in Web tions. Facilities such as Javascript, the Document Ob- interactivity. ject Model (DOM), and Ajax have made it possible to offer sophisticated interactive applications over the The rest of this paper is organized as follows.
    [Show full text]
  • Features Guide [email protected] Table of Contents
    Features Guide [email protected] Table of Contents About Us .................................................................................. 3 Make Firefox Yours ............................................................... 4 Privacy and Security ...........................................................10 The Web is the Platform ...................................................11 Developer Tools ..................................................................13 2 About Us About Mozilla Mozilla is a global community with a mission to put the power of the Web in people’s hands. As a nonprofit organization, Mozilla has been a pioneer and advocate for the Web for more than 15 years and is focused on creating open standards that enable innovation and advance the Web as a platform for all. We are committed to delivering choice and control in products that people love and can take across multiple platforms and devices. For more information, visit www.mozilla.org. About Firefox Firefox is the trusted Web browser of choice for half a billion people around the world. At Mozilla, we design Firefox for how you use the Web. We make Firefox completely customizable so you can be in control of creating your best Web experience. Firefox has a streamlined and extremely intuitive design to let you focus on any content, app or website - a perfect balance of simplicity and power. Firefox makes it easy to use the Web the way you want and offers leading privacy and security features to help keep you safe and protect your privacy online. Mozilla continues to move the Web forward by pioneering new open source technologies such as asm.js, Emscripten and WebAPIs. Firefox also has a range of amazing built-in developer tools to provide a friction-free environment for building Web apps and Web content.
    [Show full text]
  • 5Lesson 5: Web Page Layout and Elements
    5Lesson 5: Web Page Layout and Elements Objectives By the end of this lesson, you will be able to: 1.1.14: Apply branding to a Web site. 2.1.1: Define and use common Web page design and layout elements (e.g., color, space, font size and style, lines, logos, symbols, pictograms, images, stationary features). 2.1.2: Determine ways that design helps and hinders audience participation (includes target audience, stakeholder expectations, cultural issues). 2.1.3: Manipulate space and content to create a visually balanced page/site that presents a coherent, unified message (includes symmetry, asymmetry, radial balance). 2.1.4: Use color and contrast to introduce variety, stimulate users and emphasize messages. 2.1.5: Use design strategies to control a user's focus on a page. 2.1.6: Apply strategies and tools for visual consistency to Web pages and site (e.g., style guides, page templates, image placement, navigation aids). 2.1.7: Convey a site's message, culture and tone (professional, casual, formal, informal) using images, colors, fonts, content style. 2.1.8: Eliminate unnecessary elements that distract from a page's message. 2.1.9: Design for typographical issues in printable content. 2.1.10: Design for screen resolution issues in online content. 2.2.1: Identify Web site characteristics and strategies to enable them, including interactivity, navigation, database integration. 2.2.9: Identify audience and end-user capabilities (e.g., lowest common denominator in usability). 3.1.3: Use hexadecimal values to specify colors in X/HTML. 3.3.7: Evaluate image colors to determine effectiveness in various cultures.
    [Show full text]
  • Lecture 6: Dynamic Web Pages Lecture 6: Dynamic Web Pages Mechanics • Project Preferences Due • Assignment 1 out • Prelab for Next Week Is Non-Trivial
    Lecture 6: Dynamic Web Pages Lecture 6: Dynamic Web Pages Mechanics • Project preferences due • Assignment 1 out • PreLab for next week is non-trivial 1/31/2020 2 Lecture 5: JavaScript JavaScript has its Quirks • Procedural, Functional and Object-Oriented all at once • Objects are very different from Java/C++ o Newer versions have Java-like classes however • Scoping is different o var versus let or const o Declarations can follow uses o Declarations are optional • Automatic type conversion • Strict versus non-strict equality testing • eval function • Semicolons are optional if unambiguous • Read up on the language (prelab) 1/31/2020 3 Lecture 6: Dynamic Web Pages What is an Interactive Application • How do we want to use JavaScript • What does interactive mean • What does it do when you interact o Check inputs, compute next page o Change the page without getting a new page 1/30/2020 4 Lecture 6: Dynamic Web Pages Dynamic Web Page Examples • http://bdognom.cs.brown.edu:5000/ (spheree) • http://conifer.cs.brown.edu/s6 (s6) • http://conifer.cs.brown.edu:8888 (twitter) • http://fred4.cs.brown.edu:8800/ (sign) 1/23/2020 5 Lecture 6: Dynamic Web Pages Interactive Applications • Respond to user inputs • Change the display (e.g. add fields, show errors, …) • Dynamically check and verify inputs • Allow direct manipulation (drag and drop) • Use animation to highlight or emphasize or show things • Display external changes in real time • Provide input help (e.g. text completion) • Handle dynamic resizing of the display 1/23/2020 6 Lecture 6: Dynamic Web Pages Achieving Interactivity • Using CSS • Handling HTML events using JavaScript o Dynamically check and verify inputs o Handle direct manipulation • With modern HTML features • With animation/drawing/multimedia packages • By talking to the server continually • Displaying external changes in real time • Changing styles and the content of the page o Change the display (e.g.
    [Show full text]
  • Create a Web Page Using Microsoft Word
    Create a Website for Denise Harrison’s English Writing Class Prepared by the Student Multimedia Studio Visit http://www.library.kent.edu/sms for more information and tutorials. Contents What you will be creating (in a nutshell): ........................................................................... 1 Create a Folder on your Jump Drive ................................................................................... 1 Create the “Documents” ..................................................................................................... 1 Create the Web Page ........................................................................................................... 2 Create a “table” ........................................................................................................................... 2 Center the Table on the Page ...................................................................................................... 3 Set the Preferred Width for the Table......................................................................................... 3 Add a Title .................................................................................................................................... 3 Add a Row for the Navigation Menu ........................................................................................... 3 Create the Text Hyperlinks to the Word Documents .................................................................. 4 Add another row for more content ............................................................................................
    [Show full text]