The Full Editing Interface
Beyond the QuickEdit interface Serckit also provides a more complete Full Editing interface accessible through the 'Full Editor' link that is visible in the bar at the top of the page to be edited. This is also the interface accessible through the administrative site for Serckit (more on that later).
In addition to being able to click the various sections of text to activate them for editing (as with QuickEdit) the Full Editing Interface allows you to:
Change the page title
Just click it to enable editing. This text appears across the top of the browser window, in search engines and bookmarks. It is also used in navigation menus as well as (in most templates) being plastered across the top of the page itself. So choose something concise and descriptive with due consideration to all the contexts in which folks will try to make sense of the title.
Change the url
Urls need to be unique, and you should stick to lowercase letters and numbers--no spaces or funny business (underscores are fine though). A changed url will break any links to it (in Serckit or elsewhere) so in general urls for live pages should be left as is.
Make the Page Live
An interface for replacing the current live page with the contents of the dev page. Or for making it live for the first time.
Manage Forms, Browses, Catalog Links and more
Edit text in HTML mode
A link at the top of the green box allows you to toggle between the normal "richtext" view of the editing windows and an "html" view that may be handy for diagnosing strange formatting behavior. Only a small subset of html tags are allowed as described on the previous page.
Change Other Page Metadata
Below the text boxes there is a collapsed section where you can modify a number of other page settings. Normally the defaults are fine.
Add New Fields to a Page
On occasion it may be useful to add new fields to an existing page. The most common case is when you need to associate vocabularies or keywords with a page to support particular search behaviors. Note that in general new fields won't actually be visible on the new page unless the template already supports them.