While trying to import templates, it imports the whole one. We need options to import single pages out of the templates. Maybe sometimes headers and footers separately.

I have followed the process to upgrade to Kirki. It look like there is no search for the pages list and the list's text is so small. It's a bit hard to find a page quickly.

It would be great to have AI integration within Kirki that allows users to create and update pages using natural language prompts. For example, a user could describe the page they want, and the AI would generate the layout, content, and design elements automatically. It could also help modify existing pages based on prompts, making page creation and editing much faster and more user friendly.

It would be great being able to create a new post inside a collection on the go from our mobile phone.

Please in beta version add the lock layer feature so some layers remain undisturbed

I notice in this new beta, you disabled the import font feature. Please put it back it is very useful

Hey team Droip, Could you record a tutorial on how to start building a website from scratch. There's a lot of videos about the pre-build pages and templates. But starting from scratch I can't seem to really find.

Please enable to be able to move items in a wrap position in the layers and in the canvas with arrows keys

We can not access the variables colors when editing

It would be very helpful if Content Manager Collections could appear directly inside the WordPress admin menu, working similarly to a native content section. Currently, even for simple recurring content such as testimonials, team members, or case studies, clients must open the Droip visual editor to add new items, which creates unnecessary friction in day to day use. The suggestion is to allow each Collection to optionally be managed from the WP Admin, automatically creating its own menu entry where users can add, edit, and delete items through a standard WordPress style listing and form interface, while the layout remains fully controlled by Droip templates. This way clients can manage content without accessing the builder, reducing the risk of layout changes, simplifying training, and making the workflow closer to the native WordPress experience expected by agencies and site owners.

Please add an “Edit with Droip” action button in the WordPress admin bar when viewing a page on the frontend. Currently, users must go to WP Admin → Pages → Edit with Droip each time, which slows down the workflow. A direct admin bar button would allow one-click access to the Droip editor and make page editing much faster and more convenient.

Hi Droip Team, I would like to submit a feature request to improve how the Droip Editor handles the loading of Collections, especially in environments with strict concurrency limits (common in shared or managed hosting). 1. Sequential / Batched Loading (Throttling): Currently, the editor appears to fire a burst of simultaneous AJAX requests to fetch collection items. In environments with limited max_user_connections, this leads to 'Database Connection Errors.' Requested Feature: Implement an option or default behaviour to throttle these requests (e.g., loading in batches of 5 or 10, or moving to the next item only after the previous one confirms). 2. Improved Error Handling & Retry Logic: When a connection fails, the editor currently handles the error poorly, sometimes resulting in mangled URLs in the console. Requested Feature: Implement a Retry Mechanism. If an item fails to load due to a 500 or database error, the editor should wait 1–2 seconds and try again up to 3 times before displaying a 'Resource Busy' warning. 3. Graceful UI Feedback: Instead of a blank state or a console crash, the 'Collections' element should show a loading progress bar or specific feedback (e.g., 'Loading 15/100 items...') to the user. These improvements would make Droip significantly more stable for the large portion of the WordPress community using standard hosting environments. Thanks a lot for your consideration.

Description: Expand the Video Element dynamic mapping capabilities to support URL strings from Content Manager Collections, in addition to the current Media Library selection. The Problem: Currently, the Video Element in Droip is excellent because it allows for both hosted files and external URLs (YouTube/Vimeo). However, when switching to Dynamic Content mode within a Collection, the element only permits mapping to "Video" type fields (which are restricted to the WordPress Media Library). This prevents us from using external hosting for dynamic items, forcing high server load and suboptimal SEO/Performance for video-heavy Collections. Proposed Solution: Allow the Video Element's "Source URL" field to be mapped to a Text or URL field within a Droip Collection. Use Case / Benefit: Performance: Enables the use of CDN-hosted or third-party videos (Vimeo/YouTube) within dynamic lists. Workflow: Allows users to manage video links via CSV imports or external API syncs without needing to upload every file to the WordPress dashboard. Consistency: Brings the dynamic functionality of the Video Element in line with the Static functionality. Requested Action: Please consider adding "URL mapping" to the Video Element's dynamic settings in an upcoming update.

I would like to suggest the creation of an accordion component, similar to the tabs feature currently available in Droip. At the moment, there is a dropdown option, but it does not feel as functional or intuitive as an accordion, especially in terms of content organization and usability.

It would be grat to be able to open other themes and copy specific sections.

Currently, each element has an Interactions tab where animations and behaviors can be configured. The suggestion is to allow copying an interaction from one element to another, making it easier to reuse existing animations. Additionally, it would be very useful to be able to save interactions as templates or presets. This way, when creating a new interaction, we could select a previously configured model instead of rebuilding everything from scratch. This would significantly improve productivity, consistency, and workflow efficiency, especially in larger projects or those with repeated animations.

It would be very useful to have global settings for commonly used elements, such as: Default fonts for headings, text, and other typography elements Global body background styles Standard styles automatically applied when creating new elements This would streamline the design process, ensure visual consistency across projects, and significantly improve productivity, especially when working on larger or recurring projects.

It will be important to add a feature that enables us to lock in the layers. Especially when handing over the Site to client.

Currently, Droip Builder outputs variables in CSS using auto-generated identifiers such as var(--dp8cvp5o), which makes the code harder to read, debug, and maintain. It would be highly beneficial if variables were displayed using their original, human-readable names as defined in the Variable Manager (e.g. var(--grey-900)), aligning the output with standard CSS practices and significantly improving developer experience, collaboration, and long-term maintainability of exported code.

course card