If she woke up to a vibration from a watch, I bet she’d wake up hearing motorized blinds.

What’s the problem with just not using the portion of the service you do not wish to use? For almost everyone, the integration with email for the calendar is what actually makes it function, where you will be interacting with other people. Most people who want to create a new, unique calendar will just create an additional one in an existing account if they want a separate calendar for a certain purpose.

That’s what I do with my wife for events that we both need to know about. So we have a calendar that is just our stuff and we both subscribe to it (or more like she has the calendar shared with her from my account) but she has permissions to add/remove things. Is there some reason you need a completely separate calendar on a unique service? I feel like we are missing something about your use case to actually be able to understand what you are trying to do.

I would also second Hugo which I use for my personal site and blog which I haven’t updated for a long time. Nice thing is that it has a minimal footprint of needing to watch out for updates unlike something like Wordpress which was known for being vulnerable stable if left unmaintained. It’s mostly looking out for old themes with vulnerable javascript.

Another popular options is Jekyll and I honestly can’t remember why I picked Hugo over it but if you don’t need dynamic content, why make things more complex?