Boomla works like a class based object-oriented programming language (OOP), except it is a website builder.
Boomla pages, contents and in fact every Boomla file works like an OOP object. Applications define how these files shall behave, much like classes define how objects shall behave in object-oriented programming languages.
Each Boomla file has a file type which specifies the path of its application. Note that the Boomla platform has no concept of file extensions. File types are used instead, which is a property of the file, not visible in the file name.
Applications are files as well. Much like classes implement methods in
object-oriented programming languages, Boomla apps implement methods by
containing files with given file names. For example, to respond to requests, an
app has to contain a file named
Say, your website contains a file
/hello.html of type
/hello-page. When a
visitor goes to
/hello-page/.Request file is executed and
the generated output served to the visitor.
Currently the following methods are supported:
.Request- called when a HTTP request is made agains a file,
.Inline- called when a file is to be inlined in a HTML page.
To elaborate on
.Inline, this the method used most. Any content, menu, etc. needs to at least implement the
.Inline method for them to be shown on a web page.