Im doing a website with a structure much like the Standard Farao Umbraco website. The site structure contains different doc types (story pages, text pages, cases etc ...)
One of the page types "Story Page" contains multiple frames. Each frame is a part of the story and can vary in content and behaviour. Also sometimes a frame contains multiple frames sideways before continuing downwards. Stories can contain up to 15 frames. Frames are not required to be reusable.
I've tested a lot and are fully confident with creating property editors for the grid or even macros maybe.
Also - a huge concern is that all the definition of a grid data type is stored in db - ie not possible? to copy to another datatype (i will need multiple). (why why why is it not filebased..... )
Would you use the grid?
Anyone been doing anything crazy huge with the grid and could share some experience - do's and donts?
I would add more to your consideration that you may/may not have thought of yet.
First, is the customer "ready" for using this kind of tool, i have done a few with our homegrown grid and seen 2 customers just mess it up even if they were limited in actions. Basicly because they dont have a graphical eye at all.
Second does the customer have enough content for utilizing the power of the grid ?
The copiying part shouldnt be that rough, use usync/courier/(there is a third option aswell, package cant remember name).
To Grid or not to Grid (implementation planning)
Hi all,
Im doing a website with a structure much like the Standard Farao Umbraco website. The site structure contains different doc types (story pages, text pages, cases etc ...)
One of the page types "Story Page" contains multiple frames. Each frame is a part of the story and can vary in content and behaviour. Also sometimes a frame contains multiple frames sideways before continuing downwards. Stories can contain up to 15 frames. Frames are not required to be reusable.
I've tested a lot and are fully confident with creating property editors for the grid or even macros maybe.
Also - a huge concern is that all the definition of a grid data type is stored in db - ie not possible? to copy to another datatype (i will need multiple). (why why why is it not filebased..... )
Would you use the grid?
Anyone been doing anything crazy huge with the grid and could share some experience - do's and donts?
Certainly would like to avoid https://www.youtube.com/watch?v=Z7JSodkbrgs&feature=youtu.be&t=13m51s
best
Jesper
ps. Im used to deal with stuff like this by creating sub content in the structure but I really would like to avoid it if possible.
I would add more to your consideration that you may/may not have thought of yet.
First, is the customer "ready" for using this kind of tool, i have done a few with our homegrown grid and seen 2 customers just mess it up even if they were limited in actions. Basicly because they dont have a graphical eye at all.
Second does the customer have enough content for utilizing the power of the grid ?
The copiying part shouldnt be that rough, use usync/courier/(there is a third option aswell, package cant remember name).
But yeah i would use the grid.
You might want to be aware of this issue: http://issues.umbraco.org/issue/U4-6102
Basically, right now you cannot rename any layouts in the Grid after you have added content, or the content will vanish.
Thanks Rasmus. Good points. i just showed the grid to client and they gave me this feedback
is working on a reply...