Forum: Ruby on Rails Designing different registration processes

Announcement (2017-05-07): is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see and for other Rails- und Ruby-related community platforms.
eugenol (Guest)
on 2005-11-30 20:20
(Received via mailing list)

I am now migrating projects to RoR but I'm still wondering what's the
best issue for my case:

- There are 3 kinds of registrants; models are quite similar but not
enough then forms are different
- The registration process is long and split ed into 10 steps (means
at least 10 views).

What would you suggest as a Rails way to design this registration
process ? What would you store in the @session ? How to organize views
and controllers (one or three ? as many actions as registrations steps
?)  ?

Thank you for your suggestions
This topic is locked and can not be replied to.