The idea implemented for now is that at any save (this is configurable) the correspondent "action" will be "transmitted" in the repository (only if if this is in a project with a path name for the file that contains jcr_root to be precise).
The "actions" implemented for now are:
- create a new file: the file is created also in the repository (if the file is not empty, is a bug)
- change the content of a file: the file is modified in the repository
- delete a file: the file is deleted in the repository
The trigger is the save action in Eclipse.
At the moment there is not support for any jcr type other than nt:file (but this is going to improve).
Another important thing to highlight for the moment is the way this information is "transmitted" from the file system to the repository.
Slingclipse uses Declarative Service and the implemented solution uses HTTP for now (org.apache.sling.slingclipse.http bundle).
Should somebody else would like to use some other way to achieve the same result is enough to create another bundle implementing the api contained in the org.apache.sling.slingclipse.api bundle,
I would try to create some basic documentation somewhere in the wiki soon