Dear Tumult Hype team,
We are looking to seamlessly integrate a Tumult Hype website into Microsoft Azure without the need for extensive replication. This is because we intend to add various elements to the website, including feeds, a webshop, SEO optimization, and most importantly, a Content Management System (CMS).
Initially, our plan involved creating a Hype Mockup that needed to be replicated, with the animated headers being placed as HTML elements. Additionally, we were considering replicating the menu and overlaying it on the header, which exists within something akin to an i-frame.
However, the process of replication has proven to be labor-intensive and imprecise. Therefore, we are in search of a more elegant solution.
The website was designed in Tumult Hype and is fully responsive, with two states: mobile (portrait) and desktop (landscape). It features responsive text boxes that are linked on a symbol basis for both computer and mobile versions, ensuring that changes made in one version are reflected in the other. These text boxes contain formatted text that adjusts in size to fit the situation.
There is also a menu for desktop and one for the mobile version, both linked on a symbol basis. Furthermore, they are linked to the titles of the respective pages.
The content remains the same for both devices, with scaling applied to achieve the desired size. The underlying symbols are shared between both versions.
However, the challenge lies in integrating this website into Microsoft Azure. The current method involves importing the entire HTML page exported from Hype, resulting in a mix of HTML, JavaScript, and CSS that is challenging to separate.
Should I consider exporting components separately? For example, having a file with linked text boxes using unique IDs, another file for the menu, and a separate file for the header. This way, they could be combined into a single page within Azure. This page could serve as a template and the foundation for the CMS, with CSS connections established there, allowing subsequent pages to be created based on the newly developed CMS.
Alternatively, should I make preparations within Hype, such as coding, to facilitate a different integration approach? I would appreciate your guidance on this matter.
Kind regards,
Ellard Ottevanger