Evolution custom manager page or frame

I’m new to modx. I inherited a website from a previous webmaster. The site is an Evolution 1.0.4

I’ve seen a few postings about adding a custom page in modx revolution, is there a way to add a custom page in Evolution?

If not, as an alternative, can I add an iframe to an existing page?

Evo has modules. They are applications that can be loaded into the main working frame.

http://rtfm.modx.com/display/Evo1/Modules
http://sottwell.com/create-module.html

thanks sotwell for the quick reply. I’m aware of the concept of modules, and you’re links are a great start to develop one, however, if I developed a module, how do I add it to the manager section?

Perhaps the way I’m asking the question is not typical "Modx language", but what I’m trying to get at is adding a "page" in the manager section, or if not possible, adding a "section" or an iframe to an existing manager "page".

I am a novice when it comes to Modx, but I’m a seasoned developer.

Again, that’s exactly what modules are. Take a look at the Modules main menu submenus. You’ll see one for managing modules, and at least one existing module, DocManager. Use the Manage Modules submenu to create a new module, just as snippets are created, or to edit an existing module. Once you’ve added your module, you’ll need to refresh the top menu frame (FF allows this, or just refresh the whole manager) to have your new module appear in the submenu bar alongside the DocManager module. That’s my fault; when I designed that menu I didn’t think to also modify the save_module and delete_module processors to have the main menu automatically refresh on adding a new module or deleting a module (something like the refresh when saving the Configuration, except only refreshing the top menu frame).

If you look at the manager/index.php file, you’ll see that almost every action is simply including the appropriate .php file from manager/actions. The script for running a module (a=112) is actually a processor, manager/processors/execute_module.processor.php and it pretty much treats a module’s content the same as a snippet’s content, loading any configuration parameters into the GLOBAL array and running the content through the eval() function. You can use a mix of html and <?php...?> tags if you like (as you can with snippets). The module’s output appears in the "main" (right) frame.

Usually if I make a custom module that will be used a lot, I’ll customize the manager’s Welcome page to have a link to it along with the other icons/links.