Source: https://docs.amadalis.ai/composer/formatting-and-shared-content/

# Format text, links and shared content

Checked against the product’s code on 7 November 2026.

Open the page in [the Composer](https://docs.amadalis.ai/composer/composer/).

1.  Select editable text.
2.  Choose **Edit text**.

You can also double click the text when that field supports it. The format bar follows the kind of text being edited.

## Format the selected words

1.  Select the words you want to format.
2.  Choose **Bold**, **Italic** or **Link**. The text style menu offers paragraph and heading styles, lists or a quote where the field supports them. More text controls include underline, strikethrough, code, text colour and highlight.

A full [rich text](https://docs.amadalis.ai/reference/glossary/#rich-text) field, which holds formatted content, can also offer images, tables or blocks of code. A shorter text field may refuse those structures. Read a refusal rather than expecting every field to behave like a document editor.

When editing a table, the bar changes to its table controls. Review the selected row, column or cell before changing it. Finish the text edit and inspect the resulting draft before publishing.

## Choose media and links

1.  Select the section or element.
2.  Open **Settings**.
3.  Beside a media field, choose **Choose from library**. Beside a link destination field, choose **Choose a page or file**. A filled field can offer **Change** instead.
4.  Select a stored file, upload a supported file or choose the destination the field accepts.

To link selected words instead, use **Link** in the text format bar. The destination is separate from the visible link wording.

## Set an anchor or CSS classes

Editors and Admins can set these. The change needs the right to publish, even on a draft.

Use this when a link, stylesheet or outside integration needs to identify part of a page. A section can have an HTML anchor and extra CSS classes. A nested element can have extra CSS classes only. These markup names do not add JavaScript.

### Use Composer

Finish other pending edits in the inspector before changing these names.

For a section:

1.  Select the section itself in Composer.
2.  Open **Settings**.
3.  Expand **Advanced**.
4.  Change **HTML anchor** or **Additional CSS classes**.
5.  Choose **Review targeting changes** in the inspector’s footer.

For a nested element:

1.  Select the element in Composer.
2.  Open its **Settings**.
3.  Expand **Element targeting**.
4.  Change **Additional CSS classes**.
5.  Choose **Review targeting changes** in that element’s settings.

Then read **Change these targeting hooks?** and choose **Apply targeting hooks** only if the target and names are right. Check the draft preview and publish separately when ready.

### Ask the copilot

1.  Open the page in Composer and identify the section or element.
2.  Ask the copilot to give that section a named HTML anchor, or to set extra CSS classes on the named section or element.
3.  Read **Change these targeting hooks?**, checking the page and target.
4.  Choose **Apply targeting hooks** only when the target and names are right.
5.  Check the draft preview and, for an anchor, the link to that place.
6.  [Review and publish](https://docs.amadalis.ai/composer/composer/#review-and-publish) the draft separately when ready.

The card is required even on a draft. Anchors must be unique on the page; reserved platform names are refused. Outside CSS, analytics or experiment selectors may match differently after publication. Use the receipt’s **Undo** while it can still restore that revision; a newer draft is not overwritten. See [Targeting hooks](https://docs.amadalis.ai/reference/copilot/pages-and-sections/#pages).

## Recognize shared words

A header link either belongs to a [menu](https://docs.amadalis.ai/reference/glossary/#menu) or is another page’s own title. Renaming a menu link changes it on every page that shows the menu. Renaming a page title link renames that page and its heading as well as the navigation on every page. Read **Rename this menu link?** or **Rename this page?** and its timing explanation before confirming.

A menu link rename goes live when you publish that menu. A page title rename goes live when you publish that page. Until then visitors see the old words, and you can undo the change.

For site wide styling, use [Themes and tokens](https://docs.amadalis.ai/composer/themes-and-tokens/). For menu publication, use [Menus](https://docs.amadalis.ai/site/menus/).

### Change the shared site name, tagline or footer line

An Admin can change the site’s name or tagline. Editors and Admins can change its footer line. Check the effect beyond the page you are editing.

1.  Ask the copilot to change the site’s name, tagline or footer line to your exact new words. You can request the name and tagline together.
2.  Read **Update the site’s identity?** and the current and proposed words.
3.  Check the site wide effect before deciding.
4.  Choose **Publish this change** if it is right.
5.  Read the receipt, then check the site’s own address as the updated page reaches visitors.

Use the receipt’s **Undo** while no newer edit has replaced those words. An empty footer line clears that saved line. It is separate from the generated year and site name in the credit. An imported page can use a separate footer, so this change need not replace its imported copyright words.

See [Shared site details requests](https://docs.amadalis.ai/reference/copilot/site-and-settings/#site-identity-and-setup).