Michael: We rely mostly on experiences that people have (*when* we hear back from them) about the good things and the bad things to expand documentation like that. It's hard for me to write about it when I understand Refinery better than anyone and so don't hit many problems myself ;)
As a duther note, If any of the documentation is incorrect there is a link to "Edit this guide on Github" where you can fork/edit/pull request all from GitHub (and we welcome all contributions to improve our documentation!). Hope you have a good experience, Dmytrii (but if you have problems then please let us know how we can improve). Also be sure to search for others' posts about devise on our Google group http://groups.google.com/group/refinery-cms/search?q=devise and there's also a rather exhaustive guide based on one developer's experiences here: http://refinerycms.com/guides/attaching-refinery-cms-as-part-of-a-larger-rails-devise-application Cheers, Phil -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en.
