> For the complete documentation index, see [llms.txt](https://features.scnd.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://features.scnd.com/v2.0/front-office/front-interface-structure.md). # Front interface structure Understanding how to use the different Front interface components Path: Front * [Definition](#id-1.16.x-frontinterfacestructure-definition) * [Create an interface structure](#id-1.16.x-frontinterfacestructure-createaninterfacestructure) * [Read an interface structure](#id-1.16.x-frontinterfacestructure-readaninterfacestructure) * [Navigation bar](#id-1.16.x-frontinterfacestructure-navigationbar) * [The platform logo](#id-1.16.x-frontinterfacestructure-theplatformlogo) * [The login/register button or the user avatar](#id-1.16.x-frontinterfacestructure-thelogin-registerbuttonortheuseravatar) * [The hamburger menu](#id-1.16.x-frontinterfacestructure-thehamburgermenu) * [Footer](#id-1.16.x-frontinterfacestructure-footer) * [Update an interface structure](#id-1.16.x-frontinterfacestructure-updateaninterfacestructure) * [Header](#id-1.16.x-frontinterfacestructure-header) * [Footer](#id-1.16.x-frontinterfacestructure-footer.1) * [Delete an interface structure](#id-1.16.x-frontinterfacestructure-deleteaninterfacestructure) * [Header](#id-1.16.x-frontinterfacestructure-header) * [Footer](#id-1.16.x-frontinterfacestructure-footer.1) * [Related resources](#id-1.16.x-frontinterfacestructure-relatedresources) ## Definition Numerous interface elements are reused across the platform, ensuring cohesion of the user experience. WHO CAN USE THIS FEATURE? All users ## Create an interface structure New elements cannot be created from the platform’s Front interface. *** ## Read an interface structure ### Navigation bar The navigation bar (navbar) is consistently located at the top of each page. It enables users to personalize their platform experience according to their specific goals. Depending on the selected preferences, the homepage adjusts to function either as a solution tailored for **customers** seeking services and service providers proposing their offerings (Figure 1) , or **vendors** searching for service and services proposals (Figure 2) .

{% hint style="info" %} When the configuration switch mode is not enabled by the operator, users are restricted to operating within the marketplace solely as either a customer or a vendor. This designation is determined at the time of registration. {% endhint %} The navbar is made up of: #### The platform logo The platform’s logo (figure 2) is visible to all users.\ Clicking the logo will redirect the user to the following page: [Homepage](/v2.0/front-office/homepage.md)

#### The login/register button or the user avatar **Login/register button** The login/register buttons (figure 3.1) are displayed when a user is not logged in to the platform. Once the user is logged in, the user’s avatar will be displayed instead. Clicking one of the two buttons will open a modal to log in or register. This process is described in the following documentation: [Log in & Register](/v2.0/front-office/log-in-and-register.md)

**The user avatar** The user’s avatar (figure 3.2), allows navigating through the dashboard menu quickly upon clicking it.

**Platform mode** The platform's mode can be adjusted to align closely with user preferences within the marketplace. By selecting the "Become a customer"(Figure 4) button, the system automatically configures essential elements such as listing services and a customizable search bar tailored to the user's needs. Additionally, users have the option to post requests for proposals, enabling them to advertise services they seek or negotiate for the best possible deals.

On the opposite side is the "Become a Vendor" button (figure 4.1), designed to set up the marketplace with tools that help users manage their business activities within the platform. This feature enables vendors to create service listings and utilize additional resources for promoting and executing their services effectively across the marketplace.

#### The hamburger menu The hamburger menu (figure 5.1) displays the content pages set by the administrator. The hamburger menu opens with a single click (figure 5.2 ).

### Footer The footer displays institutional pages to users (figure 6). These pages are usually for information purposes.

2 dropdown buttons (figure 6.1) are available on the left side of the footer: * Language selection, allows the user to select the platform language * Currency selection, enable the user to choose the display currency. {% hint style="info" %} The display currency only changes the displayed prices. Payments are still made in the default platform currency set by the platform administrator. {% endhint %}

Setting up the footer pages (figures 6.2 and 6.3) is described in the following documentation: [Content page.](/v2.0/front-office/content-page.md)

## Update an interface structure ### Header Only the super-administrator can update the header content pages (figure 5.2). Instructions are provided here: [Header menus](/v2.0/superadmin/contents/header-menus.md) ### Footer Only the super-administrator can update the footer content pages (figure 6.3). Instructions are provided here: [Footer menus](/v2.0/superadmin/contents/footer-menus.md) ## Delete an interface structure ### Header Only the super-administrator can delete the header content pages (figure 5.2). Instructions are provided here: [Header menus](/v2.0/superadmin/contents/header-menus.md) ### Footer Only the super-administrator can delete the footer content pages (figure 6.3). Instructions are provided here: [Footer menus](/v2.0/superadmin/contents/footer-menus.md) ## Related resources **SBO :** * [Header menus](/v2.0/superadmin/contents/header-menus.md) * [Footer menus](/v2.0/superadmin/contents/footer-menus.md) **Front :** * [Homepage](/v2.0/front-office/homepage.md) * [Log in & Register](/v2.0/front-office/log-in-and-register.md) * [Listing deposit pages](/v2.0/front-office/rendering-types.md) --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://features.scnd.com/v2.0/front-office/front-interface-structure.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.