As a dotCMS user, I want to be able to use the new page editor with VTL rendered pages.
This should only apply to pages that are not headless. When the feature flag is set, the new editor should display a VTL rendered page in the editor iframe.
### Acceptance Criteria
- [ ] The feature flag must be set the rendering of HTML from the page API in the new editor.
- [ ] This don't include any editing and or tooling, just render the code
// Step 1: Create the content
var htmlContent = '<!DOCTYPE html><html><body><h1>Hello, World!</h1></body></html>';
// Step 2: Create a Blob from the content
var blob = new Blob([htmlContent], { type: 'text/html' });
// Step 3: Create a Blob URL
var blobUrl = URL.createObjectURL(blob);
// Step 4: Set the Blob URL as the iframe source
var iframe = document.createElement('iframe');
document.body.appendChild(iframe);
iframe.src = blobUrl;
We don't know the implications of this in terms of permissions and cross-origin issues.
Assumptions & Initiation Needs
The feature flag for rendering HTML from the page API in the new editor should be implemented and activated.
The VTL template associated with each page should be correctly defined and accessible.
The new editor should be integrated with the page API to retrieve the HTML content for rendering.
Parent
27546
Task description
As a dotCMS user, I want to be able to use the new page editor with VTL rendered pages.
This should only apply to pages that are not headless. When the feature flag is set, the new editor should display a VTL rendered page in the editor iframe.
External Links
We can try to use Blob to render the
HTML
We don't know the implications of this in terms of permissions and cross-origin issues.
Assumptions & Initiation Needs