Filesystem Tree

Files, Directories

The Boomla filesystem is a full tree. Full in the sense that all files may have children and store data at the same time. So in Boomla, files and directories are the same thing, at the same time.

Properties, Attributes

Files have properties (system defined) and attributes (user defined). These are discussed in the Filesystem Nodes section as they are not related to the tree.


Children of a file are stored in buckets. A bucket is just a group that helps sorting the children in separate groups. Buckets are identified with BucketIds, numbers from the range 0-255.

Bucket 0 is a special hidden bucket, that shall be used for system files and applications, anything not relevant to end users.

Hidden files

There is no such rule that files with names starting with a . are hidden. The only rule is that files in bucket 0 are hidden.

The Boomla Filesystem is type safe, in that it has a concept of what files are safe to be placed where. See file placement and .Accept rules for more details.


Files stored in order. There is no order_ID attribute, instead you can move around files relative to others.


Like traditional filesystems support links, so does Boomla. One key difference is that Boomla files have a special property called link. Edit the link property to create/modify a links.


Any file that contains a .Page file directly, or on its type chain, is considered a page. For example, that’s useful when generating a menu.

Alternatively, it is said that a file is a page if it implements the .Page interface.


Any file that contains a .Inline file directly or on its type chain, is considered a content. For example, that’s useful when displaying contents.

Alternatively, we can say that contents implement the .Inline interface.