Automatic page assembly systems allow you to focus your efforts on building content, not managing the logic of getting pages built, errors displayed, and form data transported. PageBlocks™ supports traditional URLs, extensionless URLs, and fully abstracted virtual URLs without mod_rewrite. Even with all these standardized tools, PB allows you to organize your apps just about however you want.
PageBlocks uses scripts to make changes to your database schema as you evolve your dev copy. Those scripts are then used to keep your beta and live copies in perfect sync. No more confusion. PageBlocks also knows which copy of a db to use based on whether it is running as dev, test, or live. No more production data loss because you forgot to edit a db name in you config code.
Among the toolkits that the PageBlocks framework offers, the central engine is an automated process for page assembly. This process begins with a page declaration, then uses a layout template to pull content into the page. As with any web page, content display is structured through regions of the page layout template. Each region is a unit of content called a page block. Once development gets underway, the page block tends to become the unit of code organization that pulls together the application's display and logic assets.
© 2002-2009, pageblocks.org