SWIN BUR · NE * Swinburne University of Technology School of Science, Computing and Engineering Technologies SWINBURNE UNIVERSITY OF TECHNOLOGY COS10026 Computing Technology Inquiry Project Assignment Part 1, Semester 2, 2022 Develop a Simple Static Web Site Due Date 10 pm on Monday in Week 7 (Late submission penalty: 10% of total available marks per calendar day) Contribution to Final Assessment: 40% Important: All work must be done by your group. Submissions are automatically checked for similarities. Unexplained/acknowledge similarities may constitute plagiarism. Carefully read the section on plagiarism in the Unit Outline before you proceed (including the section forbidding sharing your work with others). Purpose This group assignment will familiarise you with the techniques and skills involved in designing and creating static webpages utilising validated HTML and CSS created with a standard text editor. You will deploy these Web pages on a Unix / Apache server. This should be done in a way that keeps HTML content and CSS presentation separate, as discussed in the lectures. No JavaScript to be used in this part of the assignment. Essential Requirements The Web site you will develop will describe a product/service for sale or hire. Each group will be allocated a different type of product or service by their tutor. It is up to you to provide details of the particular product or service and its features. Your Web site will have the following web pages linked by a common menu: · An introductory / home page (index.html) · A product description page (product.html) · A product enquiry page (enquire.html) · A page about your assignment (about.html) You must call these files exactly by these names, otherwise the marking program will not know they exist! . A page that lists any enhancements you have made (enhancements.html) You will also include . A CSS file that styles your website (style.css). In general the web pages must: · have relevant content · include the HTML markup specified in the marking guide · validate to HTML5 without errors · have a <head> with Title, Meta tags as specified in template (including author)
· be styled by a validated CSS3 file · be linked to each other via a menu · be deployed on Mercury. All web pages in your website should have a consistent layout and navigation. Where "in-house" templates have been defined in this unit (e.g. for meta-data; tables; etc.) these should be followed. These include accessibility alternatives. The HTML in your Web pages must validate against the W3C HTML5 validator (http://validator.w3.org/nu) . Pages should not contain any deprecated elements/attributes (e.g. < i> , <b>). Do not use iframe elements in your assignment. Note: Generic structural elements like div or span should only be used where there is no more meaningful HTML5 element (e.g. section) that is appropriate. 1. Introductory home page (index.html) This page should contain appropriate header and graphic related to your allocated product, and should contain a menu that links to the other pages on your Web site. This common menu