ExamplesTemplatesStorePricingDocsTurbo CSSBlogNamed bucketsTurbo CSS is Tailwind CSS on steroidsIntroducing Turbo CSS, the most advanced web-design languageCalculate how much storage you useBetter login systemCollaboration settingsFilesystem and Database are not cutting the problem space rightWhat I'm working on64bit File node IDsNew how-to videosCreating buttons gets easierIntroducing reusable componentsHTTPS by defaultIntroducing the Boomla ThemeCDN for faster pageloadsWrite your own website builder on top of BoomlaOn On compositionShared admin accessA fresh config editorBuilding a multi-purpose themeA filesystem to replace your CMSNew file link type: scopeMobile editing supportInline file wrapping changedPackage sandboxingNew PHP-like JavaScript engine [sjs-4e]Send emails to the website ownerNew JavaScript engine [sjs-4]A better editing experienceNew email service providerGlossary and other changesNew panel changesImproved registration flowBoomla goes multiplayerUsing local dev toolsWhy Boomla doesn't need GitFile PanelLet's build a communityAutomatic updatesImproved sjs-3 APINew FrontendCSS modulesWork offline with BoomlaFaster page loads via cachingDrag & drop superchargedSupporting CommonJS modules Paranoid about loosing dataIDE usability improvementsSimple App install flowMeetups in BudapestGoodbye broken linksFlow control from user spaceCustomizing appsContextmenu support for appsDeprecating the .Class fileHello ChangelogEmbedding 3rd party pluginsIntroducing ToolsInstalling apps just got amazingPublic betaHost on our serversSimple deploy with push/pullVersion Control for the Web350M files on a 1TB disk2 weeks in review
Control Panel

Contextmenu support for apps


I’m excited to announce that Boomla landed support for apps to enlist custom Contextmenu entries.

Here is how it looks like:



Clicking the entry, you land on a settings page fully defined by the app developer.




BIG Deal

This, is a big deal. Until now, Boomla was focused on creating simple document-like websites without much support for rich building blocks that have their own configuration pages. We could say that Boomla support for functionality that naturally belonged to admin pages. But admin pages are so unnatural.

The workflow of an end-user looks like this:

  • on your website, you find what you want to change,

  • go to the admin area,

  • again, find where you need to change what you need to change,

  • then you make the change.

Boomla simplifies this workflow by giving you a quick-link to where you want to go. Want to change the video player settings or select a different video? Just click the contextmenu entry for the video settings, and you are ready to make those changes.

For developers, it’s just creating 2 files, and your application will have full control of the entire browser window - except for the toolbar. Now you can write powerful applications like an image editor without being constrained into a box on the admin page.

If you are a developer, here is how to register contextmenu entries.

See the app youtube.boomla.net as an example.


ps: follow me on Twitter