You have to implement custom data providers for all modules that you want to support Figaro. In the case of Generic Content for example, you have to inherit ContentProviderBase
class and implement all abstract methods. Then you have to configure your application to use the custom provider.
| <add name="Generic_Content" type="MyNamespace.CustomContentProvider, MyAssembly"/>
Unfortunately, documentation and examples on custom data provides is very scarce and since the work will be quite substantial, if you want to support all modules, we will have to help you with this initiative in iterative manner.
It might be worth waiting a few months for Sitefinity 4.0 for a few reasons:
The implementation of custom data providers is greatly simplified. The architecture is vastly improved. We are now constantly working on documentation in parallel with development, Sitefinity 4.0 APIs will be much better documented. Sitefinity 4.x API will not be directly backward compatible. Although we plan to provide wrappers around the new API to provide backward compatibility, this may prove to be quite challenging in certain areas.
Sitefinity 4.0 comes with its own build-in XML database engine. Although it was designed to serve Sitefinity's needs, you may find it quite convenient for general purpose storage as well. It supports transactions, optimistic locking, automatic object serialization / deserialization, LINQ. Sitefinity 4.0 will be capable of working without database while maintaining its full functionality.
If you decide to start with v3.6, please explain your goal and where you want to start from.
the Telerik team