Notice the two areas on the page that become outlined with a dotted border when the editor is on?
Those are editblocks, the only areas on the page that are editable. Place your cursor in one of the editblocks and Start Editing!
Using editblocks like this page is optional. If no editblocks exits the page is editable from open body tag to close body tag. If a page contains one or more editblocks, only the editblocks on a page get turned on for editing.
Free yourself from those tedious, distracting maintenance chores! It's hard enough to get site owners to pay you what you're worth for design, it's even harder to get them to pay you design value to do that mundane data-entry. Give your client the thrill of doing those chores with a wysiwyg!!!
EditWrxLite is a Web 2.0 application using state-of-the-art widgets instead of pop-up windows. Widgets remain on top of the page and can even be docked to one side and remain available after saving or reloading the page. You can even navigate to and edit another page without closing the Widgets. Full use of EditWrxLite features require either Explorer7+, Firefox3+, Safari3+ or Chrome3+ browsers.
The designer/webmaster can determine what pages and what parts of pages each user can edit, and what tools will be available to each user. Each user is assigned a folder for their images which can be a unique folder for that user or a common folder shared by other users.
Editblocks are easy to set up on a page and will validate as W3C compliant. Just enclose editable content in a tag such as <DIV class="editblock-one"> editable content </div><!-- editblock-one -->. You can have multiple editblocks on a page.
If you use SSI/PHP/ASP includes on your site to include common headers, navigation, footers, etc. you can enclose the include tags in an includeblock. Edits inside of an includeblock are written to the include file, not to the webpage you are editing. <DIV class="includeblock-/incs/header.inc"> <!--#include virtual="/incs/header.inc" --> </div> would direct EditWrxLite to find the /incs/header.inc file and write that block's edits to that file instead of to the page's file.