I have a grid field for recipe ingredients that contains 3 columns:
US Measurement | Ingredients | Metric Measurement
Some more complicated recipes benefits from grouping the ingredients up into components with headings like:
Dough
Ingredient 1
Ingredient 2
Ingredient 3
Filling
Ingredient 1
Ingredient 2
Ingredient 3
I thought about adding a column that you would specify which component the ingredient belonged to in terms of a number (1,2,3) etc. and that would at least allow me some formatting options in the templates. However, is there a way I get a heading (dough, filling etc.) in their efficiently since it would be user entered and its not standardized enough to have a dropdown with pre-determined options?
I want to keep it all as a single grid field, if possible.
Alright… no input. Could anyone tell me about performance and storage issues with too many grid fields? I’ve usually only used one or two small grid fields. Planning this site, it’s possible there would be at least 4 grid fields comprising an entry, as follows:
Ingredients Component 1 (3 cols) US Measurement | Ingredients | Metric Measurement
Ingredients Component 2 (3 cols) US Measurement | Ingredients | Metric Measurement
Time (8 cols) Prep H | Prep M | Cook H | Cook M | Inactive H | Inactive M |Total H | Total M
Gallery Grid Field (3 cols) Image | Caption | Credit
We will be employing a few caching techniques, but I am not familiar enough with native grid to know if I am looking at performance issues as this scales. I know I’ve been burned before with a couple complex Matrix fields, especially as the site scaled. So I am a little apprehensive.
ANY input would be appreciated.
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.