Studio Help Glossary

Architecture

A structural view of Studio CMS: areas, modules, relationships between content, navigation and management components.

Use: helps you understand how the product is organized before you start editing.

Interface

The visual layer of the backoffice where users move between modules, lists, editing forms and operational actions.

Use: it is the visual translation of the product logic.

Backoffice

The Studio CMS administration panel where pages, blocks, forms, SEO, menus and integrations are managed.

Use: it is the operational center of the project.

Login

The process of entering the backoffice through the site URL followed by /admin/login.

Use: it is the entry point for day-to-day management.

Credentials

The set of access data, usually username and password, required to authenticate in Studio.

Use: without valid credentials there is no access to the backoffice.

Workspace / Dashboard

The Studio start dashboard that brings together quick access, history, indicators, recent pages and operational shortcuts.

Use: it works as the starting point for website management.

Quick access

Direct navigation entries to areas frequently used inside the Workspace.

Use: they reduce clicks and speed up repetitive tasks.

Favorites

A set of pages or content marked for faster access and editing inside the backoffice.

Use: helps teams return quickly to their most critical content.

Feature Bar

An action bar accessible from the frontend to open technical information, identify blocks and jump into editing.

Use: it shortens the distance between seeing and fixing.

Favorite Page

A Feature Bar action that marks the current page as a favorite for faster access later on.

Use: it speeds up the return to critical or frequently used pages.

Edit Page

A Feature Bar action that opens the editing view of the current page directly in the backoffice.

Use: it reduces the time between identifying an issue on the frontend and fixing it.

Navigation Section

A side structure that organizes groups, subpages and expanded states in the documentation and other support areas.

Use: it preserves context when there are many related pages.

Frontend / Frontpage

The public view of the website, used to validate how the content configured in Studio actually reaches the end user.

Use: it is the side where the real experience is confirmed.

Content management

The Studio layer that centralizes text, images, videos, documents, forms and other digital assets of the project.

Use: it is the point where raw content becomes working material.

Integrations

The set of technical connections between Studio and external services such as analytics, email, tracking or third-party platforms.

Use: they expand the CMS beyond pure content editing.

Digital experience

The final result of the combination between content, structure, navigation, performance and accessibility on the published website.

Use: it is the final goal that the Studio architecture supports.

Users

The backoffice area dedicated to managing access, profiles and permissions for the people who use Studio.

Use: it controls who can enter and what they can do.

Advanced settings

A family of Studio technical settings used to adjust structural, visual or operational behavior in pages, blocks and forms.

Use: they should be treated as a fine-control layer, not as automatic fill-in.

Log out / Sign out

An action that closes the active session in Studio CMS safely.

Use: it is important on shared devices or temporary access points.

Page

A unit of content published on the website, usually made up of several blocks arranged in a specific structure.

Use: it is the final piece the user visits on the frontend.

Content hierarchy

The logical order in which headings, text, media, CTAs and components are distributed across a page.

Use: it affects clarity, readability and editorial performance.

Layout

The visual and structural composition of a page or block, including width, columns, rhythm and alignment.

Use: it connects editorial intent to visual presentation.

Block

A reusable modular component that represents a piece of content, media, navigation or functionality within the page.

Use: in Studio, the page is built with blocks, not with a continuous editor.

Skin

A visual variant of a block, used to change look, composition or emphasis without changing the base function.

Use: it allows flexibility while keeping consistency.

Disabled block

An option that hides a block without deleting it, useful for testing, seasonality or temporary review.

Use: it is the first thing to check when a block “disappears.”

Full Width

A setting that makes the block occupy the full available width within the layout.

Use: it changes visual impact and responsive behavior.

Margin / Padding

Control of the block's outer and inner spacing, essential for rhythm, breathing room and the relationship between sections.

Use: it fixes density and visual consistency without changing the content.

Background color / Text color

Background and text color settings used to reinforce contrast, hierarchy and readability.

Use: they help balance branding and accessibility.

Animation / Scroll animation type

Parameters that control additional visual behavior for blocks when they come into view or appear during scroll.

Use: they should be used carefully so they do not compromise readability.

Block ID / Extra Class

Technical identifiers for anchors, tracking, CSS customizations and block-specific integrations.

Use: they connect content, styling and implementation.

CTA

Call to Action: a button or link designed to lead the user to the next relevant action.

Use: it turns reading into progression.

Quick actions

A set of operations accessible directly from the structural list, without the need to enter deep editing.

Use: they speed up daily management and small maintenance tasks.

Copy

A structural action that lets you copy the selected page or item within the navigation.

Use: it is useful when you need to reuse a structural base or similar content.

Add new language

An option that creates the page in a new language, usually without a previous structure attached.

Use: it is the starting point for multilingual expansion.

Replicate language

An action that copies the structure and content from one language version to another inside the Navigation Section.

Use: it reduces rework when the structural base should stay the same.

Duplicate

An operation that creates a copy of the page with its structure, useful for new variants or similar content.

Use: it speeds up creation without starting from zero.

Delete

An action that permanently removes a page or item from the project structure.

Use: it should be used carefully because it affects navigation, content and possible public URLs.

Assign role

A structural option used to assign permissions or special roles to backoffice users in specific contexts.

Use: it helps control responsibility and access by profile.

Common advanced settings

A set of options shared by many blocks, such as Skin, Disabled block, Full Width, Block ID / Extra Class, Margin / Padding and animations.

Use: they fine-tune visuals, behavior and implementation without changing the block's function.

Search field

An internal navigation search that helps locate pages and structural items by keyword.

Use: it makes management much faster on large sites.

Records display

An interface control that defines how many items are shown per page in a structural list.

Use: it helps balance overall visibility and operational focus.

Category page

A page created to group related content within a navigation logic or thematic archive.

Use: it organizes ecosystems with multiple pieces of the same content type.

Post

A content item created within the project structure, usually associated with sections that are frequently updated.

Use: it is useful for editorial areas, news or dynamic knowledge bases.

2 Columns Tabs Block

A component that organizes content into tabs with two columns, useful for comparison and contextual navigation.

Use: it works well when there is a lot of related but segmented information.

Title Block

A block dedicated to headings, usually used to open sections and reinforce editorial hierarchy.

Use: it helps keep the page readable and well structured.

Text Block

A block for simple text content such as paragraphs, lists, notes and short reading structures.

Use: it is the basis for most editorial content.

Slideshow Block

A visual sequence block used to present several images or highlighted items in rotation.

Use: it is suitable when there is a visual narrative or a collection of highlights.

Image Block

A block designed to highlight a single image with presentation control inside the page structure.

Use: it is meant to focus attention on a specific asset.

Image Text Block

A component that combines image and copy in the same composition, widely used in storytelling and explanatory sections.

Use: it creates a better balance between reading and visual support.

Gallery Block

A block for showing multiple images in an organized way, usually in a grid or coherent visual set.

Use: it is ideal for portfolios, showcases and visual references.

Mosaic Block

A mosaic-style composition component, useful for distributing several content pieces with a more graphic rhythm.

Use: it creates visual diversity without losing structure.

Video Block

A block that embeds a standalone video for direct playback within the page.

Use: it focuses attention on audiovisual content.

Video Text Block

A composed version that combines video and supporting text, giving multimedia content better context.

Use: it is useful when the video needs editorial framing.

Accordion Block

An expandable-topic component, often used for FAQs, staged explanations and long content broken into parts.

Use: it reduces visual density without losing information.

Timeline Block

A block designed for timelines, processes, milestones or stories presented in chronological order.

Use: it helps tell the story of evolution, steps or journeys.

Testimonials Block

A component for showing testimonials, feedback or social proof in editorial form.

Use: it reinforces trust and outside validation.

Cards List

A block that presents groups of items in card format, with quick and modular reading.

Use: it works well for hubs, collections and thematic navigation.

List Block

A component designed to present structured content lists.

Use: it simplifies scannable reading and point-by-point organization.

HTML Block

A block that lets you insert custom HTML directly into the page, including embeds, widgets and iframes.

Use: it is appropriate when the standard editor does not cover the required case.

Share Block

A component with sharing buttons or icons for publishing content on social networks and external channels.

Use: it expands content distribution.

Cookies Block

An information and consent component related to cookie usage and navigation data collection.

Use: it touches privacy, compliance and tracking activation.

Attributes List Block

A block used to present attributes, features or specifications in an organized way.

Use: it makes comparison and factual detail easier to read.

Search Results Block

A component that shows results matching the terms entered in an integrated search.

Use: it improves discovery of pages and configured content.

Hotspot Block

A block with clickable points over an image or composition to reveal contextual information.

Use: it is useful for exploring details interactively.

Power BI Block

A component for embedding Power BI dashboards and reports within the website.

Use: it brings content and data visualization closer together in the same context.

Snippet Block

A block that injects a reusable content snippet into multiple pages or categories.

Use: it guarantees consistency and avoids manual duplication.

Submitted Forms Block

A component aimed at displaying received submissions, usually in an internal or operational context.

Use: it connects data capture to the practical review of responses.

Card

A modular visual unit that combines elements such as image, title, description, icon and link in a compact, quick-reading piece.

Use: it is the foundation of the Cards List and many editorial hubs.

Attribute / specification

Structured data used to highlight features, properties or factual details of a product, service or entity.

Use: it makes comparison and technical reading easier.

Hotspot

A feature that highlights specific areas of an image or interface and makes them interactive.

Use: it turns a static visual into an explorable piece.

Interactive point

A clickable marker inside a hotspot, usually numbered or highlighted, that opens related contextual content.

Use: it helps explain specific parts of a complex visual.

Dashboard / embedded report

A data visualization embedded inside the page to show metrics, charts, tables or operational reporting.

Use: it brings data and narrative closer together in the same navigation context.

Blocks Info

A Feature Bar tool that shows the block name, skin, margins, spacing and snippet indication.

Use: it is especially useful when you need to quickly identify what you are seeing on the frontend.

Images Size

A query option in the Feature Bar that lets you see the sizes of the images present on the page.

Use: it helps validate weight, suitability and visual performance.

Embed / iframe

A way to embed external content or specialized components such as maps, videos, widgets or dashboards.

Use: it is a useful solution when the functionality comes from outside the CMS.

Menu

An organized set of links used to structure the main, secondary or contextual navigation of a website.

Use: it is one of the user's main orientation systems.

Menu item

Each individual entry inside a menu, with its own label, destination, behavior and properties.

Use: it is the smallest configurable unit of navigation.

Submenu

A second navigation level created when a menu item starts containing related subitems.

Use: it should only exist when the relationship between pieces of content is clear.

Mobile menu

A version of the menu adapted to mobile devices, usually with a collapsed structure and its own interaction pattern.

Use: it needs to stay coherent with desktop navigation.

Link to page

A type of menu item that points to an existing page or category within the project itself.

Use: it should be the default choice for content already created in Studio.

Custom link

A manual link used for external URLs, anchors, documents or destinations that do not exist as project pages.

Use: it covers special scenarios outside the page tree.

Open in

A setting that controls whether the item opens in the same window or in a new tab.

Use: it influences navigation behavior and user expectations.

Item URL

The effective destination configured on a menu item, whether internal, external or contextual.

Use: it needs to be validated whenever structural changes happen.

Item CSS classes

Advanced fields that let you add specific classes for the visual or technical treatment of an item.

Use: they should only be used when they add real value.

Item logo

An advanced option that lets you associate a specific graphic element with a menu entry.

Use: it is useful in special visual cases, not as a general rule.

Permissions

Rules that condition the visibility or access of certain menu items for specific profiles or contexts.

Use: they help control navigation by access context.

Main, secondary, contextual and utility navigation

Different navigation layers that serve different goals within the website layout.

Use: separating these roles improves clarity and information architecture.

Form

In Studio, a form is an autonomous functional entity with its own lifecycle: it collects, validates, notifies, stores and exports.

Use: it should be thought of as a complete flow, not just as a set of fields.

Initial form setup

The area where base parameters, messages, redirection, edit permissions, resubmission and overall behavior are defined.

Use: it shapes the experience before, during and after submission.

General settings

The section of the initial setup where internal identification, visible title, post-submission behavior and form base options are configured.

Use: it is the core functional configuration area of the form.

Form blocks

The set of visual fields that make up the editorial dimension of the form: text, email, selects, checkboxes and similar elements.

Use: they shape data collection.

Required field

A field the user must fill in to successfully submit the form.

Use: it should exist only when the data is truly essential.

Validation

A set of rules that checks whether submitted data meets the expected format, completeness and consistency.

Use: it reduces operational errors and improves data quality.

Recipient

The person, team or address that receives and follows up on the form submission after it is sent.

Use: it should be defined before you even design the fields.

Notification template

A reusable email template with name, subject, body and, when applicable, dynamic variables.

Use: it avoids duplication and makes the system more consistent.

Administrator notification

An internal email sent to alert the team about a new submission or event associated with the form.

Use: it should be pragmatic, triage-friendly and action-oriented.

User notification

An automatic response sent to the user to confirm the submission was received and, when needed, explain the next steps.

Use: it reduces anxiety and reinforces trust.

Success and error messages

Texts shown to the user after a submission attempt, whether it ended successfully or failed.

Use: they close the flow with clarity and context.

Messages in Modal

An option that defines whether the form's success or error messages are shown in a modal window instead of inline.

Use: it changes how feedback is presented to the user after submission.

Allow editing / Allow resubmission

Options that define whether the user can change the submitted data or submit the form again.

Use: they have a direct impact on flow behavior.

Submitted forms and export

A centralized history where the team reviews responses, applies filters, clears tests and exports data for external analysis.

Use: it is only truly useful when the form architecture was well designed.

Table fields - Submitted forms

A setting that chooses which data appears in the form submissions list inside the backoffice.

Use: it improves operational reading and makes the history more useful for internal teams.

Block Group

A structural form component used to group related fields, create columns and control visual spacing.

Use: it organizes long forms into clearer sections.

Machine name

The technical identifier of the field, which should be unique, stable and coherent for notifications, exports and integrations.

Use: it should be treated as an architectural element, not as a secondary detail.

Label

The visible text that presents to the user the meaning and function of each field in the form.

Use: it should be clear and never replaced only by a placeholder.

Placeholder

Temporary text inside the field that works as contextual support and an example of what to enter.

Use: it helps, but it should not carry the field's main instruction.

Form cols

A parameter that controls the width of the field inside the form grid.

Use: it helps balance layout, density and readability.

Query parameter / automatic value

A setting that lets certain fields be filled automatically from parameters present in the URL.

Use: it is useful for campaigns, tracking and pre-contextualizing forms.

Text input

A basic short-text field used for names, job titles, companies and other simple one-line data.

Use: it is the most common input type in forms.

Textarea

A multi-line text field used for messages, descriptions or answers that need more writing space.

Use: it is appropriate when the user needs to develop the response.

Select

A dropdown selection field, suitable when there are several options but not all of them need to be visible at the same time.

Use: it makes the interface more compact, but increases cognitive load if used poorly.

Multiple select

A variation of the select field that allows choosing more than one option in the same field.

Use: it should be used only when multiple selection truly makes sense.

Radio button

A single-choice field in which all options remain visible to the user.

Use: it is preferable to a select when the visibility of the options matters.

Checkbox

A field used for confirmation, consent or multiple selection of independent options.

Use: it is common for permissions, preferences and formal acceptances.

Hidden input

A field invisible on the frontend but used to carry technical or contextual values relevant to reporting and integrations.

Use: although invisible, it can be critical for later data interpretation.

System fields

Fields tied to internal project logic, such as domain, state or other system-specific structures.

Use: they need clear functional documentation to make sense in the process.

SEO

A set of practices that improves website visibility in search engines and helps attract qualified traffic.

Use: it crosses content, technique, structure and performance.

Metadata

Additional page information used to contextualize content for search engines and external platforms.

Use: it helps the system understand what the page offers.

Meta title

The title that tends to appear in search results and should summarize the page clearly and relevantly.

Use: it is one of the main drivers of organic clicks.

Meta description

A short text that accompanies the title in search results and works as an invitation to click.

Use: it should be descriptive, compelling and aligned with the page.

Meta keyword

A legacy keyword field that carries little weight in modern search engines today, but can still support internal organization.

Use: it does not replace a real content strategy.

Open Graph

A set of metadata that controls how the page appears when shared on social networks and external platforms.

Use: it defines the visual and editorial clarity of the share preview.

og:title / og:description / og:image

The main Open Graph trio: title, description and featured image used in the share preview.

Use: they should be thought of as the social packaging of the link.

H1

The main page title, which should be unique and reflect the central theme of the content.

Use: it organizes reading and reinforces semantics.

H2 / H3

Subheadings used to organize sections and content subdivisions throughout the page.

Use: they work as the logical index of the reading flow.

Image ALT / TITLE

ALT describes the image for accessibility and SEO; TITLE provides context but has less impact.

Use: it improves technical understanding and assisted reading experiences.

Organic traffic

Visits that reach the website through natural search, without direct ad investment.

Use: it is an indicator of relevance and long-term consistency.

Indexing

The process by which search engines register the page and consider it eligible to appear in results.

Use: without indexing, the page exists but is unlikely to be discovered through search.

Keyword

A term or phrase that summarizes the main intent of the page and helps align content with real demand.

Use: it guides titles, metadata and editorial focus.

User experience (UX)

The quality of a website's navigation, clarity and ease of use, a factor that is increasingly important for SEO.

Use: a site that is easier to use tends to perform better organically.

Loading speed

How quickly a page becomes available and usable for the visitor.

Use: it affects retention, UX and how search engines evaluate the site.

Mobile-friendly

The ability of a website to work properly on mobile devices, with reading and interaction adapted to smaller screens.

Use: it is a basic expectation for both SEO and modern user experience.

Authority

The perception of trust and relevance that a website builds with users and search engines.

Use: it influences visibility, credibility and competitiveness.

Backlinks

Links from other websites to your content, especially valuable when they come from relevant and trustworthy sources.

Use: they are one of the classic authority signals.

Technical SEO

An optimization layer that covers URL structure, crawling, security, indexing, performance and other technical signals.

Use: it supports the content so it can be correctly understood and served.

Conversion rate

The proportion of visitors who complete the desired action, such as contacting, subscribing or buying.

Use: it shows whether traffic is generating results and not just volume.

HTTPS

The secure version of the web protocol, used to protect communication between the browser and the website.

Use: it is a basic requirement for technical trust and SEO good practice.

Google Analytics

A measurement tool used to track traffic, behavior, visit sources and website performance.

Use: it turns visits into an analytical view of the project.

Property

The Google Analytics unit that represents the website or app being monitored.

Use: it is the right foundation for collecting data in the right project.

Measurement ID / GA4 tag

The technical identifier associated with the Analytics property that connects the site to data collection.

Use: it is what actually connects the frontend to the measurement platform.

Google Tag Manager

A tool for managing tags, scripts and tracking without editing the site's code on every change.

Use: it centralizes the technical governance of tracking.

Container

The main GTM package where tags, triggers, variables and versions of the tracking setup live.

Use: it is the technical container that Studio needs to receive correctly.

Tag

A code snippet or measurement instruction that fires a specific integration, event or tool.

Use: it is the operational tracking unit inside GTM.

Trigger

A condition that defines when a tag should fire, for example on click, submission or page view.

Use: it controls the moment and context of activation.

Variable

A dynamic value used by tags and triggers to read information from the context, the page or the interaction.

Use: it gives tracking flexibility and precision.

Preview Mode

The GTM preview mode used to validate tags before publishing changes.

Use: it reduces the risk of publishing incorrect tracking.

Header Script

A script placed in the page <head>, common in integrations such as Analytics and GTM.

Use: its position influences loading and technical behavior.

Body Script

A script placed immediately after the opening <body> tag, used in setups such as GTM.

Use: it complements installations that require separation between head and body.

SMTP

A technical configuration that allows the website to send automatic notifications, confirmations and other operational emails.

Use: without it, many form flows stop closing properly.

Host / Port / authentication

The set of email server technical data: host address, port and authentication credentials.

Use: any mistake here can block email delivery.

Sender email, sender field, CC and BCC

Parameters that define who sends the notification, whether the sender is dynamic and which additional recipients receive a copy.

Use: they determine the real addressing of the messages.

Editable languages

Per-language areas where certain scripts, integrations and settings need to be replicated for each active project language.

Use: it avoids incomplete installations on multilingual websites.

Redirect

A rule that sends an old URL to a new destination, preventing the user and the search engine from hitting an error.

Use: it is critical in migrations, reorganizations and structural cleanup.

301

The permanent redirection code recommended when a URL change should be treated as definitive.

Use: it helps preserve continuity and SEO signals.

404

The error shown when the requested destination does not exist or is no longer accessible without a valid forwarding rule.

Use: it is one of the most common signs of incomplete maintenance.

Source URL

The old address or initial pattern that the redirect rule tries to capture.

Use: it needs to be written precisely to avoid failures or conflicts.

Target URL

The final address where users and search engines are sent after the rule is applied.

Use: it should be published and accessible before the rule is activated.

Redirect priority

A value used to order or resolve the application of rules when there are potentially competing patterns.

Use: it prevents collisions between redirects.

RegEx

A regular expression used to define flexible URL patterns and cover multiple scenarios with fewer rules.

Use: it is powerful, but it should be validated carefully.

Robots.txt

A technical file that tells search engines which areas may or may not be crawled.

Use: it belongs to the crawl-governance layer.

Sitemap XML

A technical map of the site's URLs sent to search engines to make page discovery and monitoring easier.

Use: it is an important piece of the indexing strategy.

Google Search Console

Google's tool for monitoring indexing, coverage, organic performance and crawl issues.

Use: it shows how Google technically sees the site.

SEO Report

A Studio panel used to track optimization elements, identify errors and prioritize fixes on site pages.

Use: it brings editorial review closer to technical maintenance.

WEBP

A lighter and more efficient image format designed to improve loading and the technical foundation of performance.

Use: it reduces weight without compromising visual quality too much.

Descriptive file name

A good practice of naming images with clear, contextual terms instead of generic names like image1.jpg.

Use: it helps search engines understand the asset better.

Louro.AI

A set of AI capabilities inside Studio for text generation, automatic translation and image creation.

Use: it accelerates editorial production and creative exploration.

Automatic translations

A Louro.AI feature that adapts content to other languages with automatic support inside the editorial workflow.

Use: it reduces the time needed for multilingual expansion.

AI-assisted writing

Writing help for generating drafts, unblocking blank pages and speeding up first versions of content.

Use: it brings speed, but it still requires human review.

Generate image with AI

A flow in which the user describes what they need and the system returns a generated visual asset within the Studio ecosystem.

Use: it shortens the path between a visual idea and a usable prototype.

Prompt

A written instruction used to guide AI in generating text, images or content adaptations.

Use: the clearer and more contextual it is, the better the result tends to be.