Timeline for Implement hybrid approach in project by using both tridion templating(DWT) and DD4T
Current License: CC BY-SA 3.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 30, 2014 at 8:27 | comment | added | Neil | We did consider a hybrid MVC approach whereby we could use DWTs to publish views and then use DD4T templates for dynamic stuff. We got as far as fancy routing to determine "static" from "dynamic" before we canned it and went all-out DD4T for a much more straight-forward codebase. Theres no doubt you need to think a little more carefully about your schema design with DD4T and the impact on hardware (which is a normla consideration when moving from static to dynamic anyway) but I'd recommend keeping it simple and embracing DD4T fully over hybrid. | |
| May 29, 2014 at 19:56 | history | tweeted | twitter.com/#!/StackTridion/status/472104225732698112 | ||
| May 29, 2014 at 16:21 | comment | added | Rob Stevenson-Leggett | The main con of a hybrid approach is the maintainance of 2 different delivery mechanisms. | |
| May 29, 2014 at 14:33 | answer | added | johnwinter | timeline score: 2 | |
| May 29, 2014 at 14:23 | comment | added | Nash | @Ant P: I understand you point but again need to know the cons and pons if I go for the hybrid approach | |
| May 29, 2014 at 14:02 | comment | added | Ant P | I'd say that using DD4T just for DCPs is overkill. The framework is primarily built around the idea of rendering pages dynamically. If you have a requirement to use DD4T you're better off committing to it and using it for your static content. | |
| May 29, 2014 at 13:30 | comment | added | Nash | @Ant P: But we have to use DD4T for Development as this is recommended from client so we don't have option to not use DD4T, but we are thinking of using DWT for static pages so that there would be no burden of fetching data for static pages from broker(Just to avoid broker hit for static pages) | |
| May 29, 2014 at 13:27 | comment | added | Nash | Static pages which will published on file system and Dynamic pages(Dynamic CP) are those which will fetched data from the broker. ex. For satatic pages like contact us pages would be directly published to file system where as product page will fetched data from broker database where all the products have already published | |
| May 29, 2014 at 13:22 | comment | added | Ant P | You don't need DD4T to serve DCPs from the broker - DD4T allows you to serve (functionally) static pages from the broker. If you're planning on serving your static pages from the filesystem, you don't need DD4T at all. | |
| May 29, 2014 at 12:59 | comment | added | Ant P | Also, from a configuration and architecture perspective, this question is very similar (and may be a duplicate depending on what you're actually asking): tridion.stackexchange.com/questions/5693/… | |
| May 29, 2014 at 12:58 | comment | added | Ant P | As Raimond says, as far as Tridion is concerned, DD4T pages are static pages. If you have dynamic content that is a separate issue from DD4T vs. DWT. Can you provide some examples of what content you're thinking of using DD4T for vs what you're thinking of using DWT for? | |
| May 29, 2014 at 12:50 | comment | added | Raimond | Can you elaborate a bit on what you mean with 'static' pages and 'dynamic' pages? From a Tridion CM perspective, both are just Pages. Where do you use both for ? | |
| May 29, 2014 at 12:49 | history | edited | Raimond | CC BY-SA 3.0 |
Tridion 2103 is sooo way in the future
|
| May 29, 2014 at 12:46 | history | asked | Nash | CC BY-SA 3.0 |