Forum

Keith,

I think I would start by organizing your project like this:

Data Layer

• Contact Model/Repository
• Event Model/Repository
• Registration Model/Repository

The contacttype and eventtype data can be probably rolled into the contact and event models

Service Layer

• ContactController: create, get, list, update, etc
• EventController: create, get, list, update, etc
• RegistrationController: create, get

Angular Modules

• contact-app.js: contact module, contact controller
• event-app.js: event module, event controller
• registration-app.js: registration module, registration controller
• dnnservice-factory.js: just the dnnServiceClient factory from my item-app that is shared by above 3 controllers.

For the views, you could either research how to use the MVC partials in Angular to have a true single page application that runs from a single module view (.ascx).  But it may not be necessary if these module views are very distinct and will likely need to be actual separate module definitions or .ascx module views.  You could create 3 module views: contact.ascx, event.ascx, and registration.ascx and isolate their angular module/controller to work with that view to do list/create/update/delete like in my Item example.