Contribution to Final Assessment: 20% This is an Individual Assignment. All work must be your own. Submissions are automatically checked for similarities. Unexplained 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 individual 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 is to be used in this part of the assignment we will use JS in Part 2. Essential Requirements Scenario: An IT company wants to develop a website that will enable it to advertise vacant positions. These have a position description that sets out the qualifications, skills and knowledge required. Potential applicants for the position will be able to submit an online form to apply for a position. In this assignment you will develop a prototype of this website. The website you develop will consist of the following Web pages, accessible from a common menu on each page:

• Home page with details of the company (index.html)

A page of job descriptions (jobs.html)

• A job application page (apply.html)
• A page with your personal details (about.html)
• A page which lists any enhancements

you have made (enhancements.html) You will also include

• A CSS file that styles your website (style.css).

The essential requirements for this assignment are listed in the marking guide. In general the web pages must:

• have relevant content
• must include the HTML markup specified in the marking guide
• must validate to HTML5 without errors
• must be styled by a validated CSS3 file
• must be linked to each other via a menu
• must 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. , ). 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.

2. Home page (index.html)

This page should contain appropriate title, a description and graphic related to the company. It is up to you to make up the details of the company that is advertising the jobs. It should contain a menu that links to the other pages on your Web site. This same menu should be in every page of your website with an email link to your student email.

2. Position Descriptions page (jobs.html)

You need to write a web page with at least 2 position descriptions. For one of these your tutor will allocate you a job title from the IT industry. For the second position, the choice of IT job type is entirely up to you. Why not write a position for the ideal job you would like to do? Be as imaginative as you like. The HTML on this page must contain:

• Hierarchically structured headings of at least 2 levels
• More than one

• An with appropriate content
• At least one ordered list
• At least one unordered list
• The page should also have an appropriate footer.

Your job descriptions should be concise but as a minimum include :

• Companys position description reference number (5 alphanumeric characters)

• Position title
• Brief description of the position

• Salary range
• The title of the position to whom the successful applicant will report

• Key responsibilities. A list of the specific tasks that are to be performed

• Required qualifications, skills, knowledge and attributes. These should be divided into essential and preferable. These requirements should include such things as programming languages required, number-of-years of experience required, etc..

The content of the job description should be appropriately structured with headings, sections, subsections, lists etc. using the appropriate HTML elements.

Sources / References:

• You can use material from other websites but the source of all material must be acknowledged. This acknowledgement should be immediately after the material and include a hyperlinked URL to the original source. The text of the hyperlink reference can be a short name but the hyperlink must work.
• If you are unsure of what is contained in a position description there are many resources on the web. Here is one: http://recruitloop.com/blog/how-to-write-ajob-description/

3. Job application page (apply.html) This page has a form that allows a potential candidate to register their interest in the advertised position. HTML5 data validation should be used to check the users input. The form will allow a potential applicant to fill in the following:

Field	Format requirement
Job reference number	exactly 5 alphanumeric characters
First name	max 20 alpha characters
Last name	max 20 alpha characters
Date of birth	dd/mm/yyyy
Gender	radio inputs grouped using a fieldset and legend
Street Address	max 40 characters
Suburb/town	max 40 characters
State	drop down selection from VIC,NSW,QLD,NT,WA,SA,TAS,ACT
Postcode	exactly 4 digits
Email address	validate format
Phone number	8 to 12 digits, or spaces
Skill list - the last item in list should read Other skills...	checkbox inputs
Other skills	textarea

All inputs should have labels. All form values, except the comment textarea are required or have a default value (e.g. select and checkbox inputs). The user should not be able to submit the form if any of these required fields are blank. Data Submission to Server The form should have a submit button labelled Apply. When this button is clicked the name-values from the associated form should be sent to the server using the post http method. The server action address is https://mercury.swin.edu.au/it000000/formtest.php. The server will then just echo back the name value pairs to the client. While nothing will be stored on the server in this part of the assignment (we will do this in Part 3) this will allow the form submission to be tested. 4. A page about you (about.html) This page will contain information on the following:

Information	HTML element to be used
Your name	Definition list
Student number	Definition list
Your tutors name	Definition list
Course you are doing	Definition list
Photo of you	HTML figure element
Your Swinburne timetable	HTML table
A mailto link to your student email.

It could also include personal profile, such as resume, interests, or information that is related to you. This extra information gives you an opportunity to extend the techniques you apply in your assignment, and could include:

• Demographic information about you
• Description of hometown
• A list of your favourite books, music, films etc.

5. CSS Requirements No style markup should be included in your HTML file. The pages in your website must be styled with CSS and have a consistent look and feel, particularly common elements such as menus, headers and footers. While the emphasis is this assignment is on the appropriate application of techniques rather than graphic design, your pages should follow basic usability / accessibility principles, e.g. distinguishable foreground and background colours, and font readability, etc. Create your own design and implement it using one single external stylesheet that applies to all your Web pages. This file should be named style.css and placed in a styles folder on the server. The stylesheet should style the common elements on all your web pages, and address the following specific style requirements.

2. Comments: The CSS should include comments at the beginning of the CSS file to identify author and purpose. Individual line comments should be used as necessary to explain particular styles and explain where they are applied.
4. Selectors: All the following CSS Selectors should be used appropriately at some point in this assignment:

• element, #id, .class, grouping, contextual
• pseudo class, pseudo element

2. Menu: The menu should have its own set of styles applied. Use a background colour.
4. Index Page: Demonstrated the following specific CSS rules on the index.html page:

• display a background graphic.

5. Position Descriptions Page: Demonstrated the following specific CSS rules on the jobs.html page:

• elements should have their font variant, size and family etc. set using the short-hand font property.
• The should be 25% of the width of page and float to the right.
• The should have a coloured border with an appropriate margin and padding.
• The footer should cover the full width of the page the footer text should be in a small font and centred in the footer..

6. About Page: Demonstrated the following specific CSS rules on the about.html page: Style the definition list so that each

is on the left and the

on the right in a single line. Set the dt to have a common width.

• The photo should be styled with a single border using the short-hand border- property, and the figure should be floated to the right of the definition list
• should be centred within the section, headings in bold, table cells with a background colour specified in hexadecimal format
• The email should be style similarly to the definition list.

7. All pages: should have a fluid layout (the page should Reflow on page resize). Other CSS selectors and properties can be used as necessary and appropriate for the presentation Do not include any proprietary CSS mark-up, such as moz- or webkit etc. Hint: CSS validators will validate against a particular version of CSS e.g. CSS2.1 or 3. This assignment should be valid CSS2.1 or CSS3. Make sure that you are checking your CSS using the correct version of the validator. For example, if you include CSS3 markup and validate as CSS2.1 it will show errors. (Best to pre-set the version in the Web Developer tools see the note on Blackboard). Enhancements Note: Make sure you get all the basics working first before you attempt any enhancements. See the marking Guide below. The technologies for developing Web applications are rapidly changing. One of the key skills you will need is finding out about these new techniques and applying them. When researching, look at the reliable websites such as the External Links provided on Blackboard. This assessment gives you an opportunity to demonstrate your ability to implement features/techniques that go beyond the specified requirements above. It also provides you with an opportunity to demonstrate your ability to discover techniques from a range of sources and apply them in a standards compliant manner. These enhancements need to be implemented within the required web pages (index.html, product.html, enquire.html, about.html). The extra feature needs to enhance your web site in a meaningful and relevant way. List and describe each enhancement implemented on the separate enhancements.html page, and describe how you have significantly extended the basic HTML and CSS beyond the lecture and tutorials. Hyperlink from this list to where the feature is implemented in your Web site. If it is a CSS feature, hyperlink to an example of the html that is selected by the CSS rule. For each enhancement feature briefly explain: I1 how it goes beyond the basic requirements of the assignment I1 what code is needed to implement the feature I1 the references to any third party sources for the technique, (e.g. URL) must be cited. I1 a hyperlink to where you have applied that extension in your Web site (this is needed so the tutor can quickly assess your enhancements during the demonstration). I1 All enhancements must be able to run on Firefox. Make sure you check this. A maximum of 2 enhancements will be assessed (up to 10 marks each). Examples of HTML/CSS enhancements you might make that will contribute a high distinction mark include:

• Effective, appropriate and innovative use of a number of distinct HTML elements not covered in tutorials (e.g. Image maps, Canvas, etc) used in a way that improves the user experience of the website.
• A number of additional CSS properties or selectors (e.g. support for interactivity, animation) not covered in the tutorials. For example the use of a range CSS3 pseudo-elements and classes, child or siblings combinators, attribute selectors, etc. (e.g. use the CSS3 :target selector to help us see where you have applied your enhancements.)
• Implement Responsive Design with additional CSS that presents your website specifically for mobile phone / tablet sized displays.

Discuss your proposed enhancements with you tutor before you implement them. The number of marks you receive for an enhancement will be at the sole discretion of your tutor/marker. As a guide if the enhancement has only taken a couple of lines of code it is likely to be trivial.

• Be relevant to / enhance the content of the website
• Be well described (as explained above)
• Be non-trivial.
• Be significantly different from other features you have implemented.

Note: Do not include JavaScript in this part of the assignment. This will be covered in Part 2. Web Site Folder Structure and Deployment The directory structure of your website is described below. You can create additional HTML files for your content (depending on what your content requires), but the following is needed:

assign1/ You must have this folder case sensitive! index.html jobs.html apply.html about.html enhancements.html ...other html pages images/ Folder for images for your page content styles/ Folder for style.css other css files styles/images/ Folder for images referred to by your css files e.g. background

Notes:

• HTML files should only be in the base assign1/ folder not anywhere else.
• All images used for the content should be stored in the assign1/images/ folder.
• All images used for the style should be stored in the assign1/styles/images/ folder.
• There should be a style.css file in the assign1/styles/ folder.
• All links to your files (CSS or images) should be relative. Do not use absolute links, as these links will be broken when files are transferred for marking. No marks will be allocated if links are broken.

Note: DO NOT INCLUDE VIDEO OR OTHER LARGE (>5MB) MEDIA FILES IN YOUR ESP SUBMISSION. Make sure you thoroughly test your website deployment on the mercury server. Assignment Submission (Canvas + Mercury) Your assignment should be uploaded to Mercury on or before your deadline. An electronic copy of your assignment should be submitted through Canvas on or before your deadline.

• Make sure all your files are in the correct folders and compress your root folder with all your sub-folders with HTML, CSS, and images into a zip file named assign1.zip. Submit this to Canvas. When the zip file is decompressed, the entire website should be able to be run from index.html without needing to move any files.
• You can submit more than once through Canvas. Your last submission will be marked.
• Note that all deliverables must be submitted electronically. There is no need to submit an assignment cover sheet.

Make sure you complete your Canvas submission process.

Mark Sheet Marker ............ Declaration: I hereby confirm that the assignment to be demonstrated is identical to that submitted to Student number ....................... Student name ....................................................... Signature ................................ Date .................. Tutorial Day/Time .....................

Essential Requirements Tick box 0 if requirement met	Y/N
index.html validated HTML5 LI with all meta tags, title, author LI nav menu that links LI logo/graphic LI
jobs.html validated HTML5 LI nav menu LI appropriate levels of headings LI meaningful content LI > ~150 words LI image LI list LI LI
apply.html validated HTML5 LI nav menu [ form (at least different four form controls) [ specified data echoed back from server LI some HTML5 data checking LI
about.html validated HTML5 LI nav menu LI dl list LI timetable LI photo LI email link LI
style.css validated external CSS LI single file CSS applied to all HTML pages LI consistent typological style applied to all pages LI some CSS layout applied LI Selectors used: element LI,#id LI,.class LI
Deployed to Mercury LI
Subtotal (all Y)

Specified Requirements Place 0 or lI in box - 2 marks each tick	Comment	Mark
index.html HTML (deduct 2 marks up to -10 for each HTML5 validation error) Menu that links (consistent menu on all pages) LI Header with appropriate context including title LI Footer LI CSS: Background graphic LI Menu appropriately formatted with background colour LI		/10
jobs.html HTML (deduct 2 marks up to -20 for each HTML5 validation error) Headings (at least contiguous 2 levels) LI Ordered list El, Unordered list El, 2+ Sections El, Aside LI CSS: Aside 25% viewport width El, floats right El, coloured border LI font variant, size family set LI Footer full page width LI		/20
apply.html (deduct 2 marks up to -26 for each HTML5 validation error) One mark only if input has no html check Text input with HTML format checking for: job ref no (=5 char) El, names (phone number (8 to 12 digits) LI Appropriate input for date LI Radio buttons for gender with fieldset LI Dropdown box for stateLl Skills check boxes LI Text area LI Labels linked with \'for\' (test by \'clicking\' on label) LI Data for all inputs returned from server correctly LI		/26
about.html (deduct 2 marks up to -16 for each HTML5 validation error) definitions lists LI lists single line common width LI photo in figure LI border as specified LI float right LI timetable LI timetable format as specified LI email link works LI		/16
CSS (general) (deduct 1 markup to -20 for each CSS3 validation error) Appropriate use of selectors: grouping El, context El, pseudo LI Fluid page flow (relative dimensions) LI		/8
Subtotal		/80

Enhancements to Specified Requirements listed and linked from enhancements.html Maximum of 2 Enhancements will be assessed (put your best ones at the top of the list). Up to 10 marks are available per feature. Poorly implemented or trivial enhancements may receive less or zero marks.

Feature Name	Described	Linked to where implemented on your Web site	Source (if applicable)	Mark
	Y/N	Y/N	Y/N/na	/10
	Y/N	Y/N	Y/N/na	/10
Total Additions				/20

Other Deductions based on demonstration, documentation, code and file inspection

Requirement	Max Deduction if not met	Deduct
Page design
- Well designed structure	-4
- Appropriate contrast in colours	-2
- Appropriate use of fonts	-2
- Consist application of style across pages	-2
- Appropriate application of styles	-2
Content
- Job descriptions have sufficient quantity (200 words +)	-4
- Job descriptions is sufficient quality	-4
- About.html content meets spec	-4
- Images (including portrait) present and appropriate file size	-4
HTML
- Meta-data follows in-house standard	-3
- HTML has no embedded Style markup CSS is fully separated from HTML	-4
- No deprecated elements/attributes used	-3
- No inappropriate use of HTML semantics (e.g. use of when should be used)	-4
- HTML follow usability standards (e.g. alt on images)	-3
- Comments adequate	-3
CSS
- No redundant CSS or unused selectors	-3
- Appropriate header comments (match in-house standard)	-3
- Appropriate use of selectors (e.g. Class versus ID)	-3
- Appropriate line comments	-3
Web site
- All third party content acknowledged properly*	4
- Directory Structure as defined above	-4
Total Deductions

* Note: Failure to acknowledge third party code or content at all is plagiarism and may result in zero marks for this assessment or other penalties in accord with Swinburne policy. A final assignment mark will not be provided during the demonstration. All code is inspected after the demonstration by your tutor before a final mark is allocated. Comments: ...................................................................................................