Landing : Athabascau University

Group members: this is the place for your learning diary. Use this to post your zipped-up site at least once each unit, and your reflections as often as you wish (at least once per unit). Please write your reflections directly in the post, not as attached files. Where you do need to attach documents, such as for unit 1 designs, use PDF, PNG or JPG formats. You can attach files using the 'Embed content' link in the editor.

QUICK COURSE LINKS:  Add blog post - Read latest group postsFAQs: Course process : Site design : HTML : CSS : JavaScript : JQuery : AJAX : MiscPodcasts for each unit

Updated resource pages:  Unit 1 - Unit 2  - Unit 3Units 4 & 5 - Unit 6 - Unit 7

Unit 2 Learning Diary

  • Public
By Justin Jaunzemis in the group COMP 266 August 31, 2015 - 10:46pm

For unit 2, I learned how to code in HTML, which makes up the backbone of any website. For this unit, cleaned up two sample webpages that were coded poorly, and I created the structure for my website. While not the final version, I created my website according to the mockups and site map I created in unit 1, but for brevity purposes, I omitted the submenus from the Facts and History and Aircraft Information subpages, until the final site is completed for the Portfolio, as well as the image grids where CSS is necessary to implement, and a full review of an FSX addon to being a minimal filler to explain the format of each review. While far from what I hope to accommodate to a couple of my personas like Billy and Joe who require visual aid, I plan to address that in the next unit when I get to CSS.

For the two documents, I noticed the first page had issues like a paragraph nested within an h2 tag, which made the paragraph print out in the bold h2 font. I also saw the same within the first h3 tag. Under W3C standards, no paragraph may be nested within a header tag. The picture in the HTML lacked the necessary alt information for those users who can’t see the image, but need a description of what it is. For the most part, all of the information including paragraphs, list and tables are all nested within header tags, which is what is wrong with the first sample page.

I feel that my site addresses the needs of only some of my personas at this current stage. While I can accommodate for some of my content-centric personas like Martin, Joe, Jay, and Dell, I need to utilize CSS before I can address the other two personas with Billy and Donald as they require more visual navigation besides a structured text website with Billy being a child who isn’t engaged by text alone, and Donald being a senior requiring an easy to use visual interface for my website. For each persona I can accommodate for:

Martin’s needs lie in general content, which come in the form of what I can implement until the next unit. In the form of facts, history and aircraft information regarding general content. The next unit is where I can provide images of aviation to share.

                Dell’s needs lie in technical information, which I fully implemented with Aircraft Information.

Joe’s needs lie in learning more about Aviation, which I implemented in the introduction and facts and history subpages, and as his interest grows, the general content that Martin is looking for.

For Jay, while the general content is what he also looks at, I met his needs in the form of an aircraft review for FSX. For FSX Screenshots, I will also have to wait till I can implement that in Unit 3.

I feel that I have exceptionally met the requirements for tags under the problem section for unit 2.

-I used an image I got off of WIkipedia to show off an Aircraft for Aircraft Information, as well as providing a photo of myself while I was on vacation in Denmark, and a placeholder image for a potential logo.

-I used hyperlinks to send my users to the original source of things like aircraft information, and facts, and each historical event in Aviation, from the Wright Brothers, to the Boeing 787.

-For my introduction subpage, I highlighted the four forces that acted on an aircraft using a list. A definition list was used to define each of the four forces, and two types of drag for the force of drag. I also used unordered lists in my FSX Review template for highlighting pros and cons

-For div tags, I used them to create a top menu bar for my website that is visible on all subpages. It is currently text at the moment, but with the knowledge of CSS, I can turn the text links into image links using sized icons.

For a span tag, I used one to highlight the four forces that act on an aircraft in the introduction. I plan to make each word a different bolded color to highlight and differentiate each of the four forces to visually explain the concept better.

-For tables, I plan to use tables for my aircraft information section on the technical specs of each aircraft. I have also used one on my about me subpage listing my name, phone numbers and email address for contact info.

-Other tags I included include a footer tag for my name, and last modified dates, and a header tag for my top menu for all my subpages. 

I created a form as well on my about me page to allow any user to send me comments, questions or concerns through Email, where I can address anything users send me.


Overall, I feel that my pages communicate very well. Each page has its specific purpose and content. Each page is also structured well for each purpose, with the exception for the images subpage, which I can address Unit 3, where CSS can allow me to arrange and resize images into thumbnail links where users can view and download my images. Then my page can fully meet the basic needs of my personas. 


These comments are moderated. Your comment will not be visible unless accepted by the content owner.

Only simple HTML formatting is allowed and any hyperlinks will be stripped away. If you need to include a URL then please simply type it so that users can copy and paste it if needed.