2. What is content staging anyway?

4. For security purposes, no editor access at all to live site

6. The default model is to edit on the production server

9. Replicating content from one server to multiple installations

10. Sending partial replicas of content (a subtree of the whole content, or filtered-out contents)

11. Facilitate integration with external systems

12. ...I'm sure you have more

14. Editors can view and pick change-events to be synced to remote server

17. Opening Pandora's box

19. All manipulations of eZ Publish content are possible - except emptying trashcan :-)

21. The same applies to sections definition, object states, etc...

22. Starting with a non-empty content tree to synchronize is not possible yet

23. Some datatypes are not fully supported (e.g. webshop-related ones)

24. And many more...

25. You are invited to play around with it and make sure the final version will fit your needs. Oh, and find bugs too

26. We want you

28. ggwebservices extension: http://projects.ez.no/ggwebservices/downloads

29. Source code

30. https://github.com/gggeek/ezcontentstaging

31. ggwebservices extension: http://projects.ez.no/ggwebservices

32. Specs for the REST API as implemented

33. https://github.com/gggeek/ezcontentstaging/blob/master/doc/specs.ods

34. Get in touch Thanks to eZ partner ALTI

35. [email_address] http://www.alti.com/

36. @gggeek