WC Birmingham 2015
1 like509 views
This document discusses how WordPress was used to create a recipe and menu planning tool for catering businesses. It describes building custom post types, fields, and menus for ingredients, recipes, and costings. Challenges around recipe quantities and sub-recipes are discussed. The tool was adapted to a multisite setup to allow individual businesses to create private ingredients and recipes. Future enhancements proposed include stock tracking, calorie counting, shared/central ingredient databases, and supplier cost updates.
WC Birmingham 2015
- 1. Catering for WordPress Case Study: How WordPress was used to create a recipe building / menu planning tool for businesses within the catering industry. ! www.kirstyburgoine.co.uk twitter.com/kirstyburgoine
- 3. DEMO
- 4. The approach… Part One Building the ingredients / recipes / menus sections
- 5. The approach… Part One !important: We knew this would not be a high traffic site Building the ingredients / recipes / menus sections
- 6. 1. It would be for members only, all areas except the homepage would only be accessible if you are a member. 2. The client would maintain the ingredients and recipes post types so paying members could create their own menus. 3. Each member would only be able to view the menus they had created. Not other members menus The approach… Part One
- 7. Custom Post Type Custom Post Type Custom Post Type Custom Fields Custom Fields Custom Fields The approach… Part One
- 9. Ingredients Recipes Menus Advanced Custom Fields ! Relational Field The approach… Part One
- 10. DEMO
- 11. Menus Custom roles and permissions The approach… Part One
- 13. The approach… Part Two 1. Need to give cost per dish 2. Allow the client to manually alter the amount of profit they make on each dish Costings
- 14. DEMO
- 15. The approach… Part Two Adding the ingredient
- 16. The approach… Part Two Creating the recipe
- 20. Recipe quantities… The approach… Part Three
- 21. But what about cake? The approach… Part Three
- 23. The approach… Part Four Sub Recipes…
- 31. The approach… Part Six Enter flexible content…
- 34. Permissions & roles The approach… Part Six
- 35. • People loved the recipe / menu builder functionality but actually they would rather add their own ingredients, especially if they use a lot of locally grown produce. • They would also want to create their own recipes as well as the menus for use within their organisation only. Feedback
- 36. Going back to “Agile Development”
- 38. Multisite
- 39. Multisite
- 40. Multisite
- 41. Multisite A Few Additional Changes • Introduced a child theme for MyEchef so that all of the content on sub domains was password protected and only the parent MyEchef theme was open to the public. ! • Moved all of the code for the custom post types out of my theme and instead created plugins for them. I also exported all of the code ACF created for the custom fields and put that in the relevant plugin as well so that the code was all kept together.
- 43. To the future!
- 44. What next? • Stock take facility • Calorie counter • Central ingredients database + separate. Or an easy way to share data across sub domains • Suppliers update costs for their ingredients only
- 45. Kirsty Burgoine! @kirstyburgoine www.kirstyburgoine.co.uk Thank you for listening.