Examples Templates Store Pricing Docs Turbo CSS Blog Boomla WishList Introducing Turbo UI Named buckets Turbo CSS is Tailwind CSS on steroids Introducing Turbo CSS, the most advanced web-design language Calculate how much storage you use Better login system Collaboration settings Filesystem and Database are not cutting the problem space right What I'm working on 64bit File node IDs New how-to videos Creating buttons gets easier Introducing reusable components HTTPS by default Introducing the Boomla Theme CDN for faster pageloads Write your own website builder on top of Boomla On On composition Shared admin access A fresh config editor Building a multi-purpose theme A filesystem to replace your CMS New file link type: scope Mobile editing support Inline file wrapping changed Package sandboxing New PHP-like JavaScript engine [sjs-4e] Send emails to the website owner New JavaScript engine [sjs-4] A better editing experience New email service provider Glossary and other changes New panel changes Improved registration flow Boomla goes multiplayer Using local dev tools Why Boomla doesn't need Git File Panel Let's build a community Automatic updates Improved sjs-3 API New Frontend CSS modules Work offline with Boomla Faster page loads via caching Drag & drop supercharged Supporting CommonJS modules  Paranoid about loosing data IDE usability improvements Simple App install flow Meetups in Budapest Goodbye broken links Flow control from user space Customizing apps Contextmenu support for apps Deprecating the .Class file Hello Changelog Embedding 3rd party plugins Introducing Tools Installing apps just got amazing Public beta Host on our servers Simple deploy with push/pull Version Control for the Web 350M files on a 1TB disk 2 weeks in review
Control Panel

Drag & drop supercharged


When it comes to usability, the biggest selling point of Boomla is that you can play lego with the files. Just drag some text blocks onto your page, change the texts, add a gallery, upload some images and you are done. Except it didn’t happen that way.

I want to thank all of you who keep providing amazing feedback. What I learned is that users are dropping things everywhere. While it is obvious for me that a gallery can only contain images, users do end up dropping everything in there. Dropping a text in another text also doesn’t make sense. At least, not how those applications were programmed.

It turns out we would all benefit from a helping hand: if we could only drop things where they would make sense.



With the release of v0.6.0, Boomla only lets you drop files where they are accepted.

When dropping a file, some of the drop zones will turn red. It means the dragged file can’t be dropped there. If all drop directions (before, in, after) relative to a file are invalid, it won’t react as droppable at all. If at least one direction is valid, it will show up as blue, all the other drop directions will react as red. So, if you see a red drop-zone, you can tell that another drop direction is valid on the same target.

For developers

See the .Accept file docs.

In the IDE, you will see hints only. If you shouldn’t drop a file there, the drop highlighter will turn red, but you will be able to do the drop nevertheless.


you can follow me on Twitter