For those wondering about Custom Tables. Let's say you're doing a webcomic, and each chapter has 50 images as fields, every chapter you add will add 50 entries to your metatable, so if you publish 100 chapters you'll end up with 5,000 entries in the metatable (which will affect the query speed). But with Custom Tables those 100 chapters will only create 100 entries in the metatable, and the 50 fields will be stored separately. So it's useful from a performance perspective for large projects where you will have a lot of custom posts with a lot of fields.
Always wanted to get started with CPTs, so looking forward to the rest of the series. That said, some feedback: the video starts off nicely and informative explaining the basic terminology and such, but afterwards you seem to rush through the rest of the setup process. Since this is titled a beginners guide, I think you need to remember that throughout the video creation process and make it more beginner-friendly. Slow down, take your time, and try to explain and show more in-depth how each setting actually works, and how it gets displayed, etc. - e.g. when enabling option ABC, this is how/where the new field appears, but when enabling XYZ, this is how it would change, etc. Remember the target audience (i.e. beginners) and be patient. There's no need to speed through unless this was meant to be a quick overview (which, based on the title, it's not). It's ok for the video to be 60+ min long, if necessary, as long as you cover the basics fully - that's how beginners learn :) Just my two cents. Cheers.
Any advice on nested relationship queries? Example Events related to venues that are related to activities. Pull info on the activities through the queried venues related to the event without relating the event to the venue and the activity 15:45 just trying to avoid bloat Bricks doesn’t give the same options when its relationships queried
For those wondering about Custom Tables. Let's say you're doing a webcomic, and each chapter has 50 images as fields, every chapter you add will add 50 entries to your metatable, so if you publish 100 chapters you'll end up with 5,000 entries in the metatable (which will affect the query speed). But with Custom Tables those 100 chapters will only create 100 entries in the metatable, and the 50 fields will be stored separately. So it's useful from a performance perspective for large projects where you will have a lot of custom posts with a lot of fields.
Always wanted to get started with CPTs, so looking forward to the rest of the series. That said, some feedback: the video starts off nicely and informative explaining the basic terminology and such, but afterwards you seem to rush through the rest of the setup process. Since this is titled a beginners guide, I think you need to remember that throughout the video creation process and make it more beginner-friendly.
Slow down, take your time, and try to explain and show more in-depth how each setting actually works, and how it gets displayed, etc. - e.g. when enabling option ABC, this is how/where the new field appears, but when enabling XYZ, this is how it would change, etc. Remember the target audience (i.e. beginners) and be patient. There's no need to speed through unless this was meant to be a quick overview (which, based on the title, it's not). It's ok for the video to be 60+ min long, if necessary, as long as you cover the basics fully - that's how beginners learn :) Just my two cents. Cheers.
Any advice on nested relationship queries?
Example Events related to venues that are related to activities. Pull info on the activities through the queried venues related to the event without relating the event to the venue and the activity 15:45 just trying to avoid bloat
Bricks doesn’t give the same options when its relationships queried
cool t-shirt 🤣
Nice shirt Paul! What's the story behind it?
Ooops.. @2:34