<aside> ❓ FAQ

• What is the deadline to submit the deliverable?
• What is a web?
• What is this cool online document provided by my awesome teacher?
• How do I submit the P.1. Production plan deliverable?
• Which file format do I use for P.1. Production plan?
• What is the hierarchical structure of the production plan?
• What tools or software can I use to create the low-fidelity wireframes?
• Is this going to be evaluated?
• Is this mandatory?
• Do I need to include the instructions provided in the yellow boxes in the deliverable?
• What tools can I use to create the visual sitemap?
• Can I use stock images or icons in my design?
• What level of detail should be included in the content section? </aside>

1. Introduction

1.1 Industry affected and identification of the problem

<aside> 📎 A paragraph or two of no more than 150 words total. Describe the industry or sector targeted by this project and the problem you identified.

Use the following questions as guidelines for writing this section. You don't need to answer them word-for-word, but they should inform your response.

1. What industry is involved?
2. What is the problem you've identified in the industry?
3. Who is currently affected by this problem?
4. What are the consequences or impacts of this problem? </aside>

1.2 The solution you came up with to solve the problem

<aside> 📎 A paragraph or two of no more than 150 words total. Elaborate on the proposed solution to the identified problem.

Use the following questions as guidelines for writing this section. You don't need to answer them word-for-word, but they should inform your response.

1. What would be the ideal solution to solve the problem?
2. What previous attempts have been made to solve this problem? How successful were these attempts?
3. Are there potential challenges or obstacles in implementing our solution, and how do we plan to overcome these? </aside>

1.3 Website proposal project and how it contributes to the solution

<aside> 📎 A paragraph or two of no more than 150 words total. Include the name of the project. Be honest with yourself and your project. Your web project may not completely solve the problem you've identified, but it can contribute to a solution to some extent.

Use the following questions as guidelines for writing this section. You don't need to answer them word-for-word, but they should inform your response.

1. To what extent does your web project contribute to achieving the solution?
2. How will our project directly benefit those affected by the problem?
3. Which aspect of the problem is our project aiming to address?
4. What part of the problem our project is aiming to solve with the project?
5. Why is our project necessary or relevant in the context of this problem? </aside>

1.4 Purpose of the web

<aside> 📎 A paragraph or two of no more than 100 words total. List the specific goals that the project aims to achieve.

</aside>

1.5 Target audience (user persona)

<aside> 📎 A paragraph or two of no more than 100 words total. Describe the intended audience for your website as accurately as possible. The more detailed your description, the better. You could even create a user persona to illustrate your audience.

</aside>

2. Content

<aside> 📎 No word limit. In this section, you should thoroughly detail all content planned for your website. You may structure this section by pages. This includes all text, links, and any other elements that will appear on the site. The information should be organized to reflect its eventual placement on the website. It's beneficial to structure this within a text document for easy reference. By doing so, you're creating a complete blueprint of your website's content, ensuring that all necessary components are considered before the design and development stages.

</aside>

3. Design and visual elements

3.1 Visual Sitemap structure

<aside> 📎 In this section you need to include an extensive sitemap. It should capture the total number of pages and clearly outline the page hierarchy.

Group size determines the minimum page requirements:

• For individual projects, the minimum requirement includes a homepage, a contact page, and at least one additional page.
• For groups of two, the minimum requirement extends to a homepage, a contact page, and at least two additional pages.
• For groups of three, the minimum requirements extend to a homepage, a contact page, and at least three additional pages.

A sitemap is a tool that represents the structure of a website, outlining its pages and their hierarchical relations. It helps designers and developers to visualize the site's layout. In essence, sitemaps serve as the blueprint of a website, facilitating its planning and development.

Example of a visual sitemap from a simple web project. Source: vennage.

</aside>

3.2 List of elements to be created

<aside> 📎 Before developing your website, compile a list of all visual elements that can't be created using HTML, CSS, or JS. This list is meant to guide the development of these elements. Note that for this deliverable, you only need to provide the list, not the actual elements. Please submit only the list.

When creating your list, consider the following: (1) you need a unique representation of your brand identity; (2) determine the primary and secondary colors to dictate the website's look and feel, which is your color scheme; (3) choose the typography or fonts to be used across the website; (4) Collect images, videos, or graphics to enhance visual appeal, which comprises your imagery (5) design or select icons for site navigation or to represent various site features.

Remember, you can use open resources from various sources. If you want to create your own resources, that's fine, but you also have the option to use open resources. Keep in mind, you'll need to choose the Creative Commons [link to Creative Commons] license appropriate for the content included in your website.

</aside>

3.3 Website wireframe