How to represent this kind of data (Daily food menu)

Question

I need to represent a food menu from the admin side. It is most likely to be updated/created weekly.

Here are what I have tried:

• Calendar View
  • Pros
    • Looks natural since it's based on date
  • Cons
    • Lack of control? Where to put edit? delete?

When clicking on + number more link on the date, it'll show a mini popup of the extended list:

• List View
  • Pros
    • Will be based on weekly view. Food menu is updated every week.
  • Cons
    • Lack of control too?

Other ideas that I'm planning to do would be:

• Change the popup into a modal that will allow me to do what I need like add button at the bottom for Edit, Delete or whatever

• Use table that has "Available Data", "Lunches", "Dinners", "Actions" columns (Most simplest one)

• Cards in grid that can be sorted or filtered maybe?

Any suggestions or opinions to those who have encountered a situation like this before?

EDIT:

I tried to use a table and planning to stick with it.

I made a table that shows 5 rows to represent the weekly menu excluding the weekends. It looks like:

[Menu date] [Lunches] [Dinners] [Actions]

Answer 1

I guess the OS X Calendar App's Week View design should do the trick for you. You can have the view of a complete week at your disposal, switch weeks, add or remove items.

To remove items (events in the calendar app) you could incorporate a cross on the top of the item. And you could double click an item to edit it. I guess that would serve the purpose for you.

---

You could add a new menu item by double clicking anywhere in the column.

You could edit an added item by double clicking on it.

You could delete an item by hovering over it and clicking the cross as it appears.

You could navigate between weeks by clicking the arrows on the top right.

Answer 2

It is good to show the weekly calendar in the general (Add/Edit) view. Provide monthly view if required. So that, there will be enough space to display Add/Edit buttons, As per I understood. Also I'm new to the UX space, this may not be a good solution. Something like this,