Hyperflow Files & Folders

Websites serve a lot of purposes and in many scenarios, web developers need to place special files at special URLs on their site.

Unfortunately Webflow has strict limits on the type of files you can upload, and all uploaded files are stored on a separate CDN at URLs that are unrelated to your website domain.

Sygnal Hyperflow solves this by providing a full routing layer that enables you to place special files on your site in special places;

Integrate external code & assets

Embed an entire Github repo, Netlify folder, or Amazon S3 bucket directly in your Webflow-hosted site as a folder to make it accessible and SEO-friendly.

For SEO experts, this is important for asset SEO.

For developers, this can be essential for samesite security considerations.

Compliance & configuration files

Create the files you need and serve them under the compliance-required paths directly. For example-

• ‍ads.txt: This file is used for advertising transparency. It stands for Authorized Digital Sellers and is part of the Interactive Advertising Bureau’s (IAB) initiative to combat fraud in the programmatic advertising ecosystem. It lists all the companies that are authorized to sell a website’s digital advertising inventory.‍
• .well-known/security.txt: A proposed standard for websites' security information, used to describe the security policies of a web service.
• .well-known/apple-app-site-association: Used for deep linking in iOS apps.
• .well-known/apple-developer-merchantid-domain-association, used for Apple Pay verification.
• ‍.well-known/assetlinks.json: Used for deep linking Android apps.
• .well-known/browserid: Used for Mozilla’s BrowserID implementation.‍
• crossdomain.xml: Used by Adobe Flash Player and Microsoft Silverlight to permit cross-domain requests. It’s a security file that controls the ability of external domains to access your content.
• Industry-specific compliance files
• ... and many, many more.

Technical configuration files

Some of these files are already used by Webflow, but we can expand them without affecting Webflow's current needed data availability, e.g.;

• ‍manifest.json: For Progressive Web Apps (PWAs), this file is used to define the application's metadata, appearance, and behavior when installed on a user's device.
• sitemap.xml: Can be auto-generated and then modified programmatically.

Contact Us

We love working with great clients, and building great systems.

Do you need this feature on your site? Contact us.