feat: implement html and bundled webapps

[nazarfil]

A short, meaningful PR description. Explain the goal of the PR and the ideas behind it.
Closed : HEXA-1455, HEXA-1442

Changes

Please list / describe the changes in the codebase for the reviewer(s).

• Added html webapps rendering , to cover plain html and html with assets
• Changed UI of the webapps page
• Use file storage for bundled webapps, and store the zipped archive in database
• add content field for webapps to register plain text content, for example forw ebaps as well

How/what to test

• Create an HTML type webapp, add code, edit code, save the app and go to play page.
• Create or adit a webapp of type Bundle, upload a webapp bundle containing html index page and related assets, you can compile any sample of react app.

Screenshots / screencast

Screen.Recording.2025-12-17.at.09.06.47.mov

[Copilot]

Pull request overview

This PR implements support for HTML and bundled webapps, expanding beyond the existing iFrame and Superset types. The implementation adds the ability to create webapps with plain HTML content or uploaded zip bundles containing complete web applications.

Key changes include:

• Added HTML and Bundle webapp types with corresponding content storage fields
• Implemented backend views to serve HTML content and bundle files
• Created type-aware form fields with preview capabilities for different webapp types

Reviewed changes

Copilot reviewed 26 out of 26 changed files in this pull request and generated 10 comments.

Show a summary per file

File	Description
frontend/src/webapps/features/WebappForm/WebappForm.tsx	Added type-specific form fields (HTML editor, bundle uploader) with preview functionality
frontend/src/webapps/features/WebappIframe/WebappIframe.tsx	Updated to construct URLs based on webapp type (HTML/Bundle/iFrame)
backend/hexa/webapps/models.py	Added content and bundle fields to Webapp model, made url optional
backend/hexa/webapps/views.py	Implemented views to serve HTML content and bundle files from webapps
backend/hexa/webapps/schema/mutations.py	Added content input flattening logic to handle different webapp types
frontend/src/graphql/types.ts	Updated GraphQL types to support WebappContentInput union type
backend/hexa/webapps/tests/	Added comprehensive test coverage for views and mutations
frontend/next.config.js	Added rewrites to proxy webapp content requests to backend

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[nazarfil]

applies oneOf on InputType to only allow either content, bundle or html

[bramj]

As discussed yesterday: The UX is great and it's working well 👍

I was able to migrate the site https://github.com/BLSQ/site-pev-rdc-reports to a web app, and after making sure to build it with relative paths to the assets, it worked great!

The problem is: with the current implementation, every link from the web app is served by hitting a path like for example /bundle/assets/styles.css, and every call to /bundle/* will call the database of the .zip, extract it and return the correct file.
My fear is that when web apps start containing for example large json files to serve data, we'll start seeing performance issues soon (I suppose memory issues because of unzipping).

So we should explore an alternative approach such as unzipping on storage after upload and storing the bucket name on the web app. When serving the app we can then serve directly from the blob storage.