> For the complete documentation index, see [llms.txt](https://docs.idew.org/project-internet-of-things/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.idew.org/project-internet-of-things/project-instructions/2-design-and-build-solution/2.6-product-website.md).

# 2.6 Product Website

{% tabs %}
{% tab title="✓ TASK" %}
Your team will create a **one-page product marketing website** for your smart device solution, which will include a [product demo video](/project-internet-of-things/project-instructions/2-design-and-build-solution/2.7-product-video.md) that your team will create. This website will be made **public** to allow more people to learn about your smart device project.

1. Gather and/or create the content (text, images, video, etc.) for your team’s product marketing website. As necessary, tailor the content to your target users, as represented by your team's persona. Be sure the content is clear, concise, engaging, and professional. Your website should include the following (but you can add other content if helpful):
   * Product Name
   * Product Description (can use value proposition as starting point)
   * Product Video (demonstrate how smart device solution works)
   * Features (list tasks that smart device solution can perform)
   * Tech Specs (list device's inputs, outputs, connectivity, etc.)
   * Photo(s) of completed smart device (if necessary, add captions to explain)
   * Screenshot(s) of completed web app (if necessary, add captions to explain)
2. Create a visual design for your team's website that will be engaging, professional, and reinforce your product concept. As necessary, tailor the design to your target users.
   * Sketch possible ideas for the overall layout of the content on the webpage.
   * Determine the final layout and its overall style (such as: colors, fonts, etc.)
3. Build the website using a tool such as [Google Sites](https://sites.google.com/create?usp=drive_web) (available within Google Drive, see guide to [Get Started with Sites](https://gsuite.google.com/learning-center/products/sites/get-started/)) – or code the website directly using HTML and CSS.
   * Include temporary placeholders for the product demo video and product images (smart device & web app) until they are ready to add to the website.

In the next phase of the project, you'll test the website with people outside your team to determine how effective the website is at explaining and marketing your team's solution.

### **❏ Deliverable**

Submit a link to your team's product marketing website for its smart device solution.
{% endtab %}

{% tab title="➤ EXAMPLE" %}
Here's a real-life example of a product webpage:  [Fitbit Charge 3 fitness tracker](https://www.fitbit.com/charge3)
{% endtab %}

{% tab title="★ RUBRIC" %}

| **✓- Below Standard** | **✓ Meets Standard** | **✓+ Exceeds Standard** |
| --------------------- | -------------------- | ----------------------- |
| Description           | Description          | Description             |
| {% endtab %}          |                      |                         |
| {% endtabs %}         |                      |                         |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.idew.org/project-internet-of-things/project-instructions/2-design-and-build-solution/2.6-product-website.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.