Insert complete HTML page into project

[traco]

I have a complete page written in html (not developed with wysiwyg) that I want to insert into the site. What is the best way to insert it into the project?.
Thanks

[BaconFries]

First please note that WWB is not a HTML Editor but a HTML Generator what this means is that the HTML doesn't exist till published. So you cannot just drop the code (HTML) onto a blank workspace and hope it will work.
You can use the following:Importing HTML by first saving the HTML as an external page with the .html extension or .php if it is using any php and then import the page you will also need to give reference to it in any of the menu or navigation used so to be able to go back and forth to it once published.

[onlye]

you could also save your page as an html page to the server then use an iframe to insert your page into a wizzy page. i use this on several client sites.

[FritsWolf]

Dear 'onlye', can you explain to a new user of 'wizzy' how the iframe link would point to the html file on the server?

[onlye]

Dear 'onlye', can you explain to a new user of 'wizzy' how the iframe link would point to the html file on the server?

put a layout grid on a page. put an i frame in the layout grid. in the iframe reference the html page.

you can use the site manager to pull in an html page to your project. that could be your page that you use the ifram to display.

[wwonderfull]

I’ve seen a lot of folks suggest saving a page as HTML and then dropping it into a WYSIWYG page via an iframe. I’ve used this approach myself on a few client sites, but honestly, it comes with some problems you’ll want to keep in mind.

1. SEO: Search engines don’t really index iframe content well, so you’re basically hiding that page from Google.

2. Performance: Every iframe is another request, which can slow download times.

3. Responsiveness: Making iframes behave nicely on mobile can be a pain. You often end up fighting with scrollbars or fixed widths.

4. Styling: The embedded page won’t inherit your site’s CSS, so fonts/colors/layouts can look out of place.

5. Accessibility: Screen readers don’t handle iframe content smoothly, which can hurt usability.

6. Maintenance: You now have two separate files to keep updated meaning the main site and the iframe content. Easy to get out of sync.

So iframes can be a quick fix, but they’re not ideal for long-term projects. If you want reusable content, it’s usually better to integrate it directly into your wwb project using html snippet instead of iframe. After reading all this you can now continue based on the pros and cons.


There is also an alternative way like using file publisher tool to just add that html page and when publishing it will be uploaded to specific folder or path based on your structure and path.