This post was originally published by the Ektron Community Blogs here.
As any of my developer brethren will tell you, I’m a big proponent of Ektron’s Smart Forms. In our world, they’re a great way to structure content, to make dictionary objects for storing things like settings, and to store more data in a defined way than is natively available in the Ektron Workarea. I like to call them a database inside the database.
But this is geared more towards marketers and decision-makers, those that use what we developers do. So you might not be familiar with what a Smart Form is or why it’s a good idea to use it. Hopefully after this, you’ll not only understand it, but if your application isn’t making use of the concept, you’ll convince your development team to look into it.