# Noob: Help designing Architecture for custom form-builders

**URL:** <https://www.ruby-forum.com/t/noob-help-designing-architecture-for-custom-form-builders/123338>\
**Category:** Rails\
**Created:** [December 16, 2007, 6:42pm UTC](https://www.ruby-forum.com/t/noob-help-designing-architecture-for-custom-form-builders/123338 "2007-12-16T18:42:12Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![vin03](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/v/919ad9/32.png) [@vin03](https://www.ruby-forum.com/u/vin03)\
**Post date:** [December 16, 2007, 6:42pm UTC](https://www.ruby-forum.com/t/noob-help-designing-architecture-for-custom-form-builders/123338/1 "2007-12-16T18:42:12Z")

</div>

Hi,

As one of my personal projects for practice, I want to create a form  
builder application that is similar to what Wufoo is offering. However I  
could not figure out how I can build the equivalent in RoR and would  
appreciate some guidance on this issue. I’m a newbie to programming, so  
please pardon me if I’m too verbose in explaining my problem.

How would I go about designing the architecture? Should I create a model  
for my users, and a controller method that creates a new model for an  
individual user when they have saved their forms? The problem I have  
trouble grasping with, is that unlike traditional applications where we  
would normally predefine the column values for each model, it appears  
that each user will have their own separate database for **each**   
form they create after they click on the save button. Thus wouldn’t I  
need to create a controller under the user model, in order to create a  
new model for each new form that the user create?

Seeking your advice on this issue. Please let me know if any of my  
explanations is not clear. 🙂