;content_preview_function: This function is called when a page is being editied and a user hits preview. it's mostly there for you to make any selections the user has made persistent during the preview phase.
;content_edit_function: When a user wants to edit content, this function is called. it allows you to generate data for any templates you need to fill in the edit page (more below).
;content_store_function: Here you can store the content data in your serice tables.
+;comment_store_function: Similar to content_store_function, this service is called after a comment object is completely stored.
;content_expunge_function: Make sure the data from your tables is removed when a user removes the content it belongs to.
;content_user_perms_function: Modify the user's permissions for a content object. Generally intended for extending permissions. But this gives access to the user's permission hash for manipulation in whichever way.
-;content_access_control: Verify user has permission to access content. intended use is to fatal out if not.
+;content_verify_access: Verify user has permission to access content. intended use is to fatal out if not.
!!! Templates
;content_edit_tab_tpl: This template is displayed as a seperate tab when a user is editing content. this is useful for services that might contain several lines of code and want to have their own section when a user edits a page. This template is only available when the user is editing data.