Maybe, so I'll try to explain better. To be able to support users without _javascript_, we have essentially two choices:
- Output the complete form initially, then use _javascript_ to hide stuff and to add a link to show the rest.
- Output the small form initially, with a link to a separate page with the full form, and use _javascript_ to change the link to use a _javascript_ function instead of going to a different page.
I think the first version is the least amount of work, since it doesn't require a separate page which is essentially useless for _javascript_-enabled clients. Besides, it's easier to hide already downloaded markup than to fetch new.
Using the second solution, we'd also have to use a button instead of a link to change forms (in order to be able to save the data before loading the other form), and this makes for an inconsistent interaction model.
The advantage of the second solution, of course, is that users without _javascript_ also see the small form initially.
In conclusion, I think we should use the second solution for the registration forms (more likely to get more registrants, but more work), and skip the work for the other forms until we have some spare time.