I recently started to learn ASP.NET Model View Controller (MVC) . This is a very unique approach that is required for sites, I notice the potential with the help of dynamics . This will greatly improve the service.
But I see how overuse of dynamics can be bad, especially if you deviate from strongly typed model . So my question is this ...
I am creating a layout, but I would like the layout to be fluid . I want the design to be easily changing without affecting my logic. I know that you can create Master Pages and Master Content Pages , which can contain most of the layout for convenience. In addition, I will still have restrictions for my use.
Is there a way to change these Master Pages and Master Content Pages into true dynamic objects? Essentially, designer can use what you see, what you create, I create, which allows you to change the whole site?
My initial thought was to save to create a dynamic layout where each View referenced a database; no matter which of these variables would create the layout. But I'm not sure if this is the best approach?
Any suggestions or thoughts for a better approach?
Please, I am not going to start a discussion, but if people could show me the direction in which I can explore this implementation method, it will be very useful. That way I can find the best solution that will fit these projects for dynamic layout .
Update:
To give an idea of ββthis project, my company has several subsidiaries. These subsidiaries will use the application, but would like it to be specific to a particular company. To avoid excessive design mockups, I would like to abstract this part.
Thus, my logic will not be affected, but the software will be modular enough to meet all the needs of our subsidiaries without having to configure each of them or jeopardize the constructor that affects logic .
Thank you for your help.
Update:
To help clarify, the goal is to allow the User Interface be separate from the application. In a regular Windows Application I would use Inversion Of Control to help separate the interface and structure from the original logic.
This untied approach is useful, the goal is to separate the interface in this case, Razor Syntax , which will create the structure. If you have a website:
<html> <div id="Page-Container"> <div id="Header" /> <div id="Content" /> <div id="Footer" /> </div> </html>
This structure will be static, but in my case I would like it to be dynamic . Thus, my logic can be abstracted through the structure, but the designer can manipulate and modify the page layout , but he would like to.