Examples Templates Store Pricing Docs Turbo CSS Blog 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

Deprecating the .Class file


The .Class file is being deprecated. It will remain functional for an unspecified time but will be removed in future releases.

It’s purpose was to allow applications to document themselves. Imagine an application was accessible via the domain gallery.com. To allow users to quickly look up the apps documentation, the .Class file was introduced to hold actual application files. This way the file at gallery.com was up to the developer to contain any relevant documentation.

We still need both the documentation and the application files, but we are reversing the solution. Application files will live directly within gallery.com and documentation files will be moved to a subpage instead, namely the file .Docs. Visitors going to our imaginary gallery.com will be redirected to gallery.com/.Docs.


The .Class file is used way more frequently than the app documentation and so adds an unnecessary mental overhead. It now seems obvious that the file layout should be optimized for the application files over the documentation to simplify learning Boomla.

Additionally, Boomla is soon landing support for extending and configuring applications via the file type chain. The mental overhead of using and learning the .Class would significantly increase. Let’s keep things simple.

Migration guide

  • Update all your apps.

  • Move any documentation from the app file, like gallery.com to the .Docs file.

  • Move all files from the .Class file directly into the app file. For example, the file gallery.com/.Class/.Inline has to be moved to gallery.com/.Inline.

  • Set the app file’s type to app-1.

  • Remove the .Class file.

Dynamic ..Class file

The dynamic ..Class file will keep pointing to the .Class file if it exists. If it doesn’t exist, it will point to the app file instead.



you can follow me on Twitter