The public-facing Room Schedule page is attempting to call the /api/rooms endpoint, which is throwing an error because the endpoint requires authentication. However, given that:
We don't actually have any meeting/room assignments in the database now
This data is more granular than the other pages and potentially less useful to "outside" users
I think we should just hide the Room Schedule from the public-facing site for the time being.
The public-facing Room Schedule page is attempting to call the
/api/rooms
endpoint, which is throwing an error because the endpoint requires authentication. However, given that:I think we should just hide the Room Schedule from the public-facing site for the time being.