Studio

Studio connects a requested change to an existing project page. Select the project first, then open Studio. Describe the current behavior and the result you expect.

Before you start — Select the project and an existing page. Prepare the current behavior, expected result and an example. The page field accepts a known URL or name search; the arrow prepares a row and the final submission sends the batch.

Select a page by its URL

Use the URL to identify the target, then check the suggested project context.

1. Open the page to change and copy its complete URL.
2. In Studio, paste it into Page name or URL.
3. Check the selected page and the accompanying project context.
4. Read the selected Module and Part before writing the request.

A URL must belong to the selected project's known services and identify an available page. Another project's link cannot be used to choose its page here.

Find a page without its URL

Search by name when you lack the address or the project does not recognize the URL.

1. Click Page name or URL.
2. Type part of the page name.
3. Choose the matching existing page from the suggestions.
4. Check the target before continuing.

The existing page is selected without creating a page or changing its address.

Name search remains available in the same field as URL lookup.

Note — A page is not the only target. Choose only a Module to request a change to the whole module, or choose Menu in Part to change the left navigation. When your project has them, the Section picker also targets Website, Documentation, API or Preview.

Prepare and send a change

Separate preparing the request from submitting it so you can review the wording and target.

1. Describe what happens now, what should happen and a concrete example in the request field.
2. Click the arrow marked Add to list to prepare the item.
3. Review the pending list that appears above the request field.
4. Click Send all to submit the prepared requests.
5. Read the confirmation or error message.

The arrow adds a pending row. It does not perform the final batch submission.

A useful request could say: “After a validation error, keep the entered company name and number and show which field needs correction.” It names an action, an exception and the visible outcome to test. Prepare unrelated changes as separate rows rather than hiding several results in one vague request.

Manage a batch before submitting

Keep related adjustments in one area, with a separate row for each result to review.

1. Add related requests for the same business area.
2. Use Edit to revise a prepared row.
3. Use Remove to discard a row you do not want to send.
4. Submit the reviewed batch with Send all before changing to another area.

The pending list contains the intended changes and retains a consistent context.

Note — The first item fixes the batch context. Mixing areas is refused. If only part of a batch was sent, inspect the confirmation and remaining rows before retrying; do not recreate successful requests.

Follow the submitted result

Follow questions and the recorded result from the submitted request, then check the actual journey.

1. Read Changes in progress or open the request history.
2. Open the request and read Your request and the build state.
3. Use Answer the questions when clarification is needed.
4. Read What was done when a result is available.
5. Test the changed page in development, then follow the version publication workflow.

The expected behavior is reproduced in development and its release is checked before publication.

Note — Until a request is delivered, you can click Delete on its detail page; this also cancels the build work still open for it. A delivered request stays in the history and can no longer be deleted.

Resolve a page or submission problem

Identify whether the difficulty concerns the target, preparation, submission or published result.

Tip — A precise request names a user action and its expected result, such as keeping the entered fields after a validation error.