Can I Customize the URL String Parameters for Filtering?

If only it were that simple! While we can't make this happen exactly as you've envisioned, we're here to shed some light on why and help you understand the nuts and bolts behind the scenes.

Many Jetboost users aim to enhance their Webflow projects with dynamic content filtering functionality. A common discussion point is the customization of URL query parameters to achieve cleaner, less distracting URLs for filtering content. This documentation aims to clarify Jetboost’s capabilities in this area.

Understanding URL & Query Strings

URL Strings are composed of 3 main parts: Protocol (https), Domain (www.example.com), and Path (/path/to/page). We utilize URL Strings to navigate websites and access resources.

An optional, yet commonly utilized part is the Query String, which typically follows a standard web pattern. It begins with a ? to initiate the query, followed by parameters consisting of key-value pairs joined by =, and separated by &. An example is: ?category=design&tags=figma1%Cframer.

Jetboost enhances filtering functionality by leveraging URLSearchParams, a web API provided by modern web browsers designed to work with the query string of a URL efficiently. While query strings can be formulated in various ways if you control the server architecture, Jetboost operates within Webflow's framework.

Beyond straightforward key-value pairs, there might be a desire for more advanced or visually appealing modifications, such as using paths (/val1/val2) instead of traditional query strings for cleaner URLs. However, such modifications usually require server-side URL rewriting or specific routing logic in web applications to interpret path segments as query parameters. Since Webflow controls the directory path—given it's their platform—Jetboost does not have access to make these alterations.

Alternative Approach within Webflow

We understand this may not perfectly align with your vision. If having clean, aesthetically pleasing filter queries is crucial for your project, considering Webflow's native dynamic pages for each query could serve as an alternative. This route, however, will not offer the same dynamic filtering capabilities provided by Jetboost.

Conclusion

Webflow dictates the URL strings, and Jetboost capitalizes on URLSearchParams to dynamically filter CMS content within the URL string, adhering to standard query patterns.

This constraint is not exclusive to Jetboost but rather reflects general web development practices: utilizing URL strings and queries to differentiate between navigating pages and filtering content within a page or site-wide.

We're dedicated to helping our users make the most of Jetboost's tools and functionalities within Webflow's framework. If you have any further questions or need additional information, our support team is eager to assist you. Please don't hesitate to reach out!