ChrispinP
commented
1 year ago Research & Testing:
I tested an embed script for the TDS Customer Portal in Weebly which looks like so:
Things to note:
- Top nav menu is present no matter what which limits use cases since a user can navigate anywhere in the app they have permission. This leads to the desire to develop specific pages for embedding that do not have any top nav which results in needing the entire top nav menu being locked down by permissions or a whole separate knack app just for the embed.
- Additionally, top nav formatting does not carry over 100% of the time resulting in underlining occurring for top nav tabs
- Font and text generally translate well with the exception of Menu Titles and List Titles. This results in having to use Rich Text fields for Title text to display properly.
- Href links would lose functionality so custom button links would need to become standard knack menu buttons or updated with the Weebly url. Knack menu buttons work as expected for navigation and opening new tabs.
- Our custom code that affects back links and breadcrumb links would need to be included with the embed script since its not a default feature, otherwise multi-page application structures would not work well as an embed since users can navigate to any previous page.
Summary: Hard pressed to think of a great use case for embedding in a website, which makes me think embedding into another Knack app (if possible), would result in similar functionality deficits.
1) The best use case would probably be a series of multiple Knack apps where you have single page forms, without any top nav, that you can embed throughout your website on different pages. This begs the question as to why not just build it in something like Formstack, or a built in website app such as Jotform or Boom, which are supported in Weebly, since the data would be stored in separate Knack apps already.
2) Another use case would be to embed a landing page for a full Knack app such as the home page to use an entire Knack app within a website that does not have multi-page processes. This could be useful for adding database content & other Knack functionality to an active website without having to build these views & features on the website from scratch or use a new url. A possible "instead of" or "stop gap" option.
3) As we continue to produce more customer facing portals, it may worth combining them all together into a cohesive experience all on one site with their respective pages embedded.
4) After some further research it should be possible to pass our custom JavaScript in the HTML5 script for the embed code. This would be necessary to disable breadcrumbs and back links for our multi-page application flows to maintain functionality and make embedding a feasible option.
Ability to embed a Knack app into another Website in addition to another Knack app.