Integration
The basic integration approach is outlined below. We're also hard at work on our documentation. 
FTP
With FTP integration, changes to your content will be published via FTP, and embedded directly into the files on your server.
To mark up regions of your site that you want to make editable, add a css class as shown below:
<div id="firstArea" class="cms-editable">
PageLime will replace everything in this area.
</div>
You can also mark up links, images and titles.
<h1 id="heading" class="cms-editable">
PageLime will replace everything in this area.
</h1>
<img id="image"
src="/images/test.jpg"
width="200"
height="100"
class="cms-editable" />
<a id="link" href="link-target.html" class="cms-editable">
PageLime will replace this text.
And update the link HREF attribute.
</a>
The PageLime publishing engine will search your source code for the editable classes, and replace content inside those areas with the updated content from PageLime.
FTP-XML
FTP-XML is a bit more advanced type of integration. Here, instead of publishing content into your files, PageLime publishes XML files that can be read by an API file we provide. For example:
<h1 id="xmlHeading" class="cms-editable">
<?php pageLimeHtml('xmlHeading'); ?>
</h1>
<div id="xmlEditableArea" class="cms-editable">
<?php pageLimeHtml('xmlEditableArea'); ?>
</div>
<img id="xmlImage"
src="<?php pageLimeAttribute('xmlImage','src'); ?>"
width="200"
height="100"
class="cms-editable" />
<a id="xmlLink"
href="<?php pageLimeAttribute('xmlLink','href'); ?>"
class="cms-editable">
here's an editable link.
</a>
What PageLime does is publishes an XML file to ~/PageLime/XML/1.xml (where 1 is the page id), and then pulls in this data to your page.
With this approach, your code is seperate from your content, while you can still continue to use PageLime's intuitive interface, and decoupled content management features.
