Website

Website handles the structure, look and publishing of your site. The text on a page is shown by pointing to your company's explanations in Knowledge.

Because the text lives in one place, correcting it updates every page that points to it. The theme owns the look; your knowledge owns the text. Switching themes leaves the content untouched.

Use the icon at the right of the menu bar to choose between the Simple and Normal menus. Simple is the default.

Simple (chat-first: tell the AI what you want and it does it)

• Run via Chat — ask in chat and approve the changes the AI proposes

Normal (edit pages directly and approve AI suggestions)

• Page Designer — review and adjust one page at a time — structure, look, meaning and links — and publish it
• Forms — manage application forms and their questions
• Site Ops — the way into operating screens such as FAQ, CTAs, Glossary, Media, Redirects, Migration and Validation

With either menu, click Website in the menu bar to open the top page, with cards such as Site Overview, Outcomes (30 days), Recently Edited Pages and Website Pages. Which cards you see depends on your role.

The chapters below explain each menu's screen: how to read it and what you can do there.

Page Designer has three panes: Structure, Layers and Assets on the left, a live preview in the middle, and Appearance, Meaning and Links on the right. Switch the preview between Mobile, Tablet and Desktop.

• Appearance — choose shape: direction, width, spacing, alignment; finer overrides, such as a section's text color, are also possible
• Meaning — point each spot on the page to the explanation it should show
• Links — check the links going out of the page

There is also an AI audit that has the AI check structure, meaning bindings and SEO, export to JSON or Markdown, and Import JSON, which shows you the differences before anything is applied. Publish and Unpublish switch whether the page is live.

Editing is available to Admins and Owners. Other roles see the designer in view-only mode.

Correcting an explanation never rewrites the surrounding text on a page automatically. Instead, the plans that use it are marked for review, together with the change that caused it.

Articles are connected by meaning, based on what each one is about. A related link inside an article is taken off the page once its destination is confirmed to be gone.

Forms is made of three tables: your forms, the questions of the selected form, and the shared question list.

• Create a form with New form, then line up its questions with Add question
• Questions are kept in the shared Question list; add more with New question
• A question can be required, and can be shown only depending on the answer to an earlier one

Forms are never deleted: Retire takes one out of use and Restore brings it back. Each form shows In use or Retired. Changing forms is available to Admins and Owners.

Site Ops is the way into work that is not about one page. Its cards are arranged in three groups.

• Content — FAQ, CTAs, Glossary, Media, Forms
• Health & QA — Redirects, Migration, Validation, AI Actions, Audit
• Growth — Experiments, Ontology Graph

The Experiments card takes you to the Growth Cycle's Experiments screen, the one list of experiments.

Redirects lists the rules that send an old URL to a new one. Migration lists the sources your current site was read from and how many pages were found. Reading in your current site brings over the article text, where the images are, and the URL structure. A URL is treated as a label on a page, so you choose whether to keep or change it. Only pages whose content could be extracted come in, so no empty pages are left behind.

Opening the FAQ card shows a notice that FAQs are managed in Knowledge. FAQ questions and answers are kept as knowledge, and the website reads them from there. You do not edit FAQs on this screen.

• Open Knowledge Objects — go to Objects in Knowledge, where you correct FAQ text
• Search Knowledge — go to Search in Knowledge to find FAQs by meaning

What you correct in Knowledge appears as-is on every page that shows that FAQ.

CTAs, like FAQs, is a notice screen saying they are managed in Knowledge. The text of the calls to action you place on pages — to apply or to get in touch — lives in Knowledge, and pages point to it.

• Open Knowledge Objects — go to Objects in Knowledge to correct CTA text
• Marketing CTAs — go to the CTA list in Marketing

Correcting a CTA in Knowledge updates every page that points to it.

Glossary lists the terms used on this site. Each card is one term.

Reading a card

• The language (EN or JA) at the top left, then the term itself
• A term tied to a page carries a "→ route" mark on the right
• When the written form differs, the correct form appears after "Canonical:"
• Below are the definition (up to three lines) and other ways of writing the term. Up to eight are shown; the rest appear as "+N more"

Narrowing the list

• The search box — find words in the term, its canonical form or its definition
• Locale — All at first; narrow to EN or JA

The count ("N term(s)") appears above, and the list is split into pages of 25. This screen is for reading; you do not add or change terms here. The refresh button at the top right reloads the list.

Media is this site's media library. Images, videos, documents and fonts are shown as cards.

Reading the screen

• The count ("N assets") and the total size ("Total:") appear at the top
• Each card shows its state: draft, review, published or archived
• An item that only points to an external URL shows "External" instead of a size
• The gear changes the layout (Grid or Carousel) and the Thumbnail size (Small, Medium, Large). This only affects your own screen

Narrowing the list

• Kind — All kinds at first. Only kinds the library actually holds are offered
• The search box — find items by words such as the title

Actions (tick the cards first; Select all and Clear selection are also there)

• Upload — opens Upload pictures. First choose Where do these pictures come from?: Own photo, AI-generated, Supplier's page or Third-party site. The origin is recorded with each file. A supplier's or third-party picture shows an image-rights disclosure before it is stored, and your acknowledgement is recorded. The system never rules on whether a use is lawful
• Publish — publishes the selected items after a confirmation. An image placed directly on a page of the public site shows there whatever its status; some features use published images only (for example the listing CSV and library book covers)
• Unpublish — sets the selected items back to draft
• Delete — after a confirmation, removes the file and its sized versions from the library. It cannot be undone. If a page still uses an item, deletion stops and shows where it is used; it is removed only if you press Delete anyway (those pages will break). An item used as the brand's logo or similar is not deleted; you are told to unbind it on the brand first

Redirects lists the rules that forward an old URL to a new URL or page. They are used when an old page is retired, or when you move over from another site.

Reading the screen

• "Total:" and a count for each status code (301, 302, 307, 308) appear at the top
• Each row is one redirect: the status code on the left, then old URL → destination. A redirect tied to one language carries a language mark, and the reason, if any, appears under the row
• The list is split into pages of 25

Narrowing the list

• The search box — find words in the old URL, the destination or the reason
• Status — All at first; narrow to 301 (permanent), 302, 307 or 308

This screen is for reading; you do not add or remove redirects here. A redirect is added when a decision that moves a URL is applied in the Growth Cycle, or when you ask the AI chat to add one.

Migration lists the sources your current site was read from. "N source(s)" appears at the top.

Reading a card

• The kind and name of the source, with its state on the right
• If the site URL and sitemap are known, buttons open them in a new tab
• "Pages discovered:" and the date and time of the last import

Use the search box to find words in the name, URL or kind.

From the panel below the cards you can go to Knowledge Sources (the material that was read in) and Redirects (forwarding from old URLs).

This screen has no Add button. To add a source or run an import, ask the AI chat (give it your current site's sitemap URL).

Validation checks the whole site and lists the problems that stop publishing (blocking) and the warnings. The check runs when you open the screen; a check that only came from opening the screen is not recorded.

Reading the screen

• At the top: "Result:" (Passed, or Blocking issues found), "N blocking" and "N warning(s)", and Ready to publish or Publishing blocked
• Two tabs, Blocking and Warnings. Blocking is selected first
• Each row is one issue: the name of the check, where it is (for a page, its URL and language), and a description
• No SEO details and No CTA rows are about a page, so clicking one opens that page (hold Ctrl / ⌘ to open it in a new tab)
• The search box — find issues by check name, page or description

What is checked

• Blocking: No SEO details — a published page has no SEO details (title, description) for its language / Structured data failed / Past its freshness date — a published item has gone past its freshness date / Shared URL — several pages use the same URL
• Warnings: No CTA — a published page has no section that invites the reader to act (a CTA band, contact form, newsletter sign-up or pricing table; documentation pages are skipped) / Not tied to a problem — a solution or knowledge explanation is not tied to a problem or solution (one row per language)

Run Validation runs the check again, records the result and shows Validation re-run complete. Recorded results are listed in Audit. With no blocking issues you see No blocking issues — publish ready.

Audit is the record of the checks you started with Run Validation on the Validation screen. Each check is one row, newest first. A check that only came from opening the Validation screen is not recorded, so it does not appear here.

Reading a row

• The result on the left (Passed, or Blocking issues found)
• When the check ran
• "N blocking" and "N warning(s)", and Ready to publish or Publishing blocked

Use it to see, date by date, whether blocking issues are going down and warnings are not piling up.

• Run new validation — opens the Validation screen. A row is added when you press Run Validation there
• Automation Audit (Tenant Admin) — opens the automations screen

AI Actions is a guide screen that shows where the AI helps on your website and on which screen you use each kind of help. Nothing runs from this screen. It has three cards.

• Contextual Assist — AI suggestions that fit the page or section you have open. Open Projections goes to the page composition screen
• Projection Audit — the AI checks an existing page composition. Open Pages goes to your page list
• Migration Assist — AI help when moving an old site over. Open Migration goes to Migration

As the AI Pair Integration panel below explains, the chat on the right receives the screen and scope you have open. Ask something like "audit this page" to use the same help from chat.

The Experiments card in Site Ops takes you to the Growth Cycle's Experiments screen. Experiments that put a hypothesis to the test are managed there, in one place per brand. There is no separate list of website-only experiments.

A person moves each experiment one step at a time, from proposed to running, measuring and concluded. What a concluded experiment taught is proposed to Knowledge, and once you approve it, it stays as knowledge.

The Ontology Graph shows, as a diagram, how the site's pages are put together. It has three tabs, and under the tabs a line explains how to read the one you are on.

• Design parts — themes, layouts and section types. A line means at least one page uses the two together, and its number is how many pages do
• Pages — each page (by URL and language) and the theme and layout it names. A page that names none uses the site default, and that line is not drawn
• Delivery — each page and the render policy that delivers it

Reading the screen

• At the top, the number of nodes and edges, and how many are shown
• The colour legend gives a count for each kind of part
• Click a point to open its details on the right, with the lines that connect to it
• Sub-type narrows to one kind of part, and the search box finds points by a word in their name (their direct neighbours are shown too)
• Pages are shown up to the first 200 by URL; past that the screen says so

Ask in chat and the AI drafts a page. It is applied when you review and approve it. Operations that can be tried out are checked before approval; the rest have their input checked when they run.

The explanations a page shows live in Knowledge, and article plans are made in Marketing's Strategy Designer. Forms are used by both products and pages, so before you retire one, the table shows where it is used.