sifbuilder.com is the site of sifbuilder, a framework and open source program that enables the declarative definition and automatic generation of web sites. The site is functionally described here and has been automatically generated with one single instruction.
Once I had a love and it was a gas
Soon turned out had a heart of glass
Seemed like the real thing, only to find
Mucho mistrust, love's gone behind
Once I had a love and it was divine
Soon found out I was losing my mind
It seemed like the real thing but I was so blind
Mucho mistrust, love's gone behind
In between
What I find is pleasing and I'm feeling fine
Love is so confusing there's no peace of mind
If I fear I'm losing you it's just no good
You teasing like you do
Once I had a love and it was a gas
Soon turned out had a heart of glass
Seemed like the real thing, only to find
Mucho mistrust, love's gone behind
Once I had a love and it was divine
Soon found out I was losing my mind
It seemed like the real thing but I was so blind
Mucho mistrust, love's gone behind
Lost inside
Adorable illusion and I cannot hide
I'm the one you're using, please don't push me aside
We could've made it cruising, yeah
Yeah, riding high on love's true bluish light
Once I had a love and it was a gas
Soon turned out I had a heart of glass
Seemed like the real thing only to find
Mucho mistrust, love's gone behind
<h2 class="title" style="clear: both">sifbuilder interaction with the cores</h2>
Whenever sifbuilder installs a component, it follows the following actions:
Process. Manage package versions, dependencies, and conflicts
Control. Control the version of the site package (core or module) to be installed. This is taken from the sip installation package. Check whether that package is already installed in the site and get the installed version
Transpose. Download and explode the site package source if not available
Transfer. Copy the package files from the packages repository to the site (this may remove information of the pre-update status
Config. Configure the site parameters. Done normally only with the installation of the core
Install or Upgrade the package as required. Installation is dependent on the type of package. Installation of a module usually includes initialization and activation. Installation of a theme may imply activation of that theme
Build. When sifbuilder runs against a site definition template, the previous actions are followed by configuration of panels and blocks, setting of system variables and permission, and creation of content.
These actions are carried out by sifbuilder in a single session relying as much as possible on the interfaces offered by the site core and its modules. In ideal conditions, sifbuilder should neither modify the code of the core nor import code from it.
The easiness with which sifbuilder may interact with a WCM system is determined by three features of the cores:
Exposure. The exposure refers to the functionality offered by the core and components to an external application. It is dependant on an API. When the level of exposure is low, extending or modifying the behavior of the application is done by modifying the code and not by adding functional components to a repository
Segmentation. The segmentation refers to the separation between the presentation and the logic code. When the level of segmentation is low, calls to a function may generate undesired output intended for user interaction
Contextualization. Contextualization refers to the possibility of entering the code once the global status has evolved. Usually, wcm systems are designed to allow a single package action in a session. With a low level of contextualization, installing various themes or upgrading a module is difficult. This may be provoked by the use of static variables, include instead of include_once, or unbundled code in files
Comments