# Full Screen Menu #3

### Component Structure

**Primary Elements**

* **FS3 COMPONENT (Section)**: The main container that encapsulates the full-screen menu, including the logo, menu trigger, and navigation links.
* **FS3 CONTAINER (Container)**: Houses the logo and trigger elements, ensuring they're correctly aligned within the navigation bar.

**Navigation Activation**

* **FS3 LOGO WRAPPER (Div)**: Contains the website's logo, serving as a visual anchor for users.
* **FS3 TRIGGER WRAPPER (Div)**: Hosts the menu trigger icon, an interactive element that toggles the full-screen menu's visibility.

**Menu Content**

* **FS3 MENU WRAPPER (Block)**: Envelops the entire full-screen menu content, including informational blocks, social media links, and navigation items.
* **FS3 INFO WRAPPER (Div)**: A dedicated section for additional information or imagery related to the website or organization.
* **FS3 NAV WRAPPER (Div)**: Contains the structured navigation links provided within the menu.

### Animation Structure

* **FS3 - Menu Trigger**: Manages the reveal and hide animations for the full-screen menu, smoothly transitioning it into and out of view upon interaction with the menu trigger.
* **FS3 - Nav Item Hover**: Enhances the user interaction with navigation items, applying a hover effect that shifts the textual appearance for an engaging visual cue.

### Events

* **FS3 - INITIAL SET**: Prepares the full-screen menu for interaction by initially setting its visibility to hidden upon page load, ensuring a clean and uncluttered user interface.
* **FS3 - ON FOCUS - NAV ITEM & FS3 - ON BLUR - NAV ITEM**: These events are designed to improve accessibility and usability by providing clear visual feedback when navigation items gain or lose focus, respectively, via keyboard navigation. This interaction ensures all users can navigate the menu effectively.


---

# 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://bricksmotion.gitbook.io/bricksmotion-components/components/menus/full-screen-menu-3.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.