Please tell us how we can make Clutch more useful for you.
Share Your Feedback
Code with AI Improvements
When using AI tools like Cursor, VS Code with Copilot, or other prompt-based assistants, the default output often lacks the structure or context needed for Clutch-specific components and files. This project exists to create a custom-tuned prompt that improves how AI understands and generates code within the Clutch ecosystem — leading to more accurate, consistent, and usable results for developers building with Clutch.
An option to export production build as static HTML site
It would be great to have the ability to export production builds as static HTML, CSS, and JS files, especially for simple landing pages that don’t rely on CMS content, dynamic data, or APIs. For example, projects like basic marketing pages, brochure-style pages, or one-pagers where content is usually static and don’t require constant update or data fetching. This would allow us to host the site without a need for Node.js hosting or SSR capabilities. Since Clutch is powered by Next.js, having this functionality seems feasible: https://nextjs.org/docs/pages/guides/static-exports I hope this feature can be considered in a future release! :)
From WordPress & cPanel to Clutch, React & Next.js: A Beginner’s Guide to Building and Deploying a Website
I’ve been using Bricks Builder for years, and before that, Oxygen Builder. I’ve always worked via shared hosting, which has been sufficient for my clients who serve only local markets, not global ones. Now that I’ve discovered Clutch, and believe it may represent the future of web development, I’ve started diving into JavaScript, followed by React and Next.js. However, I’d really like to see a step-by-step video tutorial for people like me, those used to simply spinning up a WordPress site through cPanel, that explains how to adapt our workflow for Clutch. Here are my main questions: Where do we host the WordPress backend? I assume this can still be done on a shared hosting platform? For the frontend, we can host it via Clutch or alternatively export everything and deploy the files to a hosting provider that supports Node.js right? How do we deploy the frontend as beginners so that the site goes live? Since Clutch is a desktop app, is it always connected to both the frontend and backend? What happens if my computer crashes, does Clutch remember my last revision once I reinstall the app? More generally, I’d love a beginner-friendly tutorial that walks through the entire process, from start to finish, of building a simple site (with a blog and contact form), putting both the backend and frontend online, and maintaining it afterwards. How do we update the site from the backend? How do we edit or update it from the frontend? I’m eager to learn this new approach but would appreciate guidance tailored to someone coming from a traditional WordPress & cPanel background.
Auto Refresh WordPress Connected Site Cache
Auto Refresh builder when clearing WordPress connected site cache. That way, it reduces number of clicks to get new WordPress data to show up in Clutch.
Canceled
Bulk Import token/variables and generate color shades, tints and transparency levels
I’d love the ability to import my own design tokens/variables in one go, for example, via an Excel, Google Sheet or a better way, where I can group them by type. After importing into Clutch, I want to easily navigate between categories such as colors, spacing, shadows, radius, grid, etc. For colors specifically, I would only import the main static colors like primary, secondary, action, accent, base, white, black, light, and dark. Then, within the Clutch Builder, I’d like the option to automatically generate shades, tints, and transparency levels for each color.
Canceled
Figma to Clutch Importer
Figma to Clutch Importer: Design everything in Figma as usual, then import it directly into Clutch. From there, just make a few adjustments if needed. This approach can significantly speed up the entire workflow. Clients want to see a design early on, and that’s not going to change. Redoing the work in every builder is frustrating—but being able to import everything straight into your plugin would be a game changer.
Rename actions name in Contact form
It would be very nice if we could rename these REST to be able to easily differentiate between each one.
Shipped
JetEngine and Meta Box fields not appearing
After updating Clutch WP plugin to v2.0.0, custom fields created via JetEngine and Meta Box are no longer appearing in the Data to bind to.
Shipped
Post published date not present under item when looping over posts
Post published date is missing from the post item data. Please also consider providing post modified date.
Rich Text component's default HTML tag
We typically add paragraphs inside a Rich Text component. The current tag of span should be div by default. Also, it should have the tag property set by default. https://discord.com/channels/949340418229800990/1366998107396771890
Shipped
Update available notice and 1-click updating functionality for the WP plugin
Being able to update the WP plugin w/o having to upload over would be nice. https://anchor.host/using-github-to-self-host-updates-for-wordpress-plugins/ https://github.com/afragen/git-updater
Canceled
The ability to add custom CSS in the builder
A way to add both global sitewide and page-specific CSS in the builder would be handy.
Add SVH Units
SVH is similar to VH except on mobile (I believe specifically iPhones) where on an iPhone when you you load a section at 100vh it uses the entire browser browser app’s viewport height which results in part of the section behind hidden below the address bar that initially loads with a page before scrolling down. 100svh respects only the visible viewport and won’t load behind the address initial address bar.