File Transfer Web Application Madhavi Dintakurthy Governors State University

Total Page:16

File Type:pdf, Size:1020Kb

File Transfer Web Application Madhavi Dintakurthy Governors State University Governors State University OPUS Open Portal to University Scholarship All Capstone Projects Student Capstone Projects Spring 2013 File Transfer Web Application Madhavi Dintakurthy Governors State University Follow this and additional works at: http://opus.govst.edu/capstones Part of the Computer Sciences Commons Recommended Citation Dintakurthy, Madhavi, "File Transfer Web Application" (2013). All Capstone Projects. 60. http://opus.govst.edu/capstones/60 For more information about the academic degree, extended learning, and certificate programs of Governors State University, go to http://www.govst.edu/Academics/Degree_Programs_and_Certifications/ Visit the Governors State Computer Science Department This Project Summary is brought to you for free and open access by the Student Capstone Projects at OPUS Open Portal to University Scholarship. It has been accepted for inclusion in All Capstone Projects by an authorized administrator of OPUS Open Portal to University Scholarship. For more information, please contact [email protected]. Page | 1 FILE TRANSFER WEB APPLICATION By Madhavi Dintakurthy PROJECT DOCUMENTATION For the Degree of Master of Science, With a Major in Computer Science Governors State University University Park, IL 60484 2013 Page | 2 Abstract Aim is to develop a web application using java web framework. Description: Develop a web application in 3 tier architecture involving user interface, controller and database. The user interface will be a web page hosted on a server. The web page consists of both static and dynamic content. All the data required for the application is stored in database tables. Controller accesses the data from the database and provides it to the user through user interface (web page). Web page: The webpage serves as user interface to the application. Web page is developed using Jsp, HTML, Java Script and Ajax. Controller: The controller serves as the communicating interface between web page and database. Controller serves the data to the user based on the user request. Controller is developed using Java 7, Java Servlets, and JDBC. Database: Database is used to store all the required data for the application. Database tables are designed according to requirement and developed using SQL. Server: Server is used to host the application. The developed web application is deployed onto server. Apache Tomcat is the application server for the application. Environment: Java 7, HTML, Java Script, JDBC, Ajax, Apache Tomcat, Derby Database, SQL. Page | 3 CONTENTS ABSTRACT 1. INTRODUCTION ………………………………………………………….. 5 2. SOFTWARE PROCESS MODEL ……………………………………….. 6 2.1 INTRODUCTION 2.2 WATERFALL MODEL 3. TECHNOLOGIES ………………………………………………………… 8 4. SOFTWARE DESCRIPTION ……………………………………………. 9 4.1 WEB PAGE 4.1.1 JSP 4.1.2 HTML 4.1.3 JAVA SCRIPT 4.1.4 AJAX 4.2 CONTROLLER 4.2.1 JAVA 4.2.2 JAVA SERVLETS 4.2.3 JDBC 4.3 DATABASE 4.3.1 SQL SERVER 4.4 SERVER 4.4.1 APCHE TOMCAT 5. SOFTWARE INTERFACE ……………………………………………… 29 6. DATABASE TABLES ……………………………………………………. 33 7. SYSTEM TESTING AND IMPLEMENTATIONS …………………… 34 Page | 4 7.1 STRATEGIC APPROACH OF SOFTWARE TESTING BIBLIOGRAPHY …………………………………………………………. 36 Page | 5 1. Introduction File Transfer Web Application is used to upload any type of files like pdf, mp3, word, video, etc.) into a database table and can download any type of files from the database. This web application is developed using java web framework. The web application is developed in 3 tier architecture involving user interface, controller and database. The user interface will be a web page hosted on a server. The web page consists of both static and dynamic content. All the data required for the application is stored in database tables. Controller accesses the data from the database and provides it to the user through user interface (web page). User Interface: The File Transfer web application contains four web pages like Home page, Upload page, download Page and About Us page. On every page there are four buttons named Home, Upload, download and AboutUs, and the user can click on any of the button to go to that particular page. The Home page and AboutUs page contains details about the project. In the Upload page, the user can upload any type of files into a database table by selecting any file from the computer using ‘choose a file’ button and once the user click on the upload button the file will be uploaded to a database table. The Download page contains all the files that are in the database table. When the user clicks on a particular file that is displayed on a Download page the file will be downloaded into the computer. In this way the user can upload and download files using File Transfer Web Application. Page | 6 2. Software Process Model 2.1 Introduction: After analyzing the requirements of the task to be performed, the next step is to analyze the problem and understand its context. The first activity in the phase is studying the existing system and other is to understand the requirements and domain of the new system. Both the activities are equally important, but the first activity serves as a basis of giving the functional specifications and then successful design of the proposed system. Understanding the properties and requirements of a new system is more difficult and requires creative thinking and understanding of existing running system is also difficult, improper understanding of present system can lead diversion from solution. The model that is basically being followed is the WATER FALL MODEL. 2.2 Waterfall Model: The waterfall Model illustrates the software development process in a linear sequential flow. This means that any phase in the development process begins only if the previous phase is complete. The waterfall approach does not define the process to go back to the previous phase to handle changes in requirement. Therefore, different projects may follow different approaches to handle such situations. What is Waterfall methodology? The waterfall approach is the earliest approach that was used for software development. Initially, most projects followed the waterfall approach because they did not focus on changing requirements. Page | 7 Waterfall Approach Phases a. Conception: Triggers when a problem is perceived. This phase involves identifying goals to be achieved after the problem is solved, estimating benefits in the new system over the current system, and identifying other areas that are affected by the solution. This phase also involves and developing the business case for the project. A business case provides the information that a manger needs to decide whether to support a proposed project, before resources are committed to its development. Page | 8 b. Initiation: Involves a macro level study of the customer requirements. This phase also involves defining alternative solutions to the customer requirements and cost-benefit justification of these alternatives. c. Analysis: Involves carrying out detailed study of the customer requirements and arriving at the exact requirements of the proposed system. The phase involves freezing the requirements before the design phase begins. d. Design: Involves translating the identified requirements into a logical structure, called design that can be implemented in a programming logic. e. Construction: Involves integrating and testing all the modules developed in the previous phase as a complete system. f. Integration and Testing: Involves integrating and testing all the modules developed in the previous phase as a complete system. g. Implementation and maintenance: Involves converting the new system design into operation. This may involve implementing the software system and training the operating staff before the software system is functional. The waterfall approach assumes that requirements are stable and frozen across the project plan. However, this is usually not true in case of large projects where requirements may evolve across the development process. Page | 9 3. TECHNOLOGIES 3.1 Software Requirements Web Technology : Eclipse IDE Web Server : Tomcat Server Database : SQL Server 2012 Code Behind : Java, J2EE, JDBC, ODBC, JavaScript, Html, Ajax, Sql 3.2 Hardware Requirements Intel Pentium : 600 MHz or above. RAM (SD/DDR) : 512MB Hard Disc : 30GB or above System bus : 32 bits RAM : 256MB of RAM Monitor : SVGA COLOR Keyboard : 108 keys Mouse : 2 button mouse Page | 10 4. Software Description 4.1 Web page: The webpage serves as user interface to the application. Web page is developed using Jsp, HTML, Java Script and Ajax. 4.1.1 JSP: Java Server Pages (JSP) is a technology that helps software developers create dynamically generated web pages based on HTML, XML, or other document types. Released in 1999 by Sun Microsystems, JSP is similar to PHP, but it uses the Java programming language. To deploy and run JavaServer Pages, a compatible web server with a servlet container, such as Apache Tomcat or Jetty, is required. Java Server Pages (JSP) is a technology that lets you mix regular, static HTML with dynamically-generated HTML. Many Web pages that are built by CGI programs are mostly static, with the dynamic part limited to a few small locations. But most CGI variations, including servlets, make you generate the entire page via your program, even though most of it is always the same. JSP lets you create the two parts separately. Here's an example: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML> <HEAD><TITLE>Welcome to Our Store</TITLE></HEAD> <BODY> <H1>Welcome to Our Store</H1> <SMALL>Welcome, <!-- User name is "New User" for first-time visitors --> <% out.println(Utils.getUserNameFromCookie(request)); %> To access your account settings, click <A HREF="Account-Settings.html">here.</A></SMALL> <P> Regular HTML for all the rest of the on-line store's Web page. </BODY></HTML> Page | 11 4.1.2 HTML: HyperText Markup Language (HTML) is the main markup language for creating web pages and other information that can be displayed in a web browser. HTML is written in the form of HTML elements consisting of tags enclosed in angle brackets (like <html>), within the web page content.
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]