# Comments

Web designers use comments to leave a message for themselves, or other team members working on the site. It can be used as a reminder, or a note or a citation or an easter egg. &#x20;

A comment is a unique tag, it doesn't open and close - it is a self-contained tag. Don't you hate when you learn one rule and then immediately it gets changed? The reason is simple, so far we have had commands that contained instructions for the computer. But this tag says - hey computer ignore this!

```
<!--    -->
```

The comment tag says "Hey Computer, everything inside these two dashes is a comment. It is NOT computer instructions and it is NOT visible to visitor.

**Rule #41 in Room 112:** Every web page should have your name, the date and the block in a comment that appears BEFORE the title....hint at the very tip top of the page

```
<!-- Student Name, 2nd Block, 1.6.2020 -->
```

**TIP:** that is two dashes with NO spaces ...Extra tip: that is button on your keyboard next to the + sign.


---

# Agent Instructions: 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:

```
GET https://computational-thinking-in-room11.gitbook.io/room-112-dhs/html-1/my-1st-webpage/comments.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
