> For the complete documentation index, see [llms.txt](https://docs.elsaworkflows.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.elsaworkflows.io/studio/design/workflow-editor-3.5-preview.md).
# Workflow Editor (3.5-preview)
As of version 3.5.0, the default workflow editor got a minor UI refresh.
However, if you prefer the previous look, change the following in your Blazor projects Program.cs:
```csharp
builder.Services.AddServerSideBlazor(options =>
{
// Comment out the V2 activity wrapper (default).
//options.RootComponents.RegisterCustomElsaStudioElements();
// To use V1 activity wrapper layout, specify the V1 component instead:
options.RootComponents.RegisterCustomElsaStudioElements(typeof(Elsa.Studio.Workflows.Designer.Components.ActivityWrappers.V1.EmbeddedActivityWrapper));
options.RootComponents.MaxJSRootComponents = 1000;
});
// Add this for the V1 designer theme (default is V2).
builder.Services.Configure(options =>
{
options.DesignerCssClass = "elsa-flowchart-diagram-designer-v1";
options.GraphSettings.Grid.Type = "mesh";
});
```
In the \_Host.cshtml file (or index.html in case of WebAssembly), in he `` element:
```cshtml
@* Comment out the V2 designer.css. *@
@* *@
@* To use designer.v1.css for the old designer. *@
```
You should now have the old design back.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.elsaworkflows.io/studio/design/workflow-editor-3.5-preview.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.