Problems
Lack of correlation to "Blocks"
Looking at the website alone, after identifying that a block should be edited, it is difficult to find where that block is located without knowing its name. Usually, the major piece of information that the user might have as to where the block might be located is the name of the page. As a result, the user might turn to the "Manage Pages" section to find the block. Unfortunately, while the "Edit Block" page does indicate what pages the block will appear on, the "Edit Page" screen does not indicate what blocks will appear on that page.
Lack of connection between the real world and the system
When working with pieces of HTML, after time, it becomes clear that HTML is the organization of blocks of elements. To a user unfamiliar with HTML, however, it is difficult to see how a webpage's layout can be split into a series of blocks.
Lack of encapsulation
While it may be useful for a developer to easily place a piece of PHP
into the site using Blocks, the content-manager does not need to see this.
It would offer less clutter if these two aspects were more clearly separated
in the "Manage Blocks" interface, so that the content-manager could focus
on content-oriented blocks while the developer could focus on code-related
blocks, rather than presenting every block in the website in a single list.
Lack of images where needed
In the "Edit Block" page, the user can choose where the block's location will
be on the page. It would be useful to have a preview of where it will appear,
rather than using words such as "top" and "verytop" to describe the location.