I'm taking this seriously. Smaller companies, independent pizzerias, coffee shops, and sandwich shops are being under served. I only need to create a product better than what is available to them right now. I'm not competing against you.
Here is a case. My Market and Deli is down the street from me. They sell hundreds of sandwiches a day out of a little deli in the back of their shop. It has to do with being near large boat yards for private luxury yachts where the crew are doing varnishing and maintaince before going the Mediterranean for the summer.
Their menu is huge with lots of modifiers for each item. Many of the modifiers come with a price that is added on. Right now a delivery company, Delivery Dudes, who everyone loves and are awesome btw, have an order form for My Market online here. But their form doesn't solve the modifier problem.
I'm passionate about Drupal and have worked with Drupal Commerce. If I wanted to build a single instance, I wouldn't waste any time and use Drupal Commerce for the back end with a rest server added to connect to an AngularJS SPA. It is a decent, inexpensive turn key solution for a small shop.
Instead I'm building the back end with Node and MongoDB. I was struggling with how to organize the models and came upon some blog posts on the MongoDB website where they share a lot of the ideas they used for the Designer Shoe Warehouse (DWS) backend. The moment I read that blog everything clicked in my mind on how to structure the database.
The biggest problem I'm having is working with trees in AngularJS. The entire menu container structure is a tree as is each menu item. There is no case where a part of the menu structure needs to be individually queried so why not store it as a big object and parse it when loaded to the UI? It will never be too large. It might be an anti pattern. However, I thought that it would be cool to construct and edit each node of the tree with the node being stored in an Angular service which I labeled the active context. The user can edit the active context, move items positions, edit its image, or description then using navigation items move up the tree one node into a different context, add a child context, and move into a child context. The breadcrumb is just the path to that node and by clicking on any link moves the user into a different context.
All the UI that you see in the images on the website were built in the last week. There are several others that I left out. I needed to take a break from working with the trees. Each context is assigned a type which is a module with a plugin that defines callbacks for CRUD operations on that context type.